Re: PEAR Development on Github

I think the best plan is the maintainers of packages work as possible to migrate the packages to PEAR2. the packages without maintainers in PEAR need have new maintainers to migrate to PEAR2. One question: How to synchronize PEAR and PEAR2 version of a package? It's not confuse to pear users? like "where I get this package?" On Aug 5, 2011, at 10:59 AM, Jesus M. Castagnetto wrote: > I already asked about this some months ago when I was moving my code to > Github. > > They ones from PEAR and some modified for PEAR2 (and some that I did just > for fun) are all at: > > https://github.com/jmcastagnetto > > What would be the best solution now? Massive fork or cherrypick each > package? > > History and everything else has been (mostly) preserved. > > Cheers. > > -- > Jesus M. Castagnetto <jesus@castagnetto.com> > Web: http://www.castagnetto.com/ > > > On Fri, Aug 5, 2011 at 08:29, Brett Bieber <brett.bieber@gmail.com> wrote: > >> On Fri, Aug 5, 2011 at 6:56 AM, Igor Feghali <igor.feghali@gmail.com> >> wrote: >>> Hello Brett, >>> >>>> Right now we have two accounts, >>>> http://github.com/pear and >>>> http://github.com/pear2 — each are organizations >>>> which can have teams >> of >>>> developers with push access to repositories. >>> >>> can we use those repositories to host proposed codes or only current >> packages ? >> >> I would say, only current PEAR packages can be moved to >> github.com/pear. PEAR2 proposals are welcome on github.com/pear2. >> Because the proposal process is different for PEAR vs PEAR2, each is >> managed differently. There's no pepr process required before creating >> or releasing a PEAR2 package. The PEAR2 review process is required >> before a package can be released as stable, but not before any code is >> accepted. >> >> -- >> Brett Bieber >> >> -- >> PEAR Development Mailing List (http://pear.php.net/) >> To unsubscribe, visit: http://www.php.net/unsub.php >> >>