On Fri, Jan 13, 2017 at 09:14:10PM -0500, Martin Owens wrote:
I can only see the Wiki page for website contributions, so it seems you tested the Wiki-to-md conversion tool.
I did test one of the tools, there's a couple of them. As well as a couple of markdown formats, I chose github md. There is one issue, the images in gitlab wiki are uploaded to a separate space and not the wiki repository (which is dumb) but one can commit all images into the repository directly and that will work. I just wish it was all together as it'd make backups easier.
Report back when you have a scheme for doing backups, ideally one we could follow for all inkscape projects.
- 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'm thinking of having it as a separate repository/project on GitLab. Maybe inkscape-web-i18n or something similar. Would you like to create the project? I can help you do the repository translation.
In Launchpad we have multiple projects all linked to a master 'Inkscape Project' record. Is there something analogous that can be done in gitlab?
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...).
I've never really found a use for a sub-module, I mean it is a sub repository in that it belongs inside the inkscape-web. But I don't have a clue really how to set that up or if that means the repository lives in the inkscape-web project or a seperate project on GitLab.
I've used submodules in other VCS's. They add some complexity for what is essentially just convenience. In an open source project where not everyone is familiar with them, I feel the cons outweigh the pros...
Is there anything specific that you'd like help with at the current stage?
I'm working on bugs and milestones, launchpad's API is truely slow, but the code I've got here makes some mistakes which can fix and make it a little faster. But 200 bugs an hour is REALLY SLOW if we ever want to export inkscape's own bug list. (inkscape-web is 617 bug reports)
Other than looking into the i18n repository and sub-module repositories. Those are the most useful items. Thanks Maren!
Best Regards, Martin Owens
Bryce