Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@
Ivan Habunek <[email protected]> Wed, 08 Mar 2017 10:53:30 +0100
| Newsgroups | gmane.comp.apache.logging |
|---|---|
| Message-ID | <1488966810.3723506.904307312.5F8AC00D@webmail.messagingengine.com> |
This is a multi-part message in MIME format. --_----------=_148896681037235062 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" On Wed, 8 Mar 2017, at 05:20, Matt Sicker 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@ -> > [email protected] > log4j-user@, log4php-user@, log4net-user@, log4cxx-user@, general@ -> > [email protected] > > 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] > -0 It's unclear which problems this solve. I don't think there's a reason developers from one project would be interested in either dev@ or user@ mail traffic from other projects. Well, at least having subject tags, it's possible to create email filters. Regards, -- Ivan --_----------=_148896681037235062 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="utf-8" <!DOCTYPE html> <html> <head> <title></title> </head> <body><div>On Wed, 8 Mar 2017, at 05:20, Matt Sicker wrote:<br></div> <blockquote type="cite"><div dir="ltr"><div>I may be missing some mailing lists considering I just subscribed to half of them less than five minutes ago.<br></div> <div><br></div> <div>This is a vote to merge the various Apache Logging Services mailing lists. The proposal is to combine them as follows:<br></div> <div><br></div> <div>log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ -> <a href="mailto:[email protected]">[email protected]</a><br></div> <div>log4j-user@, log4php-user@, log4net-user@, log4cxx-user@, general@ -> <a href="mailto:[email protected]">[email protected]</a><br></div> <div><br></div> <div>commits@ and private@ remain the same as before.<br></div> <div><br></div> <div>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:<br></div> <div><br></div> <div>[java]<br></div> <div>[net]<br></div> <div>[cxx]<br></div> <div>[php]<br></div> <div><br></div> </div> </blockquote><div><br></div> <div>-0<br></div> <div><br></div> <div>It's unclear which problems this solve. I don't think there's a reason developers from one project would be interested in either dev@ or user@ mail traffic from other projects. <br></div> <div><br></div> <div>Well, at least having subject tags, it's possible to create email filters.<br></div> <div><br></div> <div>Regards,<br></div> <div>-- <br></div> <div>Ivan<br></div> <div><br></div> </body> </html> --_----------=_148896681037235062--