As long as I have time, I can make up very basic page with sections like that. And then other people can tweak in the details which I either get wrong or leave out.
All best, brynn
-----Original Message----- From: Bryce Harrington Sent: Tuesday, January 31, 2017 7:37 PM To: brynn Cc: Martin Owens ; C R ; inkscape-devel Subject: Re: [Inkscape-devel] Website Development Was: User Involvement
On Tue, Jan 31, 2017 at 03:56:04AM -0700, brynn wrote:
Hi Martin, Yes, I understand that. I just wasn't sure the things we're dicussing here need to be documented. If they need to be documented, I would probably just make a link to the list archive for this thread. I mean, based on past experience, we could even be discussing this off list. So you aren't suggesting a change such that we document this kind of discussion, right?
Since it was one of my suggestions that spawned this thread, I should clarify better at what I was intending. What I had in mind is a landing page that explains the absolute basics:
1. Where do I find the inkscape_web source code? How do I check it out? (i.e. a pointer to the gitlab project + some basic setup hints)
2. Where do I find directions for setting up an inkscape_web instance on my local system? (i.e. a pointer to the docs in the source tree)
3. What help is needed? (i.e. pointer to a todo list)
4. Who can I talk to for proposing ideas, or getting help with problems? (i.e. a mailing list, IRC, etc.)
5. What is the process for getting changes accepted and landed?
6. When does the live website get updated? Is there a regular schedule?
Presumably this landing page would be in the inkscape_web wiki, but it could be whereever the inkscape_web team finds most convenient. Then, on the inkscape web proper we would include a link to that page on our Contribute page.
Hope that clears up what I had in mind here... And again, just a suggestion; if the inkscape_web team has ideas on how they want to handle new contributors, those would take priority.
Bryce
But I am curious about no part of it remaining on Launchpad.You mean except for bug reports, right? Or will the inkscape-web bugs be moved over there too?
Thanks, brynn
-----Original Message----- From: Martin Owens Sent: Sunday, January 29, 2017 10:51 PM To: brynn ; Bryce Harrington Cc: C R ; inkscape-devel Subject: Re: [Inkscape-devel] Website Development Was: User Involvement
Sorry Brynn,
I mean to say: If you consider the inkscape-web project as it's own thing, then I want all documentation, all blueprints, all non-bug related notes to be in the gitlab wiki here:
https://gitlab.com/inkscape/inkscape-web/wikis/home
So the inkscape-web project will end up in two places. Deployed live on the web server and on GitLab. The plan is that no part of it will remain on Launchpad, no part of it will be on a media wiki and very little documentation will be committed to the repository itself (unlike inkscape itself in Bryce's plan)
Does this make better sense?
Best Regards, Martin Owens
On Sun, 2017-01-29 at 22:32 -0700, brynn wrote:
Hhmmm, I don't quite understand what you mean, Martin. Sometimes you skip a step in your comments or logic that I can't infer. I actually didn't understand what Bryce meant about closing the current wiki in favor of something else....if that's where your comments come from.
Or do you mean you want the current wiki page (http://wiki.inkscape.org/wiki/index.php/WebSite#Website_Development) moved over to the gitlab wiki?
Or do you mean to make notes in the gitlab wiki about these proposed changes (on Contribute and Promote pages)?
After 5 readings, I think you mean a little bit each of the last 2 guesses. But just for the record, can you clarify?