On Tue, 2017-01-31 at 20:12 +0100, Eduard Braun wrote:
That's unfortunate but absolutely understandable. I guess moving to another server / a virtualized server was not an option?
Are you volunteering? ;-) getting services out of osuosl has been almost impossible. I'd rather be able to show them we can cut back and not have to have replacements.
I think we're talking about different things here: As far as I can see the Wiki currently contains a) documentation on built-in extensions (that was the link), b) documentation on how to write an extension, and c) a list of third-party extensions. While a) is obviously user-facing and therefore would fit on the webpage I don't think it's complete enough yet and needs work. b) is even harder - personally I'd keep it in a Wiki so it can be improved continuously by everyone (as I'd prefer for all developer documentation), bryce would like to put it into the VCS's developer documentation if I understood him correctly and Maren even considered having it on the Website! Extensions themselves obviously do not belong in any Wiki.
a) goes to the inkscape-docs project b) goes to the gitlab wiki c) goes to the inkscape.org website
Links between them are useful. We don't /have/ to keep things in a silo, the extensions on the website can link to creating extensions. The inkscape-docs are built and already shown on the website so continue that.
- If we put a huge sign on top "Warning! Outdated!" nobody will take
that information serious (how could they?). If we don't people might not be aware they're browsing an archived read-only version of the page that in fact *can* be outdated.
People will make mistakes, that is something we'll always have. Having the the button redirect to a page explaining the process would be helpful for anonymous helpers. But most people are going to be bryce ;- ).
scenes like "there's some information on the old Wiki which is mostly up-to-date; unfortunately nobody's able to update the few errors since it's a read-only version; unfortunately we also did not have the time to transfer it to the new Wiki, yet").
If there's not enough time to copy and paste it raw into a gitlab wiki, then it mustn't be a very important change. We're not expecting every page to be a perfect copy, we'll lose things, but then gain the ability to edit them. Nothing is perfect, but it's a chance to make it better.
If I must make a button on every page that say "Move this to GitLab" and "Move this to the website" I'll add those. Not perfect, but maybe helpful.
Best Regards, Martin Owens