Roundup Tracker - Issues

Issue 2550637

classification
Title: filesystem/VCS backend
Type: rfe Severity: normal
Components: Database Versions:
process
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: Nosy List: kowey, rouilj
Priority: Keywords:

Created on 2010-02-08 00:42 by kowey, last changed 2016-07-10 23:08 by rouilj.

Messages
msg4022 Author: [hidden] (kowey) Date: 2010-02-08 00:42
Roundup is supremely flexible.  

What would make it even more so is if we could store our issues (and
everything else) as files and directories which could then be version
controlled. To support distributed version control, it would help if
roundup objects could have non-sequential names, ie. derived from some
sort of hash.  A good example of this in action is the bugs-everywhere
tracker:
 - http://bugseverywhere.org/be/show/HomePage

What would be awesome if there could be something with the generality of
roundup but the DVCS-friendliness of bugs-everywhere, because it is
extremely reassuring to be able to consult and update one's bug tracker
offline.

At first, in msg3930 I thought this was what issue2550547 was all about,
but after reading
http://www.scribd.com/doc/16508428/Google-Summer-of-Code-2009-Roundup-Improvements
I see that this was solving a slightly different problem (making roundup
notice changes reported via VCS).
msg5822 Author: [hidden] (rouilj) Date: 2016-07-10 23:08
This would require a major rewrite of roundup. Unless you want to
undertake that, I don't see any chance of it occurring.

So I am going to close this as rejected.

You may be interested in http://fossil-scm.org/ which is a DVCS, simple
distributed bug tracker and distributed wiki all rolled into one.
History
Date User Action Args
2016-07-10 23:08:08rouiljsetstatus: new -> closed
resolution: rejected
messages: + msg5822
nosy: + rouilj
2010-02-08 00:42:45koweycreate