I'm working on a Django-based web app in which the community fuels the content on the site, much like a wiki. Content is in the form of HTML, and users have total freedom to fork articles/chapters or make their own modifications to existing ones and add them to the current 'working version'. The maintainer of each article/chapter (the original authors[s]), will have the option of accepting these changes.
We're also planning on maintaining two versions - or at least views - of any given article: the author-approved edits version and the free-for-all community based edits version.
The revision system that would manage all this forking, merging and branching on top of detailed histories is starting to sound a lot like what a source revision system does. So I'm considering using Git to manage these revisions.
My question to those more experienced in this type of thing than I:
Is it worth the effort and after that, will it be better than rolling something out in a RDBMS?
And if so, roughly, how should I go about implementing this with Django/Python?
asked again in hopes of catching more replies, this is very important to me