On 2011-08-12, Lester Caine <les...@lsces.co.uk> wrote: > Ferenc Kovacs wrote: > > > But you can't call it PHP anymore due to the license, where as with a > > > > DCVS with people having forks on publically accessible repositories, > > > > everybody is basically violating the license. > > > > > > you can rename your fork on github: > > https://github.com/Tyrael/forphx > > usually people don't do this, as they don't want to maintain a > > competing project, they only fork it for having their own repo to > > develop into until they are done and then send a pull request. > > Actually the real question here is WHY create a fork on github at all? > The copy 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 publish your local changes to > other developers who are working with you not to the whole world?
And how do you publish those changes? How do you get review? Yes, you can send patches, but it's often easier to point a person to a repository and branch, and let the reviewer -- or reviewers -- decide how to review -- a diff between the canonical repo and the change branch, using a web-based review system such as GitHub offers, etc. The web-based tools GitHub and BitBucket should not be discounted -- having the ability to have comment-threads per line of code is very useful for keeping the review targetted as well as easily identifying code that may need tuning. -- Matthew Weier O'Phinney Project Lead | matt...@zend.com Zend Framework | http://framework.zend.com/ PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
