Re: IETF Slack workspace

[Yoav Nir <[e-mail]>]

Because adding more tools for collaboration makes it harder, not easier, to participate.

When we deal with a technical issue, there is usually a draft. The conversation about this draft already happens in several places:
The working group mailing list
Occasionally, the IETF or last-call mailing lists
GitHub if that is where the document is developed
Physical or Meetecho WG meetings
Jabber / Meetecho chat

In order to follow the conversation about this draft, you have to be on *all* of them. If you don’t like github, some conversation is going to happen there, and you will miss it.

By adding more tools,  you increase the requirements to participate in the conversation.  A diversity of tools helps when it gives you another option to have a conversation where each conversation uses one tool.  Here we have one conversation that is happening using many tools.

Yoav

> On 27 Aug 2020, at 23:08, Ali Mezgani <[e-mail]> wrote:
> 
> For agility Slack is an instant and real time talking methodology.
> 
> I’m also, like mailing list but why not encourage diversity of tool to collaborate.
> 
> Ali.
> 
> Native LABs
> https://www.nativelabs.ma/ <https://www.nativelabs.ma/>
> 
> 
> 
> On Thu, Aug 27, 2020 at 20:58 Keith Moore <[e-mail] <mailto:[e-mail]>> wrote:
> On 8/27/20 2:55 PM, Rich Kulawiec wrote:
> 
> 
> 
> > I strong advise avoiding them entirely.  Mailing lists are a vastly
> 
> > superior tool for collaboration -- and their archives are one of the
> 
> > most stable, usable, searchable long-term solutions we have.
> 
> 
> 
> +1
> 
> 
> 
> 
>