Am 11.01.2017 um 17:50 schrieb Martin Owens:
I've set the wheels in motion to move inkscape-web to GitLab here:
https://gitlab.com/inkscape/inkscape-web
No new commits to the bzr branch will be accepted, and we'll tidy up the launchpad project as we go. Upgrade should be possible by moving your existing checkout aside and doing a fresh git checkout, move any data and pythonenv directories you have back into the new git repository.
- Is the code on gitlab yet? I can't find it, but the original on lp is indeed closed.
I can only see the Wiki page for website contributions, so it seems you tested the Wiki-to-md conversion tool.
The next items are for the bugs, milestones and other bits of data I have that need to be put away in the new GitLab project page. I'll post any scripts or other bits of code that make that process possible.
A good example of some hanging threads are any remaining changes to the projects branch you have open bryce, and the separate translations repository.
- Moving the translation repo will require code changes in the main inkscape-web repo (just as moving the main repo will, for the contributors page, which parses the commits).
I assume it will live in parallel to inkscape-web in the inkscape group's realm?
Will it be integrated into the inkscape-web repo directly? I've never really used it, but I know that in git, you can have nested repos (aka submodules)... (my git repo always told me something was 'dirty' until I found a way to silence it...).
Is there anything specific that you'd like help with at the current stage?
Regards, Maren