wiki stuff, et al
will <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.devel |
|---|---|
| Message-ID | <[email protected]> |
I've been poking around and talking to people about SourceForge and their wiki experiences. The general consensus is that we could install MediaWiki on SourceForge--it's not a trivial thing to do, but it'll probably work--but that it'll be really sluggish. SourceForge has their own wiki system called wikiplaces, but it's kind of slow and not as useful as MediaWiki or MoinMoin would be. The primary use case for the wiki is to make it easier for users to provide and share "recipes" for setting up PyBlosxom in various contexts/servers/configurations... Additionally, we need to straighten out the ecosystem surrounding plugins and flavours that other people build and maintain. I have a server that I lease from ServerBeach. Let's say we were to move the web-site to that server. What do we install to solve our problems? Should we try to do it all in PyBlosxom? Should we install MediaWiki (or some similar system)? Does anyone have experience with other projects that have similar issues and what they did to solve them? /will ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/