Lots of good comments, especially appreciate those from Martin, Henry and Geir.

My suggestions...

* Multiple user lists.  One primary dev list, possibly distinct dev
lists for major distinct subprojects. (example: Velocity/Velocity
Tools should share a dev list, but Click, if it joins, would likely
have a separate dev list).

* Shared svn and JIRA access across the TLP.  Just makes sense.

* I don't see a need for new Velocity committers to get Jakarta
privileges, but I wouldn't mind keeping mine.

* Doesn't really matter to me who's chair.  Should be someone active
in the project, doesn't have to be a primary coder.  Ideally we could
rotate.

Maybe it's just my guilty concience speaking, but I would feel better
about this if we could deal with the release around the same time.

WILL

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to