Nice work.
Why not move lib2geom to github? On 7 Feb 2016 07:13, "Krzysztof Kosiński" <tweenk.pl@...400...> wrote:
2016-02-06 17:54 GMT-08:00 Bryce Harrington <bryce@...961...>:
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.
I converted the Inkscape repository using git-remote-bzr and it was flawless. It's available here, as I mentioned. The branches converted correctly as well, though I had to specify them manually.
https://github.com/tweenk/inkscape
However, the Bazaar history has outdated contributor names and e-mails, which screws up Github graphs, since commits by people not known to Github are not counted and it looks like the project started in 2010. I experimented with git filter-branch and it generally gives good results. I am 80% done with compiling a mapping from old names and e-mails to current ones. (The e-mails are not visible in the web interface, only when you clone the repo, so it's OK to use real ones.)
I went ahead and converted lib2geom to Git on Launchpad, fixing commit authors in the process. (Factoid: there were 24 unique authors.) https://code.launchpad.net/lib2geom
I'm also really skeptical that github/gitlab's bug hosting is going to cut the mustard for our bug folks. And like I said, even if it does, I'm really worried that transferring the bug data promises would be a huge amount of work.
I also have this impression. Here is what I found.
- Cannot attach SVG files to bugs. This would not be a dealbreaker on
its own, since we can just point users to a pastebin or a file host, but...
- No issue template, no voting system / "heat meter" like on
Launchpad, and practically no control over what the new issue page looks like. This is in fact a very common gripe, so much so that over 1500 people have signed an open letter.
https://github.com/dear-github/dear-github
1+2 mean that users can't attach problematic files to bugs, and we cannot point them to an external pastebin-like site. Even if the migration from Launchpad was effortless, Github's bug management is simply worse for a project like Inkscape.
There only two things that Launchpad doesn't have: if a commit message contains something like "Fix #12345", Github will automatically mark the issue as closed, however I don't see a distinction between "Fix Commited" and "Fix Released". Another useful thing is that issue numbers are project-local instead of global, so the numbers are easier to remember. Finally, the styling on Github is nicer, but that's a personal preference.
Best regards, Krzysztof
Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel