Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Reid Thompson <reid.thompson@ateb.com>
To: Reid Thompson <reid.thompson@ateb.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Choosing a bug tracker for Sup
Date: Tue, 3 Nov 2009 12:03:38 -0500	[thread overview]
Message-ID: <20091103170338.GC20359@ateb.com> (raw)
In-Reply-To: <20091103164953.GA20359@ateb.com>

On Tue, Nov 03, 2009 at 11:49:53AM -0500, Reid Thompson wrote:
> On Tue, Nov 03, 2009 at 10:34:24AM -0500, Mike Kelly wrote:
> > 
> > On Tue, 03 Nov 2009 07:16:15 -0800, William Morgan
> > <wmorgan-sup@masanjin.net> wrote:
> > > Reformatted excerpts from Mike Kelly's message of 2009-11-03:
> > >> As much as I hate to suggest it... RT should have all of these
> > >> qualities.
> > > 
> > > Rrrrrrrrreally. Is it a pain to set up? Why do you hate to suggest it?
> > > (I've heard people complain about it before, but I don't remember any of
> > > the details.)
> > 
> > Yes, somewhat, IIRC. But, I haven't really ever had to set it up. It's one
> > of those things which requires half of CPAN to work. So, it was annoying
> > when I made an attempt to package it for a distro, but if you're just
> > installing it following their directions, it's probably not that bad.
> > 
> > But, someone is able to get away with charging $3250 a month for a
> > "platinum" managed install of it. (Then again, some enterprises will pay
> > anything for hosting...)
> > 
> > Let me try a test install real quick, and I'll get back to you.
> 
> I just started looking at it, so not sure if it fits all needs but
> fossil has a built in bugtracker
> 
> http://www.fossil-scm.org/index.html/doc/tip/www/index.wiki
> 
forgot to mention, it's developed by the same person as sqlite 
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2009-11-03 16:05 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 21:52 Nicolas Pouillard
2009-11-02  1:17 ` Kevin Riggle
2009-11-02  8:30   ` Nicolas Pouillard
2009-11-02  7:01 ` Tero Tilus
2009-11-02  8:46   ` Nicolas Pouillard
2009-11-02  9:50     ` Tero Tilus
2009-11-02 14:58       ` William Morgan
2009-11-02 14:53   ` William Morgan
2009-11-02 17:38     ` Nicolas Pouillard
2009-11-02 14:50 ` William Morgan
2009-11-02 17:47   ` Nicolas Pouillard
2009-11-02 19:20     ` William Morgan
2009-11-02 20:23       ` Nicolas Pouillard
2009-11-02 20:40   ` Joe Wölfel
2009-11-02 21:49     ` Nicolas Pouillard
2009-11-03 14:50   ` Mike Kelly
2009-11-03 15:16     ` William Morgan
2009-11-03 15:34       ` Mike Kelly
2009-11-03 16:49         ` Reid Thompson
2009-11-03 17:03           ` Reid Thompson [this message]
2009-11-03 18:04           ` William Morgan
2009-11-03 19:30             ` Reid Thompson
2009-11-03 16:20       ` Sebastian Schwarz
2009-11-03 17:03         ` Daemian Mack
2009-11-03 18:06           ` Mike Kelly
2009-11-03 17:25         ` William Morgan
2009-11-03 17:37           ` Dan Falcone
2009-11-03 18:33         ` Tero Tilus
2009-11-03 23:11 ` Jim Cheetham
2009-11-04  0:07   ` Mike Kelly
2009-11-04  9:38     ` Michael Stapelberg
2009-11-04  9:44       ` Israel Herraiz
2009-11-04 10:00         ` Michael Stapelberg
2009-11-04 10:05           ` Israel Herraiz
2009-11-04 23:40             ` Israel Herraiz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091103170338.GC20359@ateb.com \
    --to=reid.thompson@ateb.com \
    --cc=sup-talk@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox