On Tue, Jul 22, 2014 at 05:43:54PM -0400, Martin Owens wrote:
On Tue, 2014-07-22 at 13:46 -0700, Bryce Harrington wrote:
Many of the 'About' pages really should be on the main website anyway. I figure we can post board documents here for now.
I see:
Publicity: Website User Documentation: Website User Community: Website / #inkscape / sf-mailing list Administration: Website / wiki / sf-mailing list Development: Wiki / launchpad / sourceforge / #inkscape-devel / sf-mailing list
Some of the pages in particular in wiki I'd like to see moved include "About Inkscape", "Features", "Supported Operating Systems", "Coverage" (aka Publicity), and maybe "Branding". These all seem like stuff that should go "on the box" so to speak. "FAQ" IIRC originally was part of the website proper, but was moved to wiki just to make it easier to edit; perhaps it (or some subset or rewrite of it) should move back.
There's a dozen pages in the wiki listed under User Documentation. I haven't reviewed any of these pages so have no opinion on whether they should be on wiki or the main website, or even if they're still relevant. But it likely to be to users' benefit if someone could take a look through them and make those decisions.
There's also a fair number of abandoned stubs. We could probably be more aggressive at pruning these, to give more room for newer topics.
We've got a lot of both duplication and disjointed parts. I'm hoping we can remove the need for sourceforge for example. Moving downloads and mailing lists to the website server (if we can get the right tech in place) but as for the wiki / website split for administration, I'm not sure.
Downloads ought to be pretty straightforward since it'd just be a directory of (signed?) files. Mirroring is probably the main thing to worry about. Have you given thought to how we'd go about setting this up? Perhaps we could go ahead and prototype something.
As to the mailing lists, I had brought up moving the board list to launchpad but we didn't have full consensus on that. Perhaps self-hosting the list would be more acceptable, but I'm a bit leery about the list administration workload that'd be incurred and if we could handle it. Anyone else have thoughts on this?
In general, I do favor having more of our services on a unified host that is regularly backed up and easily replicated with a new provider in case of disaster.
Bryce
P.S. Please feel free to reply on inkscape-devel@ if you want to open up more discussion on any of the above.