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

On Wed, Aug 29, 2012 at 3:14 AM, Christian Weiske <[email protected]>wrote:

> 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 agree that a we need to maintain a copy/mirror that we have complete
control over, but before we move the reference repositories away from
GitHub, it might be worth evaluating the amount of external contributions
github has provided.

PEAR org has had 100 pull requests (PRs).
PEAR2 has had 24 PRs,
Pyrus has had 31 PRs.

I'm not in favor of a change which reduces the amount of contributions or
how easy it is to merge those contributions in.

The second item is the code review process GitHub offers when pull requests
are used. Yes, email notifications from git.php.net can provide the commit
info, but that does not give others the opportunity to review the code
before it has been merged in to the master repository.

A backup is essential, no question about that, but for the long-term
success of these projects we also need contributions, visibility, and
community interaction. I believe GitHub (at the moment) is the best service
for achieving those goals.

-- 
Brett Bieber