So we're considering adding some new features to Codehaus...
Projects want the ability to
- let users commit code, but keep said code segregated from their code base
- identify who committed changes
- allow users to write pages in Confluence
- New users will be able to apply for contributor access.
- Contributor access may be granted by any developer or despot (as opposed to developer access only being grantable by despots)
- Contributors may be required to click through a CLA (per project configuration)
- Contributors will gain write access to a new -contrib SVN repository (CVS will not be supported - time to upgrade folks).
- URL: https://svn.codehaus.org/<project>-contrib
- It's VERY hard to block access to parts of a Subversion repository once SVN+SSH access is granted - hence the separate repository.
- Developers will have write access to the -contrib repository
- New subversion repositories will be indexed in Fisheye
- I don't use m2 so I'm not really sure what the best option is here. Would allowing them write access to <main project id>.contrib be sensible (Brett Porter or similar should be able to give some clarity here).
- What are the legal impacts of letting random users release artifacts ostensibly as your project - I'd wager this was bad!
- No new mailing lists; I would entertain the notion of a -contrib list, but am currently resisting this on the basis that -dev should be sufficient.
- Contributors will have limited write access to pages in Confluence - more than enough for everyday work.
- Contributors will be able to create new pages and edit existing ones
- A NEW SPACE WILL NOT BE CREATED FOR CONTRIBUTORS
- Contributors will have standard access to Jira
- A NEW PROJECT WILL NOT BE CREATED FOR CONTRIBUTORS
- Xircles (aiming to get this implemented in the next day or so - once we've had a bit of feedback - there's quite a few changes under the hood to do this)
- Subversion (fairly straightforward implementation once Xircles is done)
- Fisheye (very straightforward implementation once Xircles is done)
- Confluence (most of the code is already written, just need to start cleaning up rogue space permissions)
- Jira (nothing to do)
- Mailing lists (nothing to do)
All feedback is welcome.
This will initially be implemented as a proof of concept for Mule and Mojo.