+1 on combining listservs and using [TOPIC_HEADING] and try to keep issues to one topic.
email is natively asynchronous communication, standardized across all user systems and experiences, ubiquitous when archived it is searchable yes, it is old school, but it works there is a tongue in cheek saying that all collaboration systems (e.g. Slack) devolves to email functionality eventually https://api.slack.com/methods/search.messages Further related topic? [Tools for Collaboration of Community] I'd suggest that the fineract community should: 1) stay focused on the existing and mainstream apache tools that are current, rather than on the cutting edge, acknowledging there's always a new thing that is cool 2) practice good email hygiene with {TOPICS} and on-topic threads, using a mantra of disciplined culture (this thread is now somewhat off topic, and I would note got there very quickly) 3) reduce the number of communication channels for the fineract community, understanding that many users and developers also are subscribed to- and participate in-the mifos community which is the origin of the community and still has a 90%+ overlap (90% of members of fineract are members of mifos I figure, but didn't calc) 4) have clear roles for the various tools and flows - which are described as part of the "Getting Started" wiki how information is summarized and flows from one forum to another, specific to our community but leveraging Apache norms (which also should be noted): e.g. email discourse leads to a wiki entry like a requirements page , or leads to a bug issue, or leads to a new feature, or leads to a development sprint ; e.g. JIRA entries are summarized quarterly or monthly back to the listserve to provide round trip ; e.g. github commit entries are auto included in JIRA tickets when tagged appropriately ; ~Jdailey On Wed, Oct 17, 2018 at 9:11 AM Ed Cable <[email protected]> wrote: > Thanks for sharing that Bertrand - it was a good read - and easy for you > to share because it was discussed publicly on a mailing list :) > > On that thread as well there was also a lot of support for a > discourse-based forum too which can be a nice happy medium offering the > advantages of a mailing list and the approachability of a chat/forum. > > Ed > > On Wed, Oct 17, 2018 at 9:04 AM Bertrand Delacretaz < > [email protected]> > wrote: > > > On Tue, Oct 16, 2018 at 7:46 PM <[email protected]> wrote: > > > > > > ...[ASIDE] Realtime communications are not inclusive... > > > > FWIW there was a good discussion about this recently in Apache Arrow: > > > > > > > https://lists.apache.org/thread.html/8433cda04dc9e1d6bb235e4f29bde30d07c3e5d81177af785af177f2@%3Cdev.arrow.apache.org%3E > > > > -Bertrand > > > > > -- > *Ed Cable* > President/CEO, Mifos Initiative > [email protected] | Skype: edcable | Mobile: +1.484.477.8649 > <(484)%20477-8649> > > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org > <http://facebook.com/mifos> <http://www.twitter.com/mifos> >
