Wiki

[Cayle]

Sourceforge sucks $%&?!  What really peeves me is the wiki.  It is timeout heaven and it is so bad that it is hardly editable.  I know that there is an OpenOffice.org plugin for MediaWiki.

@Ray - How hard would it be to set up a MediaWiki for the project?  Then we could edit it offline and publish.

[Ray]

Dave look at this wiki http://docs.wikkawiki.org/WikkaFeatures this can be loaded directly on the site.  See if it does what you want.  Ray

[Cayle]

That wikkawiki looks pretty slick!  I'd want to see it (and particularly its editor) in action before making any great leap forward.  Sourceforge's wiki is feature free, but the biggest problem is performance. 

[Cayle]

Ray, can you check to see what would be required to use that wikawiki with Django, or how we might migrate?  Also, there is a Django code snippet for rendering mediawiki markup as html.  In this guy's blog, he had mediawiki working with Django.

[Cayle]

Ray, have you had a chane to look at the wikis?  Do you have a suggestion between Mediawiki and Wikawiki from an admin perspective?  I'm still attracted to mediawiki from the OpenOffice plugin perspective.  I like being able to edit offline and post.  For a while, I was doing that to my India blog using MS Office, though I lost the habit after actually moving to India.  It is VERY convienient to edit locally and publish remotely, instead of having your session time out, or simply having a slow and unresponsive dog of a website (*cough* sourceforge) throw your work into the bit bucket. 

[Cayle]

It may be good to start looking at how we handle a wiki again.  IIRC, Ray is making slow progress with Django-CRM.  What we need now is a wiki so that we can move from one documentation maintainer (me) who publishes in PDF to one where we can have multiple maintainers and the end users can browse and search.  Mediawiki markup handling would be nice as there are exporters for most popular word processors.  This Django snippet may very well give us the ability to use mediawiki markup: http://www.davidcramer.net/code/54/mediawiki-markup-and-sphinxsearch-for-django.html

I know, I know? there are forty gazillion PhP based ways of doing it, but sine nobody here knows PhP? I know Python.

[Edward]

I like the idea of using MediaWiki or MediaWiki markup, because so many people already know it, and because I'm using it in another project.  I don't have strong feelings about it, though.  My main concern is that we use something that's unlikely to be orphaned, since it probably wouldn't be practical to migrate our content to another markup language down the road.

[Ray]

PHP was way easier for me to figure out then this python/django-cms crap.  There are several php wiki's offered through hostmonster that i can setup now.  If we can decide on one.

[Cayle]

Let me take it for a spin first.  I'm running an svn pull of both Django and Django-CMS.  I'll post later.

[Cayle]

Ray and I are both trapped in exception hell; only in different places.  I'm going to try a trick. 

I'll stop working on debugging entities for a couple of days.  In the meantime, I'll try to get Sphene, some blog app and Django's RSS feeder working on an otherwise vanilla Django.  The templates will be ugly, but can be tweaked later. 

[Cayle]

Sphene community tools works with "minimal" pain.  It only took a few hours to get working, discounting a wild goose chase with postgres (which I eventually ditched for MySQL) and less than forthcoming documentation about dependencies; for which knowing Python was a lifesaver.  It has a minimal forum, blog and wiki.  I'll start messing with the mediawiki markup and see where it goes.  In the meantime, we know this at least works.