PEAR issues vs Github issues - open question

So recently, a decent conversation picked up around PEAR core; getting it
stable; etc.

One comment stood out to me
>> I'd suggest at least documenting that PEAR lives @ github and list people
>> having push access to the repository.
>

It was also pointed out that there was a large number of bugs that are
resolved via github, but no obvious connection back to the original bug
report exists.

How would the community feel about increasing the use of github issue
tracking, and on some or maybe even all packages; going read only for new
pearweb based bug reports?


Previously we decided against swapping the bug tracker: it was seen as
valuable/a point of pride to have a PHP based solution.

I'd argue now that we've seen what github can do; and it's at least a 1:1
replacement for the core features we rely on.

Given the fact we're fairly quiet/short handed, and the bug tracking code
is a touch on the older side, this is a maintenance problem we needn't
necessarily have (there is occasional spam, odd issues with html escaping
bugs, etc).

Thoughts?