Hello, Several people have raised issues regarding the current wiki.netsurf-browser.org which is a fairly locked down instance of nanoki. It's not terribly stable and it's hard to allow people access etc. As such, we need to migrate to a new wiki. There any many options out there but unless someone has a really good reason for discounting the three I will present herein, or a really good alternative option, then we need to choose between these three. Option 1: Trac -------------- Trac is actually a multi-faceted tool which would provide us with viewsvn-like functionality, a simple issue tracker, a wiki, a dev-document manager, and various other bits and bobs. Pros: Written in python, will run on pepperfish[1], provides integrated behaviour for issues, a wiki etc. Cons: Hard to modify for our users' issue-reporting requirements, needs filesystem access to the SVN for the viewsvn-like functionality (could be a mirror, or we could move svn to pepperfish) Option 2: Mediawiki ------------------- Mediawiki is a very popular and well-known wiki engine. Used by Wikipedia and various other sites, it is richly featured but unlike trac, it is just a wiki engine. Pros: Only a wiki engine, so we're free to implement the other features in other ways without confusion. Already has an example instance on the machine which currently runs our SVN. Cons: Only a wiki engine. Written in PHP which means we cannot ever consolidate its functions onto pepperfish (where the rest of the websites are). Is complex and backs onto MySQL which is yet another failure point. Option 3: Moin -------------- Moin is a popular wiki engine written in python. Used by many sites (including in its early days www.ubuntu.com) Moin's syntax is well known and like Mediawiki, moin incorporates plenty of ACL management etc. Pros: Only a wiki engine, easy to set up instances, can run on pepperfish, runs entirely from filesystem and thus can be moved between hosts and can be backed up easily. Cons: Only a wiki engine. Theming can be "interesting" in the chinese proverb sense. Personally I don't care which of the three options we choose, I just want a consensus of opinion. I'm personally against PHP because of what it has done to machines in the past and quite how many security issues tend to arise because of it, but as it isn't hosted on Pepperfish, that's not a concern I need to have. I would raise the following issues as important: 1. Reliability 2. Reachability (people have expressed concern over the reachability of our svn in the past) 3. Backup-ability 4. Relocatability (in case of hosting failure) 5. Maintainability (how many people have access to the underlying instance - i.e. can SSH in and change config etc) Please, start to chime in. D. -- Daniel Silverstone http://www.netsurf-browser.org/ PGP mail accepted and encouraged. Key Id: 2BC8 4016 2068 7895