Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@
Matt Sicker <[email protected]> Wed, 8 Mar 2017 10:41:49 -0600
| Newsgroups | gmane.comp.apache.logging,gmane.comp.jakarta.log4j.devel,gmane.comp.apache.logging.log4cxx.devel |
|---|---|
| Message-ID | <CACmp6kp8J1ia_kWOiq1_3m4pVNdLhaUs4mCcyF8xYYAoSB7+Yg@mail.gmail.com> |
--94eb2c0b0c1c1525ed054a3ace9b Content-Type: text/plain; charset=UTF-8 Based on the voting so far, it looks like merging user lists isn't desired. I'm cool with that, so I'll -1 the user list merge as well. I'm still +1 for merging developer lists unless someone has a better idea. We shouldn't have to rely on the private list for public discussions. On 8 March 2017 at 06:38, Apache <[email protected]> wrote: > The reason for doing this is a result of the last board meeting. The PMC > had to discuss something on the private mailing list simply because PMC > members don't subscribe to every list, nor do they want to, so it was not > possible to have the discussion on the correct mailing list. > > Ralph > > On Mar 7, 2017, at 9:20 PM, Matt Sicker <[email protected]> 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] > > 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 <[email protected]> > > -- Matt Sicker <[email protected]> --94eb2c0b0c1c1525ed054a3ace9b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Based on the voting so far, it looks like merging user lis= ts isn't desired. I'm cool with that, so I'll -1 the user list = merge as well. I'm still +1 for merging developer lists unless someone = has a better idea. We shouldn't have to rely on the private list for pu= blic discussions.</div><div class=3D"gmail_extra"><br><div class=3D"gmail_q= uote">On 8 March 2017 at 06:38, Apache <span dir=3D"ltr"><<a href=3D"mai= lto:[email protected]" target=3D"_blank">[email protected]= m</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi= n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto"= ><div>The reason for doing this is a result of the last board meeting. The = PMC had to discuss something on the private mailing list simply because PMC= members don't subscribe to every list, nor do they want to, so it was = not possible to have the discussion on the correct mailing list.<span class= =3D"HOEnZb"><font color=3D"#888888"><br><br></font></span></div><span class= =3D"HOEnZb"><font color=3D"#888888"><div id=3D"m_-3899264141692311570AppleM= ailSignature">Ralph</div></font></span><div><div class=3D"h5"><div><br>On M= ar 7, 2017, at 9:20 PM, Matt Sicker <<a href=3D"mailto:[email protected]"= target=3D"_blank">[email protected]</a>> wrote:<br><br></div><blockquote= type=3D"cite"><div><div dir=3D"ltr">I may be missing some mailing lists co= nsidering I just subscribed to half of them less than five minutes ago.<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:</div><div><br><= /div><div>log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ -> <a hre= f=3D"mailto:[email protected]" target=3D"_blank">[email protected]= g</a></div><div>log4j-user@, log4php-user@, log4net-user@, log4cxx-user@, g= eneral@ -> <a href=3D"mailto:[email protected]" target=3D"_blank">= [email protected]</a></div><div><br></div><div>commits@ and private@ = remain the same as before.</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 subje= ct tag can be added such as:</div><div><br></div><div>[java]</div><div>[net= ]</div><div>[cxx]</div><div>[php]</div><div><br></div><div>Though I wouldn&= #39;t think such a tag is required, though it should help in gaining the at= tention of the appropriate audience.</div><div><br></div><div>Voting:</div>= <div><br></div><div>+1: Yes, combine the mailing lists!</div><div>+0: Go ah= ead, don't care that much.</div><div>-0: Don't like it, but not vet= oing it.</div><div>-1: No, don't do that! I have a better idea!</div><d= iv><br></div><div>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.<br clear=3D"all"><div><br></d= iv>-- <br><div class=3D"m_-3899264141692311570gmail_signature">Matt Sicker = <<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]<= /a>></div> </div></div> </div></blockquote></div></div></div></blockquote></div><br><br clear=3D"al= l"><div><br></div>-- <br><div class=3D"gmail_signature" data-smartmail=3D"g= mail_signature">Matt Sicker <<a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a>></div> </div> --94eb2c0b0c1c1525ed054a3ace9b--