Re: The backbone that sucks least?
Do they manage tickets with Keystone? I've heard you mention that as a decent trouble ticket system in the past.
UUNET has some kind of localized commercial hybrid tracking system, it doesn't look like Keystone from my outsider (former customer) perspective. I really liked Keystone while it was growing.
Keystone is, unfortunatly, indisputably dead at the moment. White Pajama Software bought it from Stonekeep, and promptedly turfed it in favor of their homegrown software. The source is "available", but it was never released under any kind of OSS license, so you're stuck with the last "official" release (which, while usable, still had tons of bugs and usability issues), and there's no active development going on right now.
I've seen nothing I like better, warts and all. I guess if there were a standard database schema and interchange format for trouble tickets, so that folks could choose their front end and back end systems from different sources (and maybe for different strengths), a lot of duplicate effort could still be avoided.(*) (*) I only said that to make Jerry and DRC <winge>. IRTS 'til it hurts, man.
Keystone is, unfortunatly, indisputably dead at the moment. White Pajama Software bought it from Stonekeep, and promptedly turfed it in favor of their homegrown software. The source is "available", but it was never released under any kind of OSS license, so you're stuck with the last "official" release (which, while usable, still had tons of bugs and usability issues), and there's no active development going on right now.
For a while I tried WP's system. It was nice but buggy as all heck. And slow too. They supposedly would only support T1s - any problem I had was attributed to either my dialup or my cable modem. And when I requested SSL, performance went straight down.
I've seen nothing I like better, warts and all.
I switched to using RT - www.fsck.com - which is actually an extremely good system. - mz
participants (2)
-
matthew zeier
-
Paul Vixie