As I build out the tools for space builders I run across interesting ideas which mostly consist of applying various web patterns to 3spaces. Lately people have been chatting about wikitecture, which I have summarized with this outline:
Versioning
- history
- revert
- offline backups
- shards
Sharing
- default to open, but lock when hot
- vandalism isn't fatal
- snippet libraries
Communicaton
- proposals, vetting
- ref. patch submission to code repo
- talk pages
- feedback: traffic, thumbs up/down, comments (by object, by view)
- leadership: de facto or de jure
I'm intrigued by the idea of tightly versioned spaces, though it's tough to justify the complexity on the server side for more than regular backups and a broad restore capability. We're already seeing the libsl folks making noises about backups and versioning and perhaps answer is to place the versioning burden on the creator side in the form of IDEs working against code repositories and pushing periodic updates into spaces. But that's not very wiki-wiki, is it?