> log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ -> d...@logging.apache.org
+0 I can see some benefits, but I think that most developers outside of the PMC are like regular users and only care about one about the projects. > log4j-user@, log4php-user@, log4net-user@, log4cxx-user@, general@ -> u...@logging.apache.org -1 I am quite sure that most users only care about one of the projects, and they don't want to be spammed with irrelevant messages about the others. We (the PMC) shouldn't annoy users just to make it slightly more convenient for ourselves. On Wed, Mar 8, 2017 at 5:20 AM, Matt Sicker <boa...@gmail.com> wrote: > I may be missing some mailing lists considering I just subscribed to half > of them less than five minutes ago. > > This is a vote to merge the various Apache Logging Services mailing lists. > The proposal is to combine them as follows: > > log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ -> > d...@logging.apache.org > log4j-user@, log4php-user@, log4net-user@, log4cxx-user@, general@ -> > u...@logging.apache.org > > commits@ and private@ remain the same as before. > > The proposal would also suggest that the old emails become aliases for the > combined email names so as not to lose any future emails. To distinguish > between projects, a subject tag can be added such as: > > [java] > [net] > [cxx] > [php] > > Though I wouldn't think such a tag is required, though it should help in > gaining the attention of the appropriate audience. > > Voting: > > +1: Yes, combine the mailing lists! > +0: Go ahead, don't care that much. > -0: Don't like it, but not vetoing it. > -1: No, don't do that! I have a better idea! > > This vote follows the same "lazy consensus" (at least 3 +1 binding, no > -1/vetoes) we use for general releases and whatnot. The vote will be open > for at least 72 hours. > > -- > Matt Sicker <boa...@gmail.com> > -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* mikael.stal...@magine.com Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
