migrating wiki.koffice.org

[Jaroslaw Staniek]

(sorry I wasn't subscribed, so probably starting new thread)

The question was:
> community.kde.org/calligra/applicationname or as
> community.kde.org/applicationname (Krita is already on the wiki as
> community.kde.org/Krita) ?

It is possible to have all the above. Mediawiki hierarchy has
redirects, so we have graphs structure.
The concern about missing features is still valid. Among the isses is:
- a lot of garbage will appear in search result, unless we use
mediawiki namespaces
- I believe some random people would add translation for some of our
technical pages, what's not quite reasonable (outdated translation is
worse than no translation); there's also problem of accuracy
- it's not easy to ask for installing plugins, on our installation it
would be nobrainer
- I consider wikis are important part of our web page and message to
the outside world

As a plus for the community base wiki, we do not have to do administration.
Another plus is the common kde sign in.
Anyway I volunteer for the administration task if we decide to have
our installation.

Also, I do not propose to have documentation for applications on our
wiki, communitybase is a good place for this type of content.

-- 
regards / pozdrawiam, Jaroslaw Staniek
 http://www.linkedin.com/in/jstaniek
 Kexi & KOffice (http://kexi-project.org, http://identi.ca/kexi,
http://koffice.org)
 KDE Software Development Platform on MS Windows (http://windows.kde.org)