Re: Very old bugs and requirements

On Thu, Aug 25, 2011 at 8:41 PM, Stelian Mocanita <
[email protected]> wrote:

> Hello all,
>
> I just got back in town, with little bit more delay than expected and went
> through all you guys discussed here.
>
> I believe that going through old packages and trying to reach the reporters
> and get a status of a particular report is a viable solution, we could even
> automatize this process so we don't put in loads of men hours to get there.
>
> The Github migration automation is all so cool, having the amount of
> contributions on github versus pear. If noone is working, or planning to
> work on this, I am volunteering as long as we can start a discussion thread
> on this topic and figure out how and what exactly we want.
>
>
https://github.com/pear/pear-svn-git/blob/master/package-to-git.sh achieves
quite a lot of it. From my perspective; we need:
 1. A report of 'packages, unmaintained, not hosted by github' out of
pearweb on a frequent basis (that can be easily turned into a list of
commands to execute involving the package-to-git script)
 2. A button in pearweb to update the relevant DB bits (package source
location); or a output to an .sql for the scenario where X packages get
migrated at once.
 3. http://develop.github.com/ has an API in some areas - is there something
which can create the relevant repository? relevant team in pear? Can this be
trivially added to the .sh script?