Doug Ransom's wish list
Installation Documentation
- I found the documentation for apache and windows incorrect (didn't work without checking the errata) and with IIS on Win XP Pro (best avoided anyway) insufficient (could only provide a read-only wiki). Its easy to make a mistake, and if you do, its really hard to figure out what you did. In addition, the existance of unused CGI files in the htdocs area really makes things confusing for debugging.
I suggest taking a pass at making the install instructions clearer and correct especially for windows. Describe what each step does, and maybe some debugging tips. I can help out with this, or maybe with testing an install procedure written by someone else. Contact me if interested.
Install Procedure
I really think its weird I have to edit python code to get the wiki to work (using apache and windows). Editing an XML file seems a reasonable configuration step, but source code just feels weird.
I suggest having a zero-source-code-touch installation or providing a tool to make code modifications.
I also think it would be cool to have a wizard which configures apache or IIS.
Wikis at the root of a virtual server
It would be nice to have a wiki at the root of a virtual server. I was advised not to do this on the email list, advice I am willing to heed for now.
RDF Metadata
It would be cool if there were a way to create metadata for a page or changes thereof and put this in the RSS feed as well. An RDF/RSS index to the whole site could be useful by search engines, rdf tools, etc.
Maybe some wiki syntax or metadata (similar to the comments area) for a post could contain the applicable metadata, perhaps a dmoz category or something.
Easy way to look at old versions
It would be nice to see by the edit-this-page button a review-history button, and a way to see a list of deleted pages and their history too. I am guessing this is not an original request.
- Click on the info icon
Login Authentication
It would be very useful in an intranet environment to identify the person making changes, so if you have a rogue employee antagonizing the wiki they can be identified. Windows authentication would be the most useful, since in most corporate environments, MoinMoin will be deployed on windows.
Someone suggested:
- if you can't identify by ip address, then fire your network admin
LOL. The problem is the network admins control the rules. I think they are uncomfortable identifying by ip address (which really just identifies host anyway), and they don't work for me so there is not much I can do.