Hi Bertrand, But I think in this case we get another general list without any focus. I think this would prevent people from subscribing. For me it wouldn't be that interesting subscribing to a list that generic. A specialized list would lower the bar for subscribing, I think. And after all, the main purpose of such a list is helping the inter-project knowledge transfer - at least that was the reason I proposed it - so it could even be restricted to committers ... Don't think we need another super-user-list, and if we want one, that would be a totally different topic (at least for me)
Chris Outlook for Android<https://aka.ms/ghei36> herunterladen ________________________________ From: Bertrand Delacretaz <bdelacre...@apache.org> Sent: Thursday, January 3, 2019 10:48:33 AM To: dev Subject: Re: Introducing lists based on the overall project categories? On Sun, Dec 30, 2018 at 6:01 PM Christofer Dutz <christofer.d...@c-ware.de> wrote: > ...I think creating them wouldn't be a huge overhead ..... Creating lists is easy but that doesn't mean they will be used, and oversight of multiple lists is a burden (for comdev? or which PMC is in charge of them?). And scattered discussions don't help building communities. What if someone has a question on streaming for IoT devices used in Big Data contexts? Cross-posting to 3 lists is a guaranteed mess and you'll often forget that other list which would also have been interested. I strongly suggest starting with a single tech@ list with [subject line tags] as mentioned earlier in this thread, and create more lists *only* if there is too much traffic on a given topic. [1] has more info on why we like busy lists as opposed to multiple ones. -Bertrand [1] https://grep.codeconsult.ch/2011/12/06/stefanos-mazzocchis-busy-list-pattern/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
