Hi all, (including Jonas Smedeguard in Cc:)
in the discussion around X2go bug tracking I would like to make people
aware of this overview of offline bug trackers:
http://heapkeeper-heap.github.com/hh/thread_298.html
My favorite in the list of offline trackers currently is ,,ditz''.
Maybe we should start thinking about offline bugtracking as an option
for X2go. The great disadvantage is that people cannot not send
e-Mails to the tracker. The advantage is the easy-to-handle command
line interface for filing/editing bugs plus a complete VCS/Git
integration.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On 11-05-17 at 08:49am, Mike Gabriel wrote:
My favorite in the list of offline trackers currently is ,,ditz''.
My favorite - evolved since our last discussion - is to use [RT]. Because it is very mature, and because it provides very sensible interfaces (including both email and REST). RT is written in Perl, for those who care.
Then for offline needs to use [SD]. Because no distributed issue tracker seems mature enough to me so syncing with other systems becomes high priority, and SD does that as central design principle - with a few working now including RT, and Debbugs (Debian BTS) in progress. SD is written in Perl, for those who care.
Then even if SD turns out to be bad, accumulated knowledge is not lost.
If no other tool emerges doing both offline-mode and sync-with-others, then I would prefer accumulated knowledge in a more widely used format than in some great-for-laptop-use but otherwise less popular one.
Maybe we should start thinking about offline bugtracking as an option for X2go. The great disadvantage is that people cannot not send e-Mails to the tracker. The advantage is the easy-to-handle command line interface for filing/editing bugs plus a complete VCS/Git integration.
- CLI helps hardcore hackers.
- GUI/web-UI helps occational code contributors
- REST/SOAP/... APIs help syndication e.g. towards distros
- MTA encourage input from users (including distros).
So you will treat users as second class users of the issue tracker?
Not necessarily a bad thing to do, just beware of it!
Kind regards,
- Jonas
[RT] Request Tracker - http://bestpractical.com/rt/
[SD] Simple Defects - http://syncwith.us/sd/
--
- Jonas Smedegaard - idealist & Internet-arkitekt
- Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
Hello Jonas,
Am 17.05.2011 09:51, schrieb Jonas Smedegaard:
On 11-05-17 at 08:49am, Mike Gabriel wrote: My favorite - evolved since our last discussion - is to use [RT]. Because it is very mature, and because it provides very sensible interfaces (including both email and REST). RT is written in Perl, for those who care.
I've received a number of mails describing concerns and problems with the initially suggested horde tracker. So I really welcome the discussion about the bug tracker. I will have a look at RT and SD. Thank you very much for your recommendations!
- GUI/web-UI helps occational code contributors
This still is a very good point... (we should care about - if we can)
So you will treat users as second class users of the issue tracker?
Not necessarily a bad thing to do, just beware of it!
Maybe there is a way to connect them back to us in the future - but again: thank you to keep us aware of it!
Regards,
Heinz
-
Heinz-M. Graesing -
Jonas Smedegaard -
Mike Gabriel