Hi Björn, Kay, all,
reading the whole thread I think, the question here is not only about a
single web page, but the general approach using the website and the wiki
as parallel areas to inform our (present and possibly future) users and
contributors.
My personal opinion on this topic is:
Due to the different levels of write access (and licensing - I'm not
sure if you need to sign JCA/SCA [or OCA?] to edit the website) the
website is meant to provide more static content that has been approved
by the relevant part of the community / project, while the wiki is a
collaborative working area (even for website content) for easily
modifiable content, drafts, personal opinions and contributions without
"official" approvement.
I don't think that tagging some wiki pages with labels like "this page
contains official content, you should not modify it" is the right way to
go - I prefer to move this content to the website.
Therefore I'd propose to keep a static landing page at the website that
links to the wiki for modifiable content and to other web pages for
static content.
If a wiki page comes to it's final version, it should be moved
(redirected) to the website until the next overhaul starts.
Of course, this means that we need people updating the website without
too much delay, and quality should not be minor to the wiki - but this
could become easier with a wiki-to-HTML tool.
With regards to the links you mentioned I just add a few lines:
> http://contributing.openoffice.org/programming.html vs.
> http://wiki.services.openoffice.org/wiki/Development
> http://contributing.openoffice.org/qa.html vs.
> http://wiki.services.openoffice.org/wiki/Quality_Assurance
> http://contributing.openoffice.org/marketing.html vs.
> http://wiki.services.openoffice.org/wiki/Marketing
In all cases I'd link directly to the main website pages of the relevant
projects:
http://api.openoffice.org/
http://qa.openoffice.org/
http://marketing.openoffice.org/
The contribution.OOo frontpage could provide a few additional words
inviting people to join the different projects.
But I'd leave the decision to lead their customers to the website or the
wiki to the relevant projects.
So I'd reply to your subject: No, just kill the sub-pages.
Best regards
Bernhard
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
