Jonathan,
jonathon wrote:
Kay Ramme - Sun Germany - Hamburg wrote:
What you may mean and what we could (and should) have is a (common)
vision where we are heading.
There are four or five pages on the existing OOo website
that state what the current common vision is. Of course the
only one that happens to be semi-meaningful is not on the
OOo website.
please provide the links of the pages you are referring to ...
- There is a marketplace where open source developers as well as commercial
entities can offer their services.
A how to for that would be useful.
Sure
sure that, if you ask, most people can give you a list of what's coming
and what they are thinking about.
I am referring to pages that are labelled as "Roadmap for
OOo V x.x. Pages that purport to be official
representations of where the project is going.
Do you mean the project as a whole or the project as Writer or Uno?
Note, precise roadmaps for some / several future versions can only be
given in a cathedral style project.
http://wiki.services.openoffice.org/wiki/Uno/Meta/Organization
Stuff like that is going to be worse than the current situation.
Could you give more details ?
My suggestion is along the lines of
http://en.openoffice.org/wiki/Organization as a
disambiguation page for
http://en.openoffice.org/wiki/Organization_Uno
http://en.openoffice.org/wiki/Organization_Marketing
etc.
So you basically just want to prefix organizational pages with
"Organization" ? What is the advantage compared to subpages?
Everything related to the UNO project gets labelled as
{{Category:UNO Project]] Everything related to the art
project is labelled {{Category:ART Project}}
A page can belong to two or more categories.
Every Uno page is already labeled accordingly and is physically located
under wiki/Uno, pages related to but not belonging to Uno are located
elsewhere, categories are tried to be used in an orthogonal fashion,
e.g. "tutorial" for tutorials, "Spec" for specifications etc. Overview
pages are created with the help of DPL2 (Dynamic Page List), querying
for pages belonging to the overview.
The idea here is that all that one has to do to find
information is write
http:://en.openoffice.org/wiki/whatever-the-person-is-looking-for.
If that page doesn't exist, then they go to search.
That is what I tried to achieve, that you actually can guess the URL.
By having stuff like
http://wiki.services.openoffice.org/wiki/Uno/Meta/Organization
you ensure that nobody except members of the project will be
able to find data. And that defeats the entire point of
using a wiki. You might as well go back to using subversion
and having to check data out using SVN.
??? It may be that the page is not perfect and that an image would be
better, but it does not hinder anybody to search, and I think it at
least gives the chance that somebody may understand the structure (Uno
is AFAIK one of the few projects that actually has a structure). Your
criticism is too general, please bee more precise otherwise I can not
improve ...
xan
jonathon
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
