On Fri, 2016-02-05 at 08:00 -0500, Martin Owens wrote:
A lot of projects use Git. I've already done an experimental conversion of inkscape-web to git (it had a few issues that had to be fixed manually, see but not a lot)
The SVG WG has moved its specification repository to GitHub (as has most W3C working groups) and it has increased participation from people not in the working group. The shift from Mercurial to Git wasn't too bad. Switching from Bazaar also shouldn't be that bad.
We have just started to use the issue tracker in GitHub and initial impressions are good. Have a look at:
https://github.com/w3c/svgwg/issues
Other W3C groups already do all their issue tracking on GitHub.
There's a lot of support for Git, but I do have reservations about Github. It's a lot more like a cult than a platform and it's very much a monopoly at this point and I remember Bitkeeper. At least the repository is movable and they have an api for exporting issues and a wiki.
I don't know about exporting; we should check. I asked about the SVG WG reliance on GitHub (mentioning our experience with SourceForge) and the response was that it wouldn't be hard for the W3C to switch to its own servers if necessary or find an alternative host.
It's would enforce using a more code-review style model, no matter how many people we make a part of an Inkscape organisation.
Although on the positive side, it'll probably increase participation. Something the project could do with having. We're currently experiencing 40TB of downloads a month and our software is used by millions of people, but translating that into developers is meeting more resistance.
Best Regards, Martin Owens
On Thu, 2016-02-04 at 22:16 -0800, Krzysztof Kosiński wrote:
Eventually we probably need to move to Git. The user interface is completely atrocious, but the fact it works from a single directory by default is very convenient when using Eclipse, and Eclipse is an elephantine monstrosity but has good code navigation. This could also encourage more people to contribute, since almost all OSS developers know Git, while a very limited number know Bazaar at this point.
The bug tracker and answer tracker should definitely stay on Launchpad, but what about the code? Should we use Launchpad's nascent Git support, or some other site like Github? What people think?
We can convert lib2geom first and apply the lessons learned to Inkscape.
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
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