Hi Bertrand,
For me it looks as if tech@ would be one huge list ...
and the amount of emails of interest to me would be only a fraction.
Having named topic lists would help focus.
It would allow to skim the topics and react on the ones of interest.
Guess a tech-list would just feel like being on one of those project lists,
Here they do most discussions in guthub pull-requests and who's mailinglists
have almost no emails of interest anymore or I just can't find them in
between 10000000 of bot emails.
Chris
Am 07.06.19, 09:26 schrieb "Bertrand Delacretaz" <bdelacre...@apache.org>:
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
