Re: [vote] rearrange commits lists
Brett Porter wrote, On 8/8/2005 5:15 PM: Hi, Alan proposed we use the standard that is used when setting up Apache projects these days (we're still on our 2003 setup). Here it is in summary, elaborated into a bit more detail: 1) create [EMAIL PROTECTED], scm-commits, wagon-commits, continuum-commits 2) subscribe everyone on [EMAIL PROTECTED], [EMAIL PROTECTED], post to the list to let people know what they are in for and instructions to unsubscribe 3) stop *-dev forwarding from commits lists 4) reconfigure svn to put Maven commits to that list. I think Maven plugin developers should keep across what's happening in the core, so they can stay together, but the other subprojects remain separate. 5) keep JIRA and repository reports on [EMAIL PROTECTED] 6) send continuum/ci messages to the relevant commits list 7) disband the old cvs lists Please vote: [X] +1: in favour [ ] +0 < x < +1: in favour, but prefer a different setup [ ] 0: don't care either way [ ] -1: I don't like this for reason __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] rearrange commits lists
Ok, I have put this forward to apmail as suggested. We can later discuss moving JIRA, repository, etc to [EMAIL PROTECTED] I would like to keep them named commits@ to be consistent with other Apache lists. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] rearrange commits lists
+1 On 8/8/05, Brett Porter <[EMAIL PROTECTED]> wrote: > Hi, > > Alan proposed we use the standard that is used when setting up Apache > projects these days (we're still on our 2003 setup). > > Here it is in summary, elaborated into a bit more detail: > > 1) create [EMAIL PROTECTED], scm-commits, wagon-commits, > continuum-commits > 2) subscribe everyone on [EMAIL PROTECTED], [EMAIL PROTECTED], > post to the list to let people know what they are in for and > instructions to unsubscribe > 3) stop *-dev forwarding from commits lists > 4) reconfigure svn to put Maven commits to that list. I think Maven > plugin developers should keep across what's happening in the core, so > they can stay together, but the other subprojects remain separate. > 5) keep JIRA and repository reports on [EMAIL PROTECTED] > 6) send continuum/ci messages to the relevant commits list > 7) disband the old cvs lists > > Please vote: > [ ] +1: in favour > [ ] +0 < x < +1: in favour, but prefer a different setup > [ ] 0: don't care either way > [ ] -1: I don't like this for reason __ > > From me, +1. I think this might help increase subscription to the dev list. > > Vote closes after 24 hours, where if the numerical addition of all votes > > 0 will carry it. Any votes outside of the range -1 <= x <= +1 will be > considered donkey votes and omitted :) > > Cheers, > Brett > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] rearrange commits lists
Here are some comments from someone who is not a Maven developer but still subscribes to the dev list. Brett Porter wrote: Hi, Alan proposed we use the standard that is used when setting up Apache projects these days (we're still on our 2003 setup). Here it is in summary, elaborated into a bit more detail: 1) create [EMAIL PROTECTED], scm-commits, wagon-commits, continuum-commits +1 2) subscribe everyone on [EMAIL PROTECTED], [EMAIL PROTECTED], post to the list to let people know what they are in for and instructions to unsubscribe +1 3) stop *-dev forwarding from commits lists +1 4) reconfigure svn to put Maven commits to that list. I think Maven plugin developers should keep across what's happening in the core, so they can stay together, but the other subprojects remain separate. +1 5) keep JIRA and repository reports on [EMAIL PROTECTED] Keep JIRA on the dev-list, except for MEV, see below. I would like to suggest one more list: [EMAIL PROTECTED] This list would receive the REPOCLEAN e-mails and also the [MEV###] e-mails from JIRA. These e-mails are about managing the repository. 6) send continuum/ci messages to the relevant commits list +1 7) disband the old cvs lists +1 Please vote: [ ] +1: in favour [ ] +0 < x < +1: in favour, but prefer a different setup [ ] 0: don't care either way [ ] -1: I don't like this for reason __ From me, +1. I think this might help increase subscription to the dev list. Vote closes after 24 hours, where if the numerical addition of all votes 0 will carry it. Any votes outside of the range -1 <= x <= +1 will be considered donkey votes and omitted :) Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] rearrange commits lists
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: mardi 9 août 2005 02:16 > To: Maven Developers List > Subject: [vote] rearrange commits lists > > Hi, > > Alan proposed we use the standard that is used when setting up Apache > projects these days (we're still on our 2003 setup). > > Here it is in summary, elaborated into a bit more detail: > > 1) create [EMAIL PROTECTED], scm-commits, wagon-commits, > continuum-commits +0. Not sure I would call it commits. I would create a list that would receive: - JIRA issues - SCM commits - Build successes/failures - repo notifications Not sure how to name it though. Could be [EMAIL PROTECTED] I'm fine with [EMAIL PROTECTED] too. > 2) subscribe everyone on [EMAIL PROTECTED], [EMAIL PROTECTED], > post to the list to let people know what they are in for and > instructions to unsubscribe What is [EMAIL PROTECTED] for? Do you mean [EMAIL PROTECTED] > 3) stop *-dev forwarding from commits lists ok > 4) reconfigure svn to put Maven commits to that list. I think Maven > plugin developers should keep across what's happening in the core, so > they can stay together, but the other subprojects remain separate. +1 > 5) keep JIRA and repository reports on [EMAIL PROTECTED] Hmm... Not sure about this one. My first reaction was to put them on the commits list but thinking about it, I'm not sure anymore. > 6) send continuum/ci messages to the relevant commits list +1 > 7) disband the old cvs lists +1 Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] rearrange commits lists
+1 Arnaud On 8/9/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > +1 from me > > Emmanuel > > Brett Porter wrote: > > Hi, > > > > Alan proposed we use the standard that is used when setting up Apache > > projects these days (we're still on our 2003 setup). > > > > Here it is in summary, elaborated into a bit more detail: > > > > 1) create [EMAIL PROTECTED], scm-commits, wagon-commits, > > continuum-commits > > 2) subscribe everyone on [EMAIL PROTECTED], [EMAIL PROTECTED], > > post to the list to let people know what they are in for and > > instructions to unsubscribe > > 3) stop *-dev forwarding from commits lists > > 4) reconfigure svn to put Maven commits to that list. I think Maven > > plugin developers should keep across what's happening in the core, so > > they can stay together, but the other subprojects remain separate. > > 5) keep JIRA and repository reports on [EMAIL PROTECTED] > > 6) send continuum/ci messages to the relevant commits list > > 7) disband the old cvs lists > > > > Please vote: > > [ ] +1: in favour > > [ ] +0 < x < +1: in favour, but prefer a different setup > > [ ] 0: don't care either way > > [ ] -1: I don't like this for reason __ > > > >>From me, +1. I think this might help increase subscription to the dev > list. > > > > Vote closes after 24 hours, where if the numerical addition of all votes > > > >>0 will carry it. Any votes outside of the range -1 <= x <= +1 will be > > > > considered donkey votes and omitted :) > > > > Cheers, > > Brett > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: [vote] rearrange commits lists
+1 from me Emmanuel Brett Porter wrote: Hi, Alan proposed we use the standard that is used when setting up Apache projects these days (we're still on our 2003 setup). Here it is in summary, elaborated into a bit more detail: 1) create [EMAIL PROTECTED], scm-commits, wagon-commits, continuum-commits 2) subscribe everyone on [EMAIL PROTECTED], [EMAIL PROTECTED], post to the list to let people know what they are in for and instructions to unsubscribe 3) stop *-dev forwarding from commits lists 4) reconfigure svn to put Maven commits to that list. I think Maven plugin developers should keep across what's happening in the core, so they can stay together, but the other subprojects remain separate. 5) keep JIRA and repository reports on [EMAIL PROTECTED] 6) send continuum/ci messages to the relevant commits list 7) disband the old cvs lists Please vote: [ ] +1: in favour [ ] +0 < x < +1: in favour, but prefer a different setup [ ] 0: don't care either way [ ] -1: I don't like this for reason __ From me, +1. I think this might help increase subscription to the dev list. Vote closes after 24 hours, where if the numerical addition of all votes 0 will carry it. Any votes outside of the range -1 <= x <= +1 will be considered donkey votes and omitted :) Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] rearrange commits lists
+1 On 8/9/05, Brett Porter <[EMAIL PROTECTED]> wrote: > Hi, > > Alan proposed we use the standard that is used when setting up Apache > projects these days (we're still on our 2003 setup). > > Here it is in summary, elaborated into a bit more detail: > > 1) create [EMAIL PROTECTED], scm-commits, wagon-commits, > continuum-commits > 2) subscribe everyone on [EMAIL PROTECTED], [EMAIL PROTECTED], > post to the list to let people know what they are in for and > instructions to unsubscribe > 3) stop *-dev forwarding from commits lists > 4) reconfigure svn to put Maven commits to that list. I think Maven > plugin developers should keep across what's happening in the core, so > they can stay together, but the other subprojects remain separate. > 5) keep JIRA and repository reports on [EMAIL PROTECTED] > 6) send continuum/ci messages to the relevant commits list > 7) disband the old cvs lists > > Please vote: > [ ] +1: in favour > [ ] +0 < x < +1: in favour, but prefer a different setup > [ ] 0: don't care either way > [ ] -1: I don't like this for reason __ > > From me, +1. I think this might help increase subscription to the dev list. > > Vote closes after 24 hours, where if the numerical addition of all votes > > 0 will carry it. Any votes outside of the range -1 <= x <= +1 will be > considered donkey votes and omitted :) > > Cheers, > Brett > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .::You're welcome ::. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: repository mails was: [vote] rearrange commits lists
Right, maybe commits is more appropriate for this. I do like the current visibility. Either that, or send them all directly to Carlos. He's been a machine - just awesome :) - Brett Kenney Westerhof wrote: >On Tue, 9 Aug 2005, Brett Porter wrote: > >+0.9 > >I'm not entirely sure if the REPOCLEAN stuff should go to the dev list. >Could fit in with the MEV jira list (which ends up in maven-dev), although >I don't think non-committers are very interested in those. But creating >another list for repoclean will introduce the risk that no-one will >subscribe to it. > > > >>Hi, >> >>Alan proposed we use the standard that is used when setting up Apache >>projects these days (we're still on our 2003 setup). >> >>Here it is in summary, elaborated into a bit more detail: >> >>1) create [EMAIL PROTECTED], scm-commits, wagon-commits, >>continuum-commits >>2) subscribe everyone on [EMAIL PROTECTED], [EMAIL PROTECTED], >>post to the list to let people know what they are in for and >>instructions to unsubscribe >>3) stop *-dev forwarding from commits lists >>4) reconfigure svn to put Maven commits to that list. I think Maven >>plugin developers should keep across what's happening in the core, so >>they can stay together, but the other subprojects remain separate. >>5) keep JIRA and repository reports on [EMAIL PROTECTED] >>6) send continuum/ci messages to the relevant commits list >>7) disband the old cvs lists >> >>Please vote: >>[ ] +1: in favour >>[ ] +0 < x < +1: in favour, but prefer a different setup >>[ ] 0: don't care either way >>[ ] -1: I don't like this for reason __ >> >>>From me, +1. I think this might help increase subscription to the dev list. >> >>Vote closes after 24 hours, where if the numerical addition of all votes >> >> >>>0 will carry it. Any votes outside of the range -1 <= x <= +1 will be >>> >>> >>considered donkey votes and omitted :) >> >>Cheers, >>Brett >> >> >>- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > >-- >Kenney Westerhof >http://www.neonics.com >GPG public key: http://www.gods.nl/~forge/kenneyw.key > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] rearrange commits lists
On Tue, 9 Aug 2005, Brett Porter wrote: +0.9 I'm not entirely sure if the REPOCLEAN stuff should go to the dev list. Could fit in with the MEV jira list (which ends up in maven-dev), although I don't think non-committers are very interested in those. But creating another list for repoclean will introduce the risk that no-one will subscribe to it. > Hi, > > Alan proposed we use the standard that is used when setting up Apache > projects these days (we're still on our 2003 setup). > > Here it is in summary, elaborated into a bit more detail: > > 1) create [EMAIL PROTECTED], scm-commits, wagon-commits, > continuum-commits > 2) subscribe everyone on [EMAIL PROTECTED], [EMAIL PROTECTED], > post to the list to let people know what they are in for and > instructions to unsubscribe > 3) stop *-dev forwarding from commits lists > 4) reconfigure svn to put Maven commits to that list. I think Maven > plugin developers should keep across what's happening in the core, so > they can stay together, but the other subprojects remain separate. > 5) keep JIRA and repository reports on [EMAIL PROTECTED] > 6) send continuum/ci messages to the relevant commits list > 7) disband the old cvs lists > > Please vote: > [ ] +1: in favour > [ ] +0 < x < +1: in favour, but prefer a different setup > [ ] 0: don't care either way > [ ] -1: I don't like this for reason __ > > >From me, +1. I think this might help increase subscription to the dev list. > > Vote closes after 24 hours, where if the numerical addition of all votes > > 0 will carry it. Any votes outside of the range -1 <= x <= +1 will be > considered donkey votes and omitted :) > > Cheers, > Brett > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] rearrange commits lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 Brett Porter wrote: | Hi, | | Alan proposed we use the standard that is used when setting up Apache | projects these days (we're still on our 2003 setup). | | Here it is in summary, elaborated into a bit more detail: | | 1) create [EMAIL PROTECTED], scm-commits, wagon-commits, | continuum-commits | 2) subscribe everyone on [EMAIL PROTECTED], [EMAIL PROTECTED], | post to the list to let people know what they are in for and | instructions to unsubscribe | 3) stop *-dev forwarding from commits lists | 4) reconfigure svn to put Maven commits to that list. I think Maven | plugin developers should keep across what's happening in the core, so | they can stay together, but the other subprojects remain separate. | 5) keep JIRA and repository reports on [EMAIL PROTECTED] | 6) send continuum/ci messages to the relevant commits list | 7) disband the old cvs lists | | Please vote: | [ ] +1: in favour | [ ] +0 < x < +1: in favour, but prefer a different setup | [ ] 0: don't care either way | [ ] -1: I don't like this for reason __ | |>From me, +1. I think this might help increase subscription to the dev list. | | Vote closes after 24 hours, where if the numerical addition of all votes | |>0 will carry it. Any votes outside of the range -1 <= x <= +1 will be | | considered donkey votes and omitted :) | | Cheers, | Brett | | | - | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFC+CXmK3h2CZwO/4URAnRjAJsEf4yuGCYVL7yy+rzKjbdUDnfA9wCfXG8I ka8WPMx1OzoG12Ys44n7tW4= =p0Fw -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] rearrange commits lists
On Tue, Aug 09, 2005 at 10:15:41AM +1000, Brett Porter wrote: [snip] > Please vote: +1 [snip] -- Trygve signature.asc Description: Digital signature
[vote] rearrange commits lists
Hi, Alan proposed we use the standard that is used when setting up Apache projects these days (we're still on our 2003 setup). Here it is in summary, elaborated into a bit more detail: 1) create [EMAIL PROTECTED], scm-commits, wagon-commits, continuum-commits 2) subscribe everyone on [EMAIL PROTECTED], [EMAIL PROTECTED], post to the list to let people know what they are in for and instructions to unsubscribe 3) stop *-dev forwarding from commits lists 4) reconfigure svn to put Maven commits to that list. I think Maven plugin developers should keep across what's happening in the core, so they can stay together, but the other subprojects remain separate. 5) keep JIRA and repository reports on [EMAIL PROTECTED] 6) send continuum/ci messages to the relevant commits list 7) disband the old cvs lists Please vote: [ ] +1: in favour [ ] +0 < x < +1: in favour, but prefer a different setup [ ] 0: don't care either way [ ] -1: I don't like this for reason __ >From me, +1. I think this might help increase subscription to the dev list. Vote closes after 24 hours, where if the numerical addition of all votes > 0 will carry it. Any votes outside of the range -1 <= x <= +1 will be considered donkey votes and omitted :) Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
