-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On May 3, 2007, at 11:37 AM, Fil wrote:
write privileges are a big sticking point for community participation in code development, to which I agree. However, he also concluded that dvcs's are /bad/ for open source because they encourage private branches, and everything should be done in the open.
My own experience with SPIP (www.spip.net, a project now 7 years old and that I "guide") is that there was a lot a frustration when we had a 3-devs SVN system. The "big guys" spent time evaluating (and rejecting) proposals that were not "good enough".
Two years ago we opened a secondary SVN server, named "spip-zone", with a motto of "anything that's free software and relates to SPIP". It now has 150+ devs and thousands of projects positively blossom (to quote Chairman Mao).
This has been a place where shy developers have been more able to express themselves, and now the "core" team has expanded, integrating some of these developers. But most surely the "core" is more focused, and frustration has almost disappeared.
I think we can do the same thing, without all the pain that svn
brings with it. Remember that in bzr (and I'm sure hg is the same),
branches are /really/ cheap. In fact, it's encouraged to keep your
branch changes small, and not worry about branch proliferation.
Small focussed branches make it easier to review, and merge into the
main line.
In fact, because you don't need to coordinate with /me/ to create and
publish branches means anyone can do it. I envision that the really
great patches will be easier to merge, and the really great
developers will be easier to promote.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRjoEi3EjvBPtnXfVAQKFCAQAgcNkIaot1Hlv+DffA9RlTk5njvb8bOo0 ViELnkoJQxfb4ocBexw6QA09kpDYm3HSYXAN9KUq3BZyH87aMkUSK8Ck1iLGhfye q4oLOdy0/hEE/AHiAtLxYWwb79Wv7d5DoGkWy+aweiZ4FNtvU02Qcqg5Uqz34hqQ AJNPefSceFI= =bj1Z -----END PGP SIGNATURE-----