Full-on revision control

Since the infrastructure for revision control is in place. Pbwiki ought to eventually offer full-on revision control. This would have to be carefully implemented to avoid confusing users who only need basic versioning of individual files. Maybe this is best implemented as a plug-in rather than a standard feature. An existing revision control system interface could be adapted to avoid reinventing the wheel. Once the full-boat of revision control is available, then pbwiki would be a candidate for comprehensive document management including software revision control - to replace existing web-based solutions. I think you'd find many users adopting wiki first, then deciding the RCS was good enough for software projects. You'd probably have a hard time prying users away from existing revision control systems so an incremental adoption strategy would be the best market to sell. Wiki gives an easy-in to a whole class of web-based collaborative information management solutions. Plug-ins would also allow price-structuring and avoid burdening the basic users with unwanted and confusing features.