To gauge the interest in changing the wiki software we currently use I'd appreciate if you participate in the followin survey. Please feel free to add or edit our options. Also, I'd like to compile a list of advantages and drawbacks for each option, so feel free to add that to, just keep each point short enough for the whole thing to stay readable. Discussion should be held on the mailinglist, the discussion page for this article or on the next Jour Fixe.
- * I don't need any additional features: |
- + Open source, can be modified with ease (and was already modified for vimeo support fE)
- + lots of (ugly) plugins
- - nobody takes care of updates
- - baaaaaad PHP :(
- - wiki syntax sucks
- - major updates neccessary.
- + very easy upgrade management (base software and plugins)
- + built-in calendar system that could probably replace our self-written one
- + many nice features come out of the box like auto-saving of drafts, a wysiwyg editor, easy tags, user configurable rss feeds, source highlighting
- - not Free software
- - migration might lose some structure or formatting of old content
Write our own Wiki software: TomK32, ...
- + Even more control about features and workflows
- + "Lessons learned" from existing software, "time to do it right"
- + Maybe yet another opportunity for a metalab startup
- + ...
- - huge amount of work
- - haters will hate it
- - updates and changes to the codebase are in the hands of few willing to spend time, just like the MOS. future development might become a pain in the arse