Trac could use a distributed VCS storage
|Reported by:||Owned by:|
|Cc:||davidf@…, leho@…, itamarost@…||Branch:|
a friend and i are running a small publishing house, and are collaborating with trac and instant messaging - kudos to you, because it does just about all we need!
here's what trac doesn't do very well: we both use laptop computers, and are travelling quite often. in order to work on shared documents, we need to be online constantly, as conventiently most of our shared documents are in wiki format by now. it's not always possible to guarantee internet connetcivity, though…
i realise that subversion is not the ideal repository format for our needs, we really need something like monotone that works well with local repositories that can be merged with a central repository or updated from there. still, writing a whole set of tools such as trac offers on top of monotone would be quite tedious.
so, in a roundabout way what i'm asking is whether it would be possible to run trac in a 'local' mode where it reads the subversion repository information from a local copy _only_ (with limited history/changeset functionality, of course). in addition, trac should store all wiki, ticket and other data in a filesystem structure instead of a db that can also be manages via a seperate or the same subversion repository.
a "commit now" or "i'm online, try to merge with the central repository" button or something similar might be all that's left to make trac the ultimate in collaboration tools.
now being a developer myself in my day job, i realize that this could be a HUGE feature. depends on your architecture, and even if it lends itself to implement something like that, HUGE just reduces to LARGE.
still, i'd like to see it :)
Change History (17)
comment:7 by , 16 years ago
|Summary:||have trac store wiki pages in a filesystem → Trac could use a distributed VCS storage|
comment:12 by , 13 years ago
|Milestone:||triaging → next-major-0.1X|
|Priority:||normal → lowest|
|Severity:||normal → critical|