2016-02-07 2:54 GMT+01:00 Bryce Harrington <bryce@...961...>:
On Fri, Feb 05, 2016 at 09:16:36AM -0800, mathog wrote:
On 05-Feb-2016 05:40, Eduard Braun wrote:
In general I would avoid splitting the code repository from the bug tracker as those two are closely related and often intertwined. It hinders efficiency a lot when tracking bugs elsewhere.
I agree with that - everything in one place. Moving to git is fine so long as the entire history of the project makes the transition, all the bugs, all the revisions, and so forth. There shouldn't be anything "left behind" on launchpad. Not that I have any idea how one would go about doing this sort of migration, never having used git except to download entire projects for a local build.
The git repository itself should be straightforward. I've done bzr -> git on a bunch of trees without any trouble. I've not attempted on Inkscape itself, but others have already reported they've experimented and it went straightforward.
Bugs I think will be much harder to transition. There is no standardized storage for bugs like there is with git, and not really any established data spec, so unless a target site advertises a specific "Launchpad bug import" function, it's going to be a fair bit of work to write a converter.
Launchpad's data sources have an API so exporting the bugs should not be a problem technically, just a lot of python coding. Whatever we would move them to would obviously need an import API (and ideally an export API in case we decide to change providers down the road!) So if we want to keep things together, we would HAVE to have someone own this coding project. (Unless someone knows of an existing converter tool?)
I took a look at it yesterday. For the IPython project a basic python script was created 5 years ago with limited error handling [1]. It exports LP bugs to JSON and then uses Github issues API to import, inbetween there is a step for mapping accounts, bug id:s and what not.
I started exporting Inkscape LP bugs to local JSON file but got stuck at issue #212921 due the bug reporter account is gone, so some fixing is needed on that side (add error handling); others have had the same issue [2]. The last step is to import to Github which can cause some blocking due to some "abuse triggers" from github's servers, but others have already fixed that problem, pull requests are available [3].
If anyone else finds an up to date tool that would be better; if we decide to move bug tracking to github.
[1] https://github.com/termie/lp2gh [2] https://github.com/MetricsGrimoire/Bicho/issues/135#issuecomment-94892370 [3] https://github.com/termie/lp2gh/pulls