I see that folks are not as familiar with Zulip, so a bit of background info:

https://techblog.wikimedia.org/2020/05/04/using-zulip-an-open-source-tool-for-engaging-participants-in-wikimedias-technical-outreach-programs/ 

And yes, an open source variant of slack seems to be a decent description.

I have never tried it out before.



On Tue, Jul 14, 2020 at 10:45 AM Samuel Klein <meta.sj@gmail.com> wrote:
Thanks! My prefs: 

My thought would be that there is a need for three different channels:
* First and foremost, a channel to document decisions, essays, documents, plans, etc.

On WikiSpore, inviting it to work out better ways to transfer those discussions to (Abstractipedia) en masse than currently provided by Meta.   With stubs on Meta showing the crosswiki links to the Spore pages
 
* Second, a channel for asynchronous discussion, announcements, etc.

This list, for all tech and non-tech discussion.
 
* Third, a channel for synchronous discussion, for quick discussions, office hours, socialization, and later, when testing and deployment starts, for quick feedback

IRC/TG with a bridge. One channel on each.
I'm a fan of slopi communication, even when synchronous.
  
SJ
_______________________________________________
Abstract-Wikipedia mailing list
Abstract-Wikipedia@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia