Switch to Github issues

[Chris Hanson]

I was going to file an issue with CFFI, and wound up having to come here to do so. It seems weird to me to have the issue tracker for CFFI hosted at Launchpad.net but the project hosted at Github.

Trust me, I'm not one of those "everything must use Github no matter what" people, but when a project is hosted there it seems like it would be most logical to take advantage of its issue tracker, pull request integration, etc. too.

[Luís Oliveira (luismbo)]

Maybe. Is it worth the trouble to migrate this bug database to GitHub,
though?

On Sat, Jan 28, 2017, 22:30 Chris Hanson <email address hidden> wrote:

> Public bug reported:
>
> I was going to file an issue with CFFI, and wound up having to come here
> to do so. It seems weird to me to have the issue tracker for CFFI hosted
> at Launchpad.net but the project hosted at Github.
>
> Trust me, I'm not one of those "everything must use Github no matter
> what" people, but when a project is hosted there it seems like it would
> be most logical to take advantage of its issue tracker, pull request
> integration, etc. too.
>
> ** Affects: cffi
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to CFFI.
> https://bugs.launchpad.net/bugs/1660081
>
> Title:
> Switch to Github issues
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cffi/+bug/1660081/+subscriptions
>

[Chris Hanson (eschaton)]

Maybe, if they have a straightforward way to import the bugs and preserve the numbering.

[Chris Hanson (eschaton)]

Actually, it's probably worthwhile without preserving the numbering. It might even be worthwhile to enable git issues immediately, prior to migrating existing bugs.

[Luís Oliveira (luismbo)]

Keeping the launchpad bug numbers in each issue's description or something
would be sufficient, as long as it's searchable. Enabling GitHub issues
immediately would mean having two bug trackers simultaneously (even if it's
one for new bugs and another for old ones). I don't think that's at all
desirable.

On Sun, Jan 29, 2017 at 9:25 PM Chris Hanson <email address hidden>
wrote:

> Actually, it's probably worthwhile without preserving the numbering. It
> might even be worthwhile to enable git issues immediately, prior to
> migrating existing bugs.
>
> --
> You received this bug notification because you are subscribed to CFFI.
> https://bugs.launchpad.net/bugs/1660081
>
> Title:
> Switch to Github issues
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cffi/+bug/1660081/+subscriptions
>

[vydd (vidovicd)]

I think a good temporary solution would be to link to this bug tracker from repo's README.

[Stelian Ionescu (sionescu)]

I finally found an importer that works without crashing and I did a test run: https://github.com/sionescu/test-lp-import/issues.

The content is all there, including back-links to patches on Launchpad. The only inconvenience is that all posts appear to be created by me in the Github UI, although the author is linked in the post footer.

To me, that is enough to migrate to Github and I can do it as soon as possible.