Git really encourages a more distributed, less centralized approach to
development, that allows the centers of gravity to move as they
evolve. This is a good and healthy thing in many contexts, perhaps
less so in others.
I'm not sure what the issue is with respect to the CLA. What prevents
you from representing a contribution as your original work because it
originated in GitHub? How does playing in an internal Apache sandbox
solve that?
It's important to recognize that not everyone in the CouchDB community
is necessarily part of the Apache community. Some are just friendly
visitors.
Cheers,
Bob
On Aug 6, 2009, at 8:24 AM, Curt Arnold wrote:
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.
