Me too!
How will we proceed from now on? Will we be developing bugfixes and new features in feature-branches on our own personal git repos (forks) and then requesting them to be merged into this upstream repo?
It would be good to have some guidelines on how we'll coordinate development from now on.
cheers, Felipe Sanches
2017-06-09 14:12 GMT-03:00 Bryce Harrington <bryce@...961...>:
On Fri, Jun 09, 2017 at 11:29:12AM -0500, Ted Gould via Inkscape-devel wrote:
Hello all,
There seems to be a good Git repository on Gitlab now:
https://gitlab.com/inkscape/inkscape
I think there's still work to do in making the branch names, for releases especially, consistent. And there are probably many that can be deleted. But folks should be able to get back to work using that Git repository.
A reminder to folk that we have a guide in the Wiki, and I found a Gitlab cheat sheet on Git as well. Please ask on the mailing list or in #inkscape-devel if you have issues.
http://wiki.inkscape.org/wiki/index.php/Working_with_Git https://about.gitlab.com/images/press/git-cheat-sheet.pdf
Thanks everyone, Ted
Thanks Ted, just checked out the repo and it came through without a hitch.
Bryce
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel