Re: [PEAR-DEV] Hosting PEAR's git repositories on git.php.net

On Wednesday, August 29, 2012 at 10:14 AM, Christian Weiske wrote:

> Hi,
>  
>  
> Nearly a year ago we moved most of the svn.php.net/pear (http://svn.php.net/pear) packages to
> Github. We were the first php.net (http://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 (http://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 (http://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.

I don't believe this is going to happen. Besides, what keeps us from mirroring our Github organizations somewhere else?
> - 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 (http://git.php.net).
> - We would get back proper commit mails with diffs

I am not sure if I see more email I don't have time to read as an advantage. I prefer the interface a lot.  
>  
>  
> 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.

This feature has lots of implications. It's not just the maintainers who have to figure out four git commands to merge a PR vs one click, for me it's also the code review which comes with the PR on github, fast servers etc..

Also, for a PR to "happen", the contributors will have to know how to send one as well. Github mono-culture could be considered an issue, but I don't see self-hosting as a viable alternative.
Or well, I don't see a reason to make contributing and maintaining more painful than it really has to be. It's not impossible to rebuild interfaces, etc., but I am not sure if anyone of us has the time.

Btw, it's also possible to pull in a PR from one git origin into another. Decentralized version control – this is what it's all about.  
>  
>  
> What do you say? Do you have objections against it? Do you favor it?
Maybe we figure out how to mirror back and forth so people can use whatever git they want?

Otherwise, I am against moving it all to php.net at this point. I more prefer things where they are.

Till