Re: [PEAR-QA] Proposal: Migrate unmaintained packages to github

On Tue, Aug 23, 2011 at 6:18 PM, Daniel O'Connor
<[email protected]> wrote:
> We've got a number of unmaintained packages:
> http://pear.php.net/qa/packages_orphan.php
>
> We regularly get requests from folks to take over packages; but it's a bit
> of a hassle to greet them; assess them; get them karma; etc.
> A lot of us are comfortable with git. The migration path is trivial
> (git-svn; update package source link; remove from pear svn); with the
> exception of losing the CI service without a bit of mucking around.
> Git removes much friction from accepting patches/etc; once you get over the
> initial learning curve.
>
> So... what would be compelling reasons *not* to migrate packages?
>
> All I've got so far:
> 1) Validate_* have a unique dir structure which would be a pain to untangle.
> 2) There's a lot of packages; most of them without open bugs; so why muck
> around with them

3) How do we keep track of bugs.

I'd be in favor of moving any package that doesn't have open issues
immediately. I think bugtracker integration is a compelling reason to
not move source — until we can manage to keep bugs in one place, or
move them over to github issues.

You're correct that accepting new devs is a time drag, and honestly
that is what is taking up the little time volunteers have. As you've
stated, this would hopefully reduce that.

-- 
Brett Bieber