Re: Re: Proposal: Migrate unmaintained packages to github

FWIW, Migrating to github the old packages would be cool. I have not done much with the ones I have in PEAR (but they have not had bugs for years), and already have done the migration. Perhaps in the future have PEAR2 should have less dependency on a svn central repo, and maintain clones of the repos the developers can have on their own? Just another idea. Cheers -- Jesus M. Castagnetto <jesus@castagnetto.com> Web: http://www.castagnetto.com/ On Wed, Aug 24, 2011 at 07:46, Christian Weiske <cweiske@cweiske.de> wrote: > Hi Daniel, > > > > > 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 > > I follow reason 2 and would only migrate them when the need is apparent > (i.e. takeover) - it'd be too boring for me to migrate them all now. > > -- > Regards/Mit freundlichen Grüßen > Christian Weiske > > -= Geeking around in the name of science since 1982 =- > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >