Jason van Zyl wrote:
The PMC must approve a release, and anyone doing a release would most
likely be on the PMC but I don't believe that is a strict requirement.
So if you were very motivated to release the JAR plugin and went through
our standard process to release it then I would support that option.
Even for people who passed in/out of sustained participation and just
wanted to get a release done I would like to harness that motivation.
Generally we like people to show a sustained level of participation
before we nominate someone for the PMC.
So you could do all the work and prepare the work and we could work out
how to do a release. The preparation for the release is the hard part,
so if you did the work and it was sitting in SVN we could release it
quickly whether it was you or someone else. If you went through this
process once you would most likely be nominated as a committer anyway.
[...]
The goal is to get people integrated into our process and encourage
contributions and collaboration so we would adapt as necessary to attain
that goal. For example if you did all the work for the foo-plugin then I
would support you doing a release for it. You're interested and it
alleviates the burden from one of the existing developers so I see no
downside.
Understood and agreed. Thanks also to Brett for acknowledging this.
However, one last question: I do read your words mainly targeted on
work on "official" Maven plugins. Is that so (in which case I understand
that even Apache committers should still use the Mojo project to create
new plugins) or do I get you wrong (in which case I assume that your
words apply to new plugins as well)? I am asking, because the PMC will
(quite understandably) be not so much interested in having a vote on
maven-yet-another-one-plugin every week?
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
