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.
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.
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.
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.
On Tue, 2005-05-03 at 22:44 +0900, 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.
If you're using Subversion for source-code repository, I would stronly
recommend using TRAC (http://www.edgewall.com/trac/\) (even if you
don't). The ticket system they have is simple but just works(tm), the
interface is beautiful and the whole thing is written in our
friend-language Python.
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.
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.
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.
I ignore the stage of development of Coterie, but AFAIK it's a TRAC
replacement written in Rails.
--
checking for life_signs in -lKenny... no
Oh my god, make (1) killed Kenny ! You, bastards !
nicholas_wieland-at-yahoo-dot-it
______________________________________________________________________
Yahoo! Mail: 6MB di spazio gratuito, 30MB per i tuoi allegati, l'antivirus, il filtro Anti-spam
I don't think you will use it as it is (it's in PHP, and code is
messy), but you definitely should take a look at it's features list, I
bet you will want to borrow some. It tracks tasks (with dependecies
and gantt charts), bugs, test cases, documents, and work time reports,
and attempts to integrate all that. Haven't seen this combination in
any other open-source project management tool.
···
On 5/3/05, Andy Stone <xsltguru@gmail.com> wrote:
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.
On 5/3/05, Andy Stone <xsltguru@gmail.com> 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
>
>
You could also look at FogBugz. Its pretty affordable, and has
features geared towards customer facing tasks like forums, defect
reporting, etc. It also runs on both Unix and Windows. BugTrack
seems to have drawn some inspiration from it as well IMHO.
-Kris
···
On 5/3/05, Tom Copeland <tom@infoether.com> wrote:
On Tue, 2005-05-03 at 22:44 +0900, 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.
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 <jason.sweat@gmail.com> wrote:
On 5/3/05, Andy Stone <xsltguru@gmail.com> 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.
Trac seems to be popular. I'll have to review it more, but didn't see
where it did LDAP authentication. We are trying to consolidate all
authentication via LDAP. As I mentioned earlier (too many
technologies). We are using subversion, so that is a nice feature.
Another drawback is that it doesn't have PostgreSQL support (yet).
This is another consolidation we are planning.
thanks Dema and Stephan,
andy
···
On 5/3/05, Stephan Kämper <Stephan.Kaemper@schleswig-holstein.de> wrote:
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
In article <1115131538.406428.180220@g14g2000cwa.googlegroups.com>,
If you're using Subversion for source-code repository, I would stronly
recommend using TRAC (http://www.edgewall.com/trac/\) (even if you
don't). The ticket system they have is simple but just works(tm), the
interface is beautiful and the whole thing is written in our
friend-language Python.
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
It's funny how everyone is trying to talk Andy out of this project. If
the CTO wants him to write this thing and even wants him to use
Ruby/Rails and will allow it to be open sourced - well, it sounds like a
great opportunity.
It would be great if we had a 'best-of-breed' bug tracking system that just
happened to be written in Ruby/Rails. It seems like a great combination
and it could only help further the reach of both Ruby and Rails. Yeah
there are a lot of bug tracking systems out there, but there's always
room for improvement.
I would suggest some sort of a pluggable architechture that allows
for easy customization - but you probably already were planning something
like that. Like Rails, it should also be very easy to set up and use
immediately.
Thanks Dmitri. And you're probably right. The more references I get
from you guys about systems you like because of the particular
feature(s) it implements the better. I'm sure there are systems out
there that will have implemented something I haven't thought about
that would be really cool to have.
-andy
···
On 5/5/05, Dmitri Borodaenko <angdraug@gmail.com> wrote:
On 5/3/05, Andy Stone <xsltguru@gmail.com> wrote:
> 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.
If you know Mantis, you definitely should take a look at ProjectView:
I don't think you will use it as it is (it's in PHP, and code is
messy), but you definitely should take a look at it's features list, I
bet you will want to borrow some. It tracks tasks (with dependecies
and gantt charts), bugs, test cases, documents, and work time reports,
and attempts to integrate all that. Haven't seen this combination in
any other open-source project management tool.
Thanks for the info. I will definitely look into this project.
-andy
···
On 5/5/05, Nicholas Wieland <nicholas_wieland@yahoo.it> wrote:
- Andy Stone :
> 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.
I ignore the stage of development of Coterie, but AFAIK it's a TRAC
replacement written in Rails.
HTH,
ngw
--
checking for life_signs in -lKenny... no
Oh my god, make (1) killed Kenny ! You, bastards !
nicholas_wieland-at-yahoo-dot-it
______________________________________________________________________
Yahoo! Mail: 6MB di spazio gratuito, 30MB per i tuoi allegati, l'antivirus, il filtro Anti-spam Yahoo fa parte della famiglia di brand Yahoo.
<Location "/cgi-bin/trac.cgi/login">
AuthLDAPEnabled on
AuthLDAPAuthoritative on
AuthType Basic
AuthName "trac"
AuthLDAPURL ldap://url/ou=Accounts,dc=aei-tech,dc=com?uid?sub?
Require valid-user
</Location>
And it uses ldap for logins quite beautifully.
···
On Tuesday 03 May 2005 10:02 am, Andy Stone wrote:
Trac seems to be popular. I'll have to review it more, but didn't see
where it did LDAP authentication. We are trying to consolidate all
authentication via LDAP. As I mentioned earlier (too many
technologies). We are using subversion, so that is a nice feature.
Another drawback is that it doesn't have PostgreSQL support (yet).
This is another consolidation we are planning.
FogBugz has the same technical drawbacks (in our view) as Trac. And
unless it does everything we would like out of the box, we wouldn't
pay for the product.
I guess it seems I'm being strict and close minded about these issues,
but really I'm not. I promise We have spent considerable time
reviewing the technologies that have been implemented over the course
of mergers and acquisitions and have a developed a restructuring plan
that will make our lives easier and possibly free up a weekend here or
there
···
On 5/3/05, Kristofer Goss <krsgoss@gmail.com> wrote:
You could also look at FogBugz. Its pretty affordable, and has
features geared towards customer facing tasks like forums, defect
reporting, etc. It also runs on both Unix and Windows. BugTrack
seems to have drawn some inspiration from it as well IMHO.
-Kris
On 5/3/05, Tom Copeland <tom@infoether.com> wrote:
> On Tue, 2005-05-03 at 22:44 +0900, 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.
>
> There's BugTrack:
>
> http://rubyforge.org/projects/bugtrack/
>
> Yours,
>
> Tom
>
>
Trac seems to be popular. I'll have to review it more, but didn't see
where it did LDAP authentication. We are trying to consolidate all
authentication via LDAP.
Trac doesn't do any authentication, it relies on the webserver for that. So if your webserver has LDAP auth support there won't be any problems.