We can have both. And if we can have only one thing I'm in favor of the project category list that Chris suggested.
If we have one huge list it'll just mean more mails etc., people having to set up filters or skip over stuff they are not interested in. I can imagine a single bigdata@ list to be super useful for coordination between all those scattered projects: < https://projects.apache.org/projects.html?category> (hadoop has its own category there, a bit confusing) On Fri, Jun 7, 2019 at 9:26 AM Bertrand Delacretaz <bdelacre...@apache.org> wrote: > Hi Chris, > > On Thu, Jun 6, 2019 at 4:02 PM Christofer Dutz > <christofer.d...@c-ware.de> wrote: > > ...I would really like to create an i...@apache.org mailinglist... > > Allow me to insist ;-) > > What's wrong with an [iot] subject line tag on a t...@apache.org mailing > list? > > The problem with single-topic lists is that discussions are rarely > single-topic: if you have a question about memory leaks in Java in a > Docker image that runs in an iot context, and we have multiple > java|docker|memorymanagement|iot lists, where are you going to post? > > Cross-posting is ugly...writing to t...@apache.org with > [java][memory][docker][iot] subject line tags will work, and having a > single list will help get critical mass about "the place where Apache > community members discuss cross-cutting technical issues". > > But whoever does the work decides... > > -Bertrand > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
