Requirements for a wiki
A wiki is for collaborative work and concerns- developers (policies...), qa team/triage
- release managers (tour, notes, errata, development: roadmap, alpha/beta, specs...)
- users (doc, how to, specific projects, collaborative work between communities)
- contributers and organization (what we do, what to do, how to do it)
- marketing (who we are, how to get involved, ...)
- others (events, initiatives, emerging projects, faq, explanations...)
Can be used:
- internationally and locally, to provide visibility for events for example
- as a support for recurring questions in forum
- as support of publication of processes (get people involved)
- as a link between developers and users
- when collaborative work with no specific resource is needed (no real web site, coordination local or global, international magazine...)
- (other works, to be defined, like personal page/blog for users...)
New international instances could be created when an activity is identified with a dedicated international community contributing (weekly newsletter, projects like providing games experience or other desktop like xfce, magazine...)
Existing documentations or implementations
http://mageia.org/wiki/doku.php?id=wiki_requirementssee ยง2 of PDF document on wiki organization to see how wiki / forum / blog / ML relate with each other
http://mageia.org/wiki/doku.php?id=web:wiki for tracking down project issues to be addressed and organization
For more:
- see http://wiki.mandriva.com (categories, languages, modules, implementation, pages, flat presentation for most of the content relying on categories to hierarchize)
- flat organization and language-transversal pages available (be it for release or developers)
- some local initiatives, some local modules (?)
Implementation of a wiki from user point of view to infrastructure and communities (delegation)
The architecture should be- scalable / dispatched
- delegated when needed (when needed)
- industrialized
- dev.wiki.mageia.org available in advance to test ?
- deployment for specific wiki (user testing)
- rule of thumb: any module available / validated is then available for all wiki (mutualization needed though, for example agenda could be concentrated or instantiated via other tools, see calendar for example)
Access
| http://en.wiki.mageia.org | http://fr.wiki.mageia.org | http://es.wiki.mageia.org | http://de.wiki.mageia.org | ... |
Directories
| http://wiki.mageia.org/en/ | http://wiki.mageia.org/fr/ | http://wiki.mageia.org/es/ | http://wiki.mageia.org/de/ | ... |
Servers
| wiki+db(en) | wiki+db(fr) / wiki+db(es) | wiki+db(de) |
for example, de.wiki.m.o may only be a redirection (or mod_rewrite if needed)
Hardware / admin
| server en | server fr + es | server de outside of mageia infrastructure (example), either with ldap authent or not |
