Thanks Phil,
As I said with the initial post, I was writing this regardless, but
just wanted to see what had been done with Ruby/Rails that I could
possibly extend. Our feature request is very specific and it's nice
to see the alternatives the other people have mentioned. (Especially
like the subversion interface)
It will definitely have a pluggable architecture as we would like to
include portions of this system into our intranet. We are also
planning on writing an inventory system with ruby/rails that will
integrate with the bug tracker. So, for instance, "john" reports a
bug with some application he has installed. We want the ability to
link (plug into) to the inventory system to see what type of computer
he has, the applications he has installed, etc... This is a very
specific, but beneficial feature that we want and knowing that's not
the norm, we decided to write such a beast. There are a host of other
features that we need and will include.
My plans for setting this up would be to use gems so it would be as
simple as rails.
I'm a big fan of Ruby and would like to see it rule the world.
thanks,
andy
···
On 5/3/05, Phil Tomson <ptkwt@aracnet.com> wrote:
In article <1115131538.406428.180220@g14g2000cwa.googlegroups.com>,
Dema <demetriusnunes@gmail.com> wrote:
>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.
Phil
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.
I've been looking at the same problem here too. If I can get BugTrack
working with PostgreSQL I plan to build upon that, the main reason is
that I am planning to build a log analysis package with RoR. My
current applicaiton is written with Python right now, but I've hit
some design issues and need to re-architect anyway (so this is a good
excuse to switch to RoR).
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.
What I eventually plan to make is an "incident response and tracking"
system. Integrating my existing log analysis code, BugTrack, data
from Snort and some configuration management tools I am writing.
BugTrack will be helpful as a starting point to the incident/response
portion (once I can figure out Rails).
Wayne
It will definitely have a pluggable architecture as we would like to
include portions of this system into our intranet. We are also
planning on writing an inventory system with ruby/rails that will
integrate with the bug tracker. So, for instance, "john" reports a
bug with some application he has installed. We want the ability to
link (plug into) to the inventory system to see what type of computer
he has, the applications he has installed, etc... This is a very
specific, but beneficial feature that we want and knowing that's not
the norm, we decided to write such a beast. There are a host of other
features that we need and will include.
Andy,
This isn't as unique as you might think, I was looking to do a similar
setup for configuration management and incident response. We
currently use Remedy for some information but I was looking to extend
that with a separate system. The problem with using Remedy for my
whole project is their security model.
My perspective on this, since I work in a security department, is
mostly compliance though.
Wayne
And if you provide me with changes, I'd be glad to include them into
BugTrack application.
Cheers,
Kent
···
On 5/3/05, Wayne Pierce <shalofin@gmail.com> wrote:
What I eventually plan to make is an "incident response and tracking"
system. Integrating my existing log analysis code, BugTrack, data
from Snort and some configuration management tools I am writing.
BugTrack will be helpful as a starting point to the incident/response
portion (once I can figure out Rails).
Wayne
Andy Stone wrote:
Thanks Phil,
As I said with the initial post, I was writing this regardless, but
just wanted to see what had been done with Ruby/Rails that I could
possibly extend. Our feature request is very specific and it's nice
to see the alternatives the other people have mentioned. (Especially
like the subversion interface)
It will definitely have a pluggable architecture as we would like to
include portions of this system into our intranet. We are also
planning on writing an inventory system with ruby/rails that will
integrate with the bug tracker. So, for instance, "john" reports a
bug with some application he has installed. We want the ability to
link (plug into) to the inventory system to see what type of computer
he has, the applications he has installed, etc... This is a very
specific, but beneficial feature that we want and knowing that's not
the norm, we decided to write such a beast. There are a host of other
features that we need and will include.
My plans for setting this up would be to use gems so it would be as
simple as rails.
I'm a big fan of Ruby and would like to see it rule the world.
thanks,
andy
We currently use Instiki for use to track bugs with task pages. What would be cool, now that Instiki is a rails app (which we haven't moved to yet), is an integration between Instiki and BugTracker. What I am thinking of is the ability to have plain wiki pages and also have every text input also be a wiki "entity". By that I mean that it could be linked to from other pages. Also it would be nice to be able to link to objects in the bug tracking system (like Bug #42 or Bug #42-Comment #3 or User:John).
I looked at Trac and it seems to have this capability from my cursory look at it.
Steve Tuckner
Wayne,
That's the thing. I don't think any of this is unique or ground
breaking. Most of what we have in mind has been done before in one
application or another. The problem is that we can't find the solution
that does everything we want. There's always the "deal breaker".
-andy
···
On 5/3/05, Wayne Pierce <shalofin@gmail.com> wrote:
> It will definitely have a pluggable architecture as we would like to
> include portions of this system into our intranet. We are also
> planning on writing an inventory system with ruby/rails that will
> integrate with the bug tracker. So, for instance, "john" reports a
> bug with some application he has installed. We want the ability to
> link (plug into) to the inventory system to see what type of computer
> he has, the applications he has installed, etc... This is a very
> specific, but beneficial feature that we want and knowing that's not
> the norm, we decided to write such a beast. There are a host of other
> features that we need and will include.
Andy,
This isn't as unique as you might think, I was looking to do a similar
setup for configuration management and incident response. We
currently use Remedy for some information but I was looking to extend
that with a separate system. The problem with using Remedy for my
whole project is their security model.
My perspective on this, since I work in a security department, is
mostly compliance though.
Wayne
Ahh Kent! Good to hear from you. The first step will definitely be to
look at BugTrack. If you don't mind I would like to run some of the
ideas by you after we have a design for what we are going to build.
Even if BugTrack doesn't match our initial design maybe we can
collaborate and work out a solution? I would really like to be able
to extend BugTrack rather than have two similar projects.
···
On 5/3/05, Kent Sibilev <ksruby@gmail.com> wrote:
And if you provide me with changes, I'd be glad to include them into
BugTrack application.
Cheers,
Kent
On 5/3/05, Wayne Pierce <shalofin@gmail.com> wrote:
> What I eventually plan to make is an "incident response and tracking"
> system. Integrating my existing log analysis code, BugTrack, data
> from Snort and some configuration management tools I am writing.
> BugTrack will be helpful as a starting point to the incident/response
> portion (once I can figure out Rails).
>
> Wayne
>
>
Sure thing. I was drugged by different projects from the BugTrack
development, but I'm planning to revive it pretty soon.
Cheers,
Kent.
···
On 5/3/05, Andy Stone <xsltguru@gmail.com> wrote:
Ahh Kent! Good to hear from you. The first step will definitely be to
look at BugTrack. If you don't mind I would like to run some of the
ideas by you after we have a design for what we are going to build.
Even if BugTrack doesn't match our initial design maybe we can
collaborate and work out a solution? I would really like to be able
to extend BugTrack rather than have two similar projects.
On 5/3/05, Kent Sibilev <ksruby@gmail.com> wrote:
> And if you provide me with changes, I'd be glad to include them into
> BugTrack application.
>
> Cheers,
> Kent
>
> On 5/3/05, Wayne Pierce <shalofin@gmail.com> wrote:
>
> > What I eventually plan to make is an "incident response and tracking"
> > system. Integrating my existing log analysis code, BugTrack, data
> > from Snort and some configuration management tools I am writing.
> > BugTrack will be helpful as a starting point to the incident/response
> > portion (once I can figure out Rails).
> >
> > Wayne
> >
> >
>
>