You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2004/07/23 07:00:22 UTC
plugin release managers/lead developers
Hi all,
I know we discussed/decided this some time ago but I'm not sure of the level of
completeness we got to. Can I ask that everyone that feels they own a plugin
make themselves the JIRA project lead and send a list to the list (if we
disagree, we can sort it out then).
Anything left over will be put up for grabs.
Anything still left over will be relegated to the sandbox. This means it is no
longer distributed with Maven. If there is demand, the code will still be in CVS
as it was so it can be moved back into the fray for further releases, and old
releases can be plugin:download'ed.
These only apply to Maven 1.x plugins - not any maven-components or mojos.
Thanks!
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: plugin release managers/lead developers
Posted by David Jencks <da...@coredevelopers.net>.
Although Dion very kindly committed the original rar plugin, since you
wish to be lead of all the other j2ee artifact generating plugins, it
might make sense for you to take that one as well.
BTW all suggestions for improvements would be welcome:-)
thanks
david jencks
On Friday, July 23, 2004, at 01:41 AM, Emmanuel Venisse wrote:
> I'm actually the lead of :
> - jbuilder
> - jcoverage
> - jnlp
> - jira
>
> I would like to take the lead on :
> - changelog (for use maven-scm when it'll be ready)
> - scm (for use maven-scm when it'll be ready)
> - jar (for use plexus-archiver when it'll be ready)
> - war (for use plexus-archiver when it'll be ready)
> - ear (for use plexus-archiver when it'll be ready)
> - ejb (for use plexus-archiver when it'll be ready)
> - dist (for use plexus-archiver when it'll be ready)
> they'll be mojo plugins
>
> Emmanuel
>
>
> ----- Original Message -----
> From: "Brett Porter" <br...@apache.org>
> To: "Maven Developers List" <de...@maven.apache.org>
> Sent: Friday, July 23, 2004 7:00 AM
> Subject: plugin release managers/lead developers
>
>
>>
>>
>> Hi all,
>>
>> I know we discussed/decided this some time ago but I'm not sure of the
> level of
>> completeness we got to. Can I ask that everyone that feels they own a
> plugin
>> make themselves the JIRA project lead and send a list to the list (if
>> we
>> disagree, we can sort it out then).
>>
>> Anything left over will be put up for grabs.
>>
>> Anything still left over will be relegated to the sandbox. This means
>> it
> is no
>> longer distributed with Maven. If there is demand, the code will
>> still be
> in CVS
>> as it was so it can be moved back into the fray for further releases,
>> and
> old
>> releases can be plugin:download'ed.
>>
>> These only apply to Maven 1.x plugins - not any maven-components or
>> mojos.
>>
>> Thanks!
>> Brett
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: plugin release managers/lead developers
Posted by Emmanuel Venisse <em...@venisse.net>.
I'm actually the lead of :
- jbuilder
- jcoverage
- jnlp
- jira
I would like to take the lead on :
- changelog (for use maven-scm when it'll be ready)
- scm (for use maven-scm when it'll be ready)
- jar (for use plexus-archiver when it'll be ready)
- war (for use plexus-archiver when it'll be ready)
- ear (for use plexus-archiver when it'll be ready)
- ejb (for use plexus-archiver when it'll be ready)
- dist (for use plexus-archiver when it'll be ready)
they'll be mojo plugins
Emmanuel
----- Original Message -----
From: "Brett Porter" <br...@apache.org>
To: "Maven Developers List" <de...@maven.apache.org>
Sent: Friday, July 23, 2004 7:00 AM
Subject: plugin release managers/lead developers
>
>
> Hi all,
>
> I know we discussed/decided this some time ago but I'm not sure of the
level of
> completeness we got to. Can I ask that everyone that feels they own a
plugin
> make themselves the JIRA project lead and send a list to the list (if we
> disagree, we can sort it out then).
>
> Anything left over will be put up for grabs.
>
> Anything still left over will be relegated to the sandbox. This means it
is no
> longer distributed with Maven. If there is demand, the code will still be
in CVS
> as it was so it can be moved back into the fray for further releases, and
old
> releases can be plugin:download'ed.
>
> These only apply to Maven 1.x plugins - not any maven-components or mojos.
>
> Thanks!
> Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: plugin release managers/lead developers
Posted by Carlos Sanchez <ap...@carlos.cousas.net>.
> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@pivolis.com]
> Sent: Friday, July 23, 2004 10:02 AM
> To: 'Maven Developers List'
> Subject: RE: plugin release managers/lead developers
>
> - aspectj - It seems that Carlos is more active so I wouldn't
> mind if Carlose stepped in as lead dev :-)
Ok, I agree.
To any jira admin, remember to allow plugin developers to create versions as
we have discussed in a thread before.
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: plugin release managers/lead developers
Posted by Vincent Massol <vm...@pivolis.com>.
I am currently marked as project lead for the following:
- abbot
- announcement
- ant
- aspectj
- aspectwerkz
- caller
- changelog
- changes
- checkstyle
- clover
- dashboard
- deploy
- ear
- eclipse
- ejb
- jboss
- jetty
- junitreport
- multichanges
- site
I am kinda active on most except for the following that I haven't touched in
ages (I don't even know why I am marked as lead on those):
- ant
- changelog
- deploy
- junitreport
- site
Thus I would like to remove myself from project lead on those projects.
Also, I would prefer if some other more active developers stepped in for the
following projects:
- checkstyle
- ear
- eclipse
- ejb
Lastly:
- aspectj - It seems that Carlos is more active so I wouldn't mind if
Carlose stepped in as lead dev :-)
- caller - I think it should be moved to sandbox or deleted as it has not
caught on.
Thanks
-Vincent
> -----Original Message-----
> From: Brett Porter [mailto:brett@apache.org]
> Sent: vendredi 23 juillet 2004 07:00
> To: Maven Developers List
> Subject: plugin release managers/lead developers
>
>
>
> Hi all,
>
> I know we discussed/decided this some time ago but I'm not sure of the
> level of
> completeness we got to. Can I ask that everyone that feels they own a
> plugin
> make themselves the JIRA project lead and send a list to the list (if we
> disagree, we can sort it out then).
>
> Anything left over will be put up for grabs.
>
> Anything still left over will be relegated to the sandbox. This means it
> is no
> longer distributed with Maven. If there is demand, the code will still be
> in CVS
> as it was so it can be moved back into the fray for further releases, and
> old
> releases can be plugin:download'ed.
>
> These only apply to Maven 1.x plugins - not any maven-components or mojos.
>
> Thanks!
> Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: plugin release managers/lead developers
Posted by Eric Pugh <ep...@upstate.com>.
I'd volunteer to take Hibernate and CruiseControl if the current leads don't
want to keep the role. And, if no one else is chomping at the bit, Eclipse.
All three plugins are near and dear to my heart!
Eric
> -----Original Message-----
> From: Brett Porter [mailto:brett@apache.org]
> Sent: Friday, July 23, 2004 7:00 AM
> To: Maven Developers List
> Subject: plugin release managers/lead developers
>
>
>
>
> Hi all,
>
> I know we discussed/decided this some time ago but I'm not sure
> of the level of
> completeness we got to. Can I ask that everyone that feels they
> own a plugin
> make themselves the JIRA project lead and send a list to the list (if we
> disagree, we can sort it out then).
>
> Anything left over will be put up for grabs.
>
> Anything still left over will be relegated to the sandbox. This
> means it is no
> longer distributed with Maven. If there is demand, the code will
> still be in CVS
> as it was so it can be moved back into the fray for further
> releases, and old
> releases can be plugin:download'ed.
>
> These only apply to Maven 1.x plugins - not any maven-components or mojos.
>
> Thanks!
> Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org