While I'm bringing up contentious issues, use of github for a sandbox
for developing significant modifications to CouchDB makes me uneasy.
If I start something on github and accept contributions and ideas from
other uses, I can't represent the eventual patch as my original work
(as required by the CLA). Also, it reduces the visibility (barring an
explicit opt-in) of the development from the radar of the PMC and
community. Other ASF projects have created "sandboxes" in their SVN
for experimental work and the threshold for commit access to the
sandbox could be lower than the trunk (still would require CLA and an
Apache account). Any Apache committer could use Apache Labs, but
since that is not developed with the oversight of the community that
still needs a pass through the Incubator. Having a sandbox or labs
branch in the CouchDB SVN would provide a location for non-trunk
development that is still under the oversight of the PMC and community.
- Uneasiness with use of github for experimentation Curt Arnold
- Re: Uneasiness with use of github for experimentation Robert Dionne
- Re: Uneasiness with use of github for experimenta... Jan Lehnardt
- Re: Uneasiness with use of github for experim... Stephan Wehner
- Re: Uneasiness with use of github for exp... Adam Kocoloski
- Re: Uneasiness with use of github for experim... Elliot Murphy
- Re: Uneasiness with use of github for experimentation Mikeal Rogers
- Re: Uneasiness with use of github for experimenta... Paul Davis
- Re: Uneasiness with use of github for experim... Dirkjan Ochtman
- Re: Uneasiness with use of github for experim... Jan Lehnardt
- Re: Uneasiness with use of github for exp... Elliot Murphy
