Discuss wiki implementations, technology, specific tools & techniques. Note: there's a "wikis" group, which seems more about the social aspect (adoption & such)
1 - Seek patronage at the highest possible level. That is, find a person with as much power within the enterprise as possible who will sponsor the project. The sponsor may do no more than ‘give the nod’ to your work, but that invests you with the authority to draw on other people’s time. In CorVu’s case, the CEO himself was a key supporter.
- lelapin
2 - Enthuse a champion. This needs to be a person who is well respected, who will lead by example, and in doing so enthuse others. The champion will need to be able to put a lot of time into the project and will often be the primary contributor to the Wiki, especially at the beginning. In our case, that turned out to be myself.
- lelapin
3 - Identify the group of people who can be expected to generate the majority of the Wiki content. These are typically subject matter experts. Discuss with them the value of writing down what they know or Wiki-izing what they have already written.
- lelapin
4 - Identify anyone whose participation is mandatory. Is there a key political player or subject matter expert who absence from the project will cause others to think, “Well, if she’s not involved, I’m certainly not going to waste my time?”
- lelapin
@DeWitt Clinton: Surprised that, given the ascendancy of python (and app engine), we haven't seen major apps like MediaWiki and WordPress ported over yet. (via http://friendfeed.com/dewitt...)
Announcing a group for discussion of wiki implementations--technology, specific tools & techniques. Note: there's a "wikis" group, which seems more about the social aspect (adoption & such). This one has a much more technical bent. http://friendfeed.com/wiki-te...
If you're involved with wiki tech, you should be aware of Creole, an attempt to create a standard language across wikis. Like all compromises, it's far from perfect. http://en.wikipedia.org/wiki...
I like creole for writing small posts or notes, but very often I miss the extensibility restructured text.
- Peter Hoffmann
Peter, no doubt about it, ReST is the king of all wiki text formats (if a bit overwhelming at times). I even prefer Markdown to Creole, really. The attraction of Creole is not that it's a great language in itself, but that it's one where there's a chance of agreement across implementations.
- Uche Ogbuji
Learned that for overwriting attachments in MoinMoin, you need to have "delete" as well as "write" and rights on the respective wiki page. Makes sense, but threw me at first.