Re: [RFC] Choosing a distributed version control system for PHP (or not). Call for Participation.

Stas Malyshev wrote:

Actually the real question here is WHY create a fork on github at all? The copy

Pull requests, for one. Push/Pull from local copy?

My point was that many of the forks currently ON github are simply not required?

you are working on LOCALLY is the fork that you are developing on? Much of the stuff on github and the other DVCS server sites is redundant? You only need to

I think you confusing "not absolutely required" and "redundant" :) Of course you could do without any infrastructure github provides. But it makes life so much easier. Especially when you are working in a team bigger than 1 person. The TEAM has a master copy on github or better still git.php.net, but you don't need 10000 other copies on github as well? I don't like the code Drupal produce, but the framework for code management is only let down by being git based :) Sandboxes and development branches are the right way to go, but could actually be provided in a DVCS agnostic way on a php.net framework? hg.php.net + git.php.net in parallel ... with the existing packaged distributions for those who do not need code access?

-- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php