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

On Sunday, September 9, 2012 at 10:24 AM, Bertrand Mansion wrote:

>  
> Le 7 sept. 2012 à 14:48, Alexey Borzov a écrit :
>  
> > Hi,
> >  
> > On 29.08.2012 12:14, Christian Weiske wrote:
> > > 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.
> > >  
> > > What do you say? Do you have objections against it? Do you favor it?
> >  
> > +1 from me.
> >  
> > Git is supposed to be, well, distributed, so I don't understand this emerging github monoculture.
>  
>  
> Thanks Christian for starting the discussion, the only Subversion-managed code I have left is from Pear and it pretty annoying to use.
>  
> +1 from me as well.
>  
> -1 for having Github as a full mirror because :
>  
> - Github is not open source
> - It seems complex to deal with administrative tasks for a group like Pear

If this is really the most complex bit, I am wondering why no one stepped up to automate this using their API. Or is there anything missing?  
> - Code in the Github pear organization is not visible on main Github account

Can you elaborate?  
> - I receive many mails from Pear organization about projects I am not concerned about

You can control which notifications you want to receive.

Just go on a project's page and disable notifications – also go here:
https://github.com/settings/notifications
> - It duplicates Pear features like the bug report tool, wiki

You can enable/disable these.
> - It lacks mail diffs and feature evolution depends on Github

I would say that it's possible to set this up and that we as a project/group of individuals will have a very hard time to compete with Github on this.

Let alone the possibility to use travis-ci and get PRs tested is a huge a plus for me, which is why I am not going to go back.  
>  
> So moving everything back to git.php.net (http://git.php.net) sounds like the best idea. Then, individually, we can do what we want and use Github or Gitorious or Google Code, etc if we want. And if we have time, we can build something around git.php.net (http://git.php.net) to make it even more useful (pull requests, history browser, comments in commits ...)

Lots of projects have stated in the past how many contributions they got from hosting at Github. I realize that mono-culture is not a good thing and that Github being commercial entity is also a problem for some people, but I still fail to understand how this is an actual real-world problem since Sourceforge, Gitorious or Google Code are backed by commercial entities as well. Even servers donated to php.net are sponsored by some commercial organization.

You mentioned – if we have time, we'll make it more useful. And until we have this time PEAR will just render itself obsolete because no one feels compelled to contribute code if it's too complicated?

I just don't see how or where all these contributions to build out our own GIT setup will come from or let alone who will step up when stuff doesn't work.

Last but not least, contributing to PEAR is not a privilege – it should be as easy as possible.

Anyway – to each their own. Do whatever you guys want or the majority is for. I'd like to ask you guys to not move any code I work on/maintain as I prefer github.com for this and won't have time to build out tools which are already available.

Till