Hi Rob,
Rob Weir schrieb:
[..]
The problem is that we don't have two wikis today with OOo. We have
one, and it has material that probably should be considered
"official", as well as other material.
[..]
Maybe you can give me some examples of pages that you think are
community-developed, should remain that way, but are not valuable
enough to users that they should be in the official doc set?
I'll add some other kind of pages.
(a) These pages are addressed to users, but are not good enough to be
considered "official":
http://wiki.services.openoffice.org/wiki/Documentation/How_Tos/Using_Data_Ranges,_Data_Sort_and_Data_Filters
http://wiki.services.openoffice.org/wiki/Connecting_to_Microsoft_Access
(b) Pages that gather useful information, but far away from being an
"official" doc, or pages that organize development:
http://wiki.services.openoffice.org/wiki/Calc/Drafts/Treatment_of_new_Excel_2010_functions
http://wiki.services.openoffice.org/wiki/Calc/ODFF_Implementation/Examine_functions
(c) Pages to organize local activities:
http://wiki.services.openoffice.org/wiki/DE/Projektwochenende2007
(d) Pages to gather and consolidate ideas
http://wiki.services.openoffice.org/wiki/User_Experience/Improving_OOo_Default_Settings
http://wiki.services.openoffice.org/wiki/Printerpullpages
So I'm happy to have two wikis, one that is a sandbox for wider
experimentation. And another one where we can migrate stable, mature,
valuable material into a location for an official release.
(Some
material might even originate in the official wiki). But for this to
happen, I think we'd need a few capabilities first:
1) Two wikis under the same platform. Having Confluence for our
developer wiki and MediaWiki for the community wiki won't work. We
need compatibility.
I do not think, that we need two wikis. MediaWiki allows to protect
pages. So it would be possible to protect an "official" doc set. If at
the same time the connected discussion page is unprotected, everyone who
notices an error or wants to make an improvement can write a comment on
the discussion page. The real problem is to react on such comments.
2) Apache 2.0 (or compatible category-A license) for all new content
on the community wiki. This is needed in order to move it eventually
into an official doc set,
Pages, that will eventually become an official doc, can be protected so,
that anonymous edit is not possible. I agree, that for those pages a
suitable license is needed.
I don't like the idea to have developer relevant pages with write access
only for commiters. If the wiki will be organized that way, pages like
(b) or (d) are not possible.
3) A search that spans the two wikis. Maybe Google custom search is
enough. Maybe there is a better way.
Search via Google is OK. A flat hierarchy starting at the main page and
a good structure to access localized content might help in addition.
Kind regards
Regina
