We've been offered the Eclipse plug-in for Geronimo. You can go back
and read the threads where the source was discussed, and some of the
ideas that Sachim has for it..
I'll start a vote on accepting it after we come to some agreement on
if we should establish subprojects, and if so, should tooling be
one. I think that we should accept and establish tooling as a
subproject.
Putting tooling aside for a sec, for something we have a subproject,
I think we would :
1) Setup a parallel SVN tree for it, say geronimo/$foo/
2) It would have it's own released artifacts and independent release
cycle.
3) It would be wholly under the control and oversight of the Geronimo
PMC
4) It would have it's own webpage on the site (I imagine left nav
entry for it under a Subprojects heading)
5) All geronimo committers would have commit access
The remaining question, as always, is the general one about having
restricted ACLs for it or not for people that come with the code in
the case where code and people are offered together.
I would be happy either with extending trust with new people that
they work on the code they came with and work with existing
committers on other parts until existing committers are satisfied, or
starting some system of ACLs.
Thoughts?
geir
--
Geir Magnusson Jr +1-203-665-6437
[EMAIL PROTECTED]
