Migrate BTS to Github Issues

[gildor478]

This feature request has been migrated from artifact #1669 on forge.ocamlcore.org. It was assigned to user102.

user102 posted on 2016-09-01 08:39:30:

Requirement:

• Don't want 2 websites with 1/2 of bugs on them, this is confusing (i.e. if we migrate to Github, I don't want to keep forge BTS visible)

• Need to keep history, because I use it often to look for old bugs and analyse things (esp. useful for managing tests, so not possible to just close forge BTS and copy opened bugs to Github)

• Migration is a matter of time, not a matter of will, this migration needs to be done, it is just pending.

user22831 replied on 2016-09-19 16:24:38:

Keeping history without loss will be tough because github uses its user authentication system for comments and issue reports. Mapping from your user names to github ids will be tough if not impossible. If you want to go down this path, I recommend a hack, such as making each comment use your own github user, while perhaps keeping the original user name in the comment.

The github api can be manipulated from either https://github.com/mirage/ocaml-github or https://github.com/PyGithub/PyGithub/tree/master/github. Probably easier to just use python, since a simple script to process your 3 CSVs is all you really need. You want to make sure to add a Feature Request label to your feature requests, since github issues are bugs by default.

user102 replied on 2016-09-19 16:39:17:

1st point, I am trying to design a system to migrate issues of this BTS but also for all the other projects of the OCaml Forge.

The idea is:

• migrate issues as yourself
• register the mapping of Forge bug id to Github bug id.
• create a webpage for each user of the forge with a list of issues they were following (author or participants) on the Forge and allow them to be follow them on Github as well.