Hosting PEAR's git repositories on git.php.net
[email protected] (Christian Weiske)
| Newsgroups | php.pear.dev |
|---|---|
| Message-ID | <20120829101438.3d4dc4d9@cyberdyne> |
Hi, Nearly a year ago we moved most of the svn.php.net/pear packages to Github. We were the first php.net project to move to git, but in the meantime other projects - including php-src - also moved to git. PHP has its own git server now, http://git.php.net/ - it is used as primary repository host now, and github is only a mirror. I'd like to see that for PEAR, too: Using git.php.net as main repository server for PEAR packages, PEAR2 packages, Pyrus and infrastructure code. Github would only be a mirror of the git.php.net code. The reasons I see for this: - Github is an entity we do not have any control over. Their Terms of Services[1] state that they can delete and repository and user/organization at their will, without any notice or a way to get the code back. - Karma (user rights) management is tedious with github, given that we have over 400 repositories. The karma file we had for svn and CVS was easier to maintain, and will be again with git.php.net. - We would get back proper commit mails with diffs The only downside I see is that merging pull requests isn't a one click action anymore, since the github repository is only a mirror, and no commits may be made to it directly. What do you say? Do you have objections against it? Do you favor it? I volunteer to do the transition and get everything setup on php.net and github side (of course together with anyone who would like to help). [1] https://help.github.com/articles/github-terms-of-service -- Regards/Mit freundlichen Grüßen Christian Weiske -= Geeking around in the name of science since 1982 =-