www.google.com Xavier.Galindo1972
On Oct 11, 2018 04:53, "Bertrand Delacretaz" <bdelacre...@apache.org> wrote: Hi, On Wed, Oct 10, 2018 at 6:00 PM Ed Cable <edca...@mifos.org> wrote: > ...One possible option is just to consolidate the lists into dev but I don't > think that is good long-term because as community grows we will have > distinct technical vs. functional/design conversations happening... Until that happens it's usually preferable to have a single list, and split later if really, really needed. Here are some thoughts about busy lists that might help (shameless plug, on my blog but the actual thoughts are not from me): https://grep.codeconsult.ch/2011/12/06/stefanos-mazzocchis-busy-list-pattern/ The "single list with tagged messages" pattern also mentioned by Tarun in this thread is successfully by OpenStack, see [1] for example - I think that's a great way to keep a community in a single place while not wasting people's time. One can scan many thread subject lines quickly if they use such [tags] and if people stick to one topic per thread that's very efficient. The key is to allow people to *process* many messages quickly, while *reading* just the few that are of interest to them. -Bertrand [1] http://lists.openstack.org/pipermail/openstack-dev/2017-June/thread.html --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
