Vladimir Prus
2004-May-05 01:37 UTC
[LLVMdev] Open Source Contributions (was Re: Benchmarks)
Chris Lattner wrote:> > Right, but you'd need HTTP/FTP server. Not a problem for *me*, but lots > > of folks are behind firewalls and can't do that. > > Sure. I can't imagine that there is a wonderful solution other than this > though. In particular, how can you do distributed development without it? > The whole idea is to reduce the need for a completely centralized > development model. Ideally, the UIUC servers would just be the "official" > tree: lots of development could happen publically in trees that are not on > our servers. When the development is done, or in a good state, it could > be merged into the official tree, and be released in the standard > releases.Why do you really need distributed development? The possible problems with centralized development are 1. The server might be often down. 2. There's too much number of active branches, so nobody understand what's going on. 3. You can't commit while you're on a plane. I don't think first two points are that important, and I never being on a plane so can't comment on the third. Ok, anyway, you decide. - Volodya
Vladimir Prus <ghost at cs.msu.su> writes:> Why do you really need distributed development? The possible problems with > centralized development are > 1. The server might be often down. > 2. There's too much number of active branches, so nobody understand what's > going on. > 3. You can't commit while you're on a plane.Replace 3 with "You have no permanent internet connection, or you are behind a firewall, so you can not access the server at all (no diffs, no logs, nothing)". BTW, before considering arch too seriously, you should check how mature/stable it is. Last time I heard about it, Tom Lord was pleading for help and funding to finish Arch. OTOH, Subversion is just a sane CVS. No distributed repositories. With CVS, some people keep a copy of the main repository on their local computers. That's what some gcc developers do. They rsync from time to time with the remote repository. I don't know how serious the incoveniences are with this approach. BitKeeper, due to its license, is a no-no, IMHO. [snip] -- Oscar
On Wed, 5 May 2004, Oscar Fuentes wrote:> Vladimir Prus <ghost at cs.msu.su> writes: > > > Why do you really need distributed development? The possible problems with > > centralized development are > > 1. The server might be often down. > > 2. There's too much number of active branches, so nobody understand what's > > going on. > > 3. You can't commit while you're on a plane. > > Replace 3 with "You have no permanent internet connection, or you are > behind a firewall, so you can not access the server at all (no diffs, > no logs, nothing)".And #4: it makes permissions on the server much easier to deal with.> BTW, before considering arch too seriously, you should check how > mature/stable it is. Last time I heard about it, Tom Lord was pleading > for help and funding to finish Arch.Yes, I think that Tom Lord is the single biggest problem with Arch. :) OTOH, Arch is now a gnu project, so perhaps its better now. I any case, everything that I know about it is dated. :)> OTOH, Subversion is just a sane CVS. No distributed repositories. > > With CVS, some people keep a copy of the main repository on their > local computers. That's what some gcc developers do. They rsync from > time to time with the remote repository. I don't know how serious > the incoveniences are with this approach.Yeah, that's a solution, but it's such a hack! :)> BitKeeper, due to its license, is a no-no, IMHO.Agreed. -Chris -- http://llvm.cs.uiuc.edu/ http://www.nondot.org/~sabre/Projects/
Oscar Fuentes wrote:> Vladimir Prus <ghost at cs.msu.su> writes: > > Why do you really need distributed development? The possible problems > > with centralized development are > > 1. The server might be often down. > > 2. There's too much number of active branches, so nobody understand > > what's going on. > > 3. You can't commit while you're on a plane. > > Replace 3 with "You have no permanent internet connection,Ok, I guess I'm spoiled by broadband internet ;-)> or you are > behind a firewall, so you can not access the server at all (no diffs, > no logs, nothing)".Since Subversion uses standard HTTP port, this should be less of a problem.> OTOH, Subversion is just a sane CVS. No distributed repositories.FWIW, there's subversion-based tool called SVK (http://svk.elixus.org/), which is advertised to be distributed, but I never used it, so can't realy comment on its merits. - Volodya