I do agree that a wiki is nice in principle, but unfortunatly it doesn't tend to stay up to date with any changes in PolyVox. These changes do still happen quite a lot even at a low level, and it causes frustration for new users when code on the Wiki does not compile. I can't really blame the contributors as the code compiled when they wrote it (so it's me that broke it!) but I also can't take responsibility for maintaining other people's code.
But maybe removing the Wiki is indeed too much... I'm not really sure. At any rate I'd like to make it clear that it is unofficial documentation, and perhaps it could be useful to have a 'last tested version' on each page (we couldn't do this previsouly because we didn't have numbered releases).
holocronweaver wrote:
What spam prevention measures are in place on your wiki? I personally have never had trouble with spam on my personal MediaWiki because I require that all user accounts be reviewed by me before being enabled. I am not sure if this is doable with Dokuwiki, but it is an idea.
Actually there aren't any spam prevention measures in place. I have to say I'm not a bit fan of DokuWiki so far (mostly I don't find it attractive though you can probably add themes). If we do want to keep the Wiki then I'd probably be keen to look at a hosted solution, and at least check out the Wiki which is built into BitBucket.
holocronweaver wrote:
As for consolidating the TODO list, I see that as a separate matter from continuing the wiki.
Indeed, we have the BitBucket issue tracker now.