Repeating (with minor edits for this context) what I have said on a similar topic on another thread:
The criteria that the ASF looks for in communication channels used by projects are (in no particular order): - open to all - asynchronous - available off-line - full history - searchable - archived on ASF controlled systems - low bandwidth / minimal system requirements E-mail may seem a little 'old school' at times but it is one of the few technologies that meets all of the above. Which is why most of our systems are configured to echo stuff back to the relevant mailing list. These days I'm used to an always on internet connections with speeds in the 10s of megabits where I don't need to worry about the cost (even when I am out and about) but it is worth remembering that not everyone is in that position. It wasn't really that long ago that I could sometimes be found working on Apache projects via a 9600 bits per second dial-up connection that I paid for by the second. It was perfectly possible for me to follow what was going on by connecting for a few minutes every couple of hours, syncing my email, making a few commits if I had anything to commit and then disconnecting and continuing to work off-line. If a large proportion of communication had happened via a Gitter like interface there is no way I would have been able to follow the project. I'll also note that I am deliberately ignoring Gitter. It isn't an 'official' communication channel for the project so I should not need to follow it to keep track of what is going on and any decisions that are being made. I accept that there are times were using a 'real-time' communication channel is more efficient. However, it excludes every member of the community that isn't participating in that channel at that point in time. The default position at the ASF is that it is better for communication to be a little less efficient for a few in order for the entire community to participate. Cheers, Mark On 08/09/18 13:58, Kun Song wrote: > Gitter is very popular among open source projects. The famous projects on > github often have a Gitter channel for users as well as a channel for > developers. Email list is good for some serious discussions, and Gitter is > good for real time discussions. > > Gitter is born for github projects, from it, you can send a message with well > formatted code, and it will show you every activity about this projects. > > So I think we can have both email list and Gitter, they will complement one > another perfectly. > > >> 在 2018年9月7日，上午11:32，Jerrick Zhu <[email protected]> 写道： >> >> hi, community >> >> Now, we have some chat groups, which are used to discuss about dubbo, such >> as: >> >> * Dingtalk group, nearly 30 people, committers and contributors >> * WeChat group, contains committers, contributors, and many users >> >> I think we need to public these chat groups, so that all people can join >> us. >> >> Maybe Gitter? or Slack ? >> >> Or maybe we can drop the chat, just use the mailing list and github issue >> for discuss. >> >> Any other suggestions? >> >> Sincerely. >> >> jerrick >
