Re: [PEAR-QA] Re: pear Jenkins
[email protected] ("Daniel O'Connor") Mon, 2 Apr 2012 16:59:47 +0930
| Newsgroups | php.pear.qa |
|---|---|
| Message-ID | <CAJsZyFC6Sf10Xp=nhqVPPF8o4Ez77TGmfouU=b+2dHH8guoM4Q@mail.gmail.com> |
On Sun, Apr 1, 2012 at 5:00 AM, Daniel Convissor < [email protected]> wrote: > Hey Folks: > > It seems to me that the PEAR repository should be migrated to > git.php.net just like the PHP repository was. And stuff on GitHub > should be brought back into PHP's server. > > I guess each package should be a separate Git repo under a pear/ or > pear/packages "directory." > > I'm not so sure on that approach. I mean http://git.php.net/ is a bit spartan - we'd lose pull requests, commit hooks, etc. I'm most worried about the ease-of-contributing - github works pretty well with pull requests and the review cycle. IMO We need all of the extra hands we can get from external contributors. If those features are there in some fashion, it's not obvious to me from a ~30 look. The second bit I'm worried about is the karma system (accepting new contributors into the fold). We've seen that it's a bit hard with the SVNROOT side of things to grant karma - a select few have access, a different select few can mint accounts; add a bit of workload and the system tends to drift apart / lag for weeks. Github at the moment it's one click to administrate, self register for accounts. There's still a core group of people with their hands on the controls, but TBH I think we could incrementally extend that group to be more of "the regulars" rather than "the elected few". I'd be open to a mirroring approach (svn.php.net -> git.php.net -> mirror to github or svn.php.net -> mirror to github); but it seems like a lot of effort.