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
