On 30 Aug 06, at 11:13 AM 30 Aug 06, Jochen Wiedmann wrote:
Jason van Zyl wrote:
That's easily remedied. You don't have it because you've never
asked. In the last while we have taken the same approach as we're
taking here in that anyone who wants access to the sandbox has
been given it so they can easily work on plugins. We know not
having commit access hinders collaboration so we've open things up
a bit, at least for sandbox access.
That would certainly help. But before I ask, let's continue this
discussion ...
I don't think it's onerous. Ask some of the other people who have
joined Mojo in the last couple days. It probably took them 5
minutes to get setup.
It's not that difficult, of course. It's possibly more a question
of "feeling at home", to be honest.
In many cases because of licensing we just can't host them here, but
moreso because we're trying not to collect every last plugin here at
Apache. It doesn't matter with m2 where the plugins come from.
If the plugin warrants a release then it would graduate from the
sandbox. Meaning it's got some decent tests and passes the docck
minimum requirements. You can pump out as many snapshots as you
want though.
That's a policy I'd like to see for the "Maven Sandbox for Apache
Committers" (MSAC) too. But what about the second, third, ...
release? Can I (or we) as the plugins author(s) push the release?
How many people do we have to nag? Will I have to wait? Do I need
to find someone who does the work for me or will I be able to do it
myself, after a positive vote?
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.
IMO, these questions are essential for the usefulness of the MSAC.
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.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Jason van Zyl
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
