From: Andy Stone Date: 2005-05-03T23:36:21+09:00 Subject: Re: Bug Tracker Thanks Jason, From an extremely quick review, the main problem with Scarab is that it uses Java. We are a very small IT department for a decent sized company. We have one CTO, one coder (me) and one network admin to handle two completely different (lines of business) web sites not to mention the Intranet,Email server and all the other day-to-day admin stuff. We currently use Java/JSP (etc..) and I'm trying to reduce the amount of code I have to maintain. Also, using Ruby removes the Tomcat layer. Small things, sure..but they add up. There is also the issue of trying to reduce the technologies we have to maintain. I won't go into the list, but right now we use way too many. I guess that was more than expected of a reply :) Thanks for the infor Jason. On 5/3/05, Jason Sweat wrote: > On 5/3/05, Andy Stone wrote: > > Hello all, > > > > We've been looking for an alternative bug tracking system. We were > > using Bugzilla, for a long time, but when we opened it up for client > > entries we found the interface non-geek friendly. So, we went to > > Mantis which is ok, but we had to write some additional modules to get > > our base requirements (i.e. LDAP authentication). We never fell in > > love with the features of Mantis and missed some of the capabilities > > of Bugzilla. So, after looking around for a while the CTO asked if I > > would like to write one using Ruby/Rails. I should also mention that > > this will be open-sourced. Has anyone started such a project that I > > may be able to help with? I will be writing one regardless, just > > thought it would be better to ask the group and combine forces rather > > than to split up the effort. > > > > thanks, > > andy > > Not written in Ruby, but Scarab (http://scarab.tigris.org/) has a > clean interface and a very configurable issue tracking system which > might be at least worth reviewing. > > Regards, > Jason > http://blog.casey-sweat.us/ > >