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]
