Thanks for the info, Bertrand.

Mailing lists can be just as exclusive as semi-synchronous environments. They 
may not work for your community, but they work for ours, and removing them will 
necessarily disadvantage many contributors.

I'm firmly of the opinion that you can't completely ignore real-time 
communications and expect 100% of everything to occur asynchronously on mailing 
lists. It explicitly disallows certain types of communication that you can't 
have in a mailing list. You have the imposition of the formality of a mailing 
list for newcomers, you have the "being on record" syndrome, you have the "must 
be subscribed to post" problem (not always), and finally you are ignoring the 
fact that people will talk real time anyway - so why not make that a venue that 
you at least have some control/visibility over? In fact, my doctoral research 
was on how semi-synchronous communications support distance work and learning 
better than fully asynchronous ones....

-Joan

----- Original Message -----
From: "Bertrand Delacretaz" <bdelacre...@apache.org>
To: "dev" <dev@community.apache.org>
Cc: d...@fineract.apache.org, "Myrle Krantz" <my...@apache.org>, 
mifos-develo...@lists.sourceforge.net, mifos-us...@lists.sourceforge.net, 
u...@fineract.apache.org
Sent: Wednesday, October 17, 2018 12:04:27 PM
Subject: Re: Dev vs User Mailing Lists

On Tue, Oct 16, 2018 at 7:46 PM <r...@gardler.org> 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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Reply via email to