From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.79.9 with SMTP id c9cs39453agb; Tue, 3 Nov 2009 09:44:45 -0800 (PST) Received: by 10.224.54.206 with SMTP id r14mr153752qag.204.1257270285499; Tue, 03 Nov 2009 09:44:45 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 15si398800qyk.57.2009.11.03.09.44.45; Tue, 03 Nov 2009 09:44:45 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id C50681598099; Tue, 3 Nov 2009 12:44:44 -0500 (EST) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by rubyforge.org (Postfix) with ESMTP id 7EC67159808A for ; Tue, 3 Nov 2009 12:37:22 -0500 (EST) Received: by qw-out-2122.google.com with SMTP id 9so1185615qwb.29 for ; Tue, 03 Nov 2009 09:37:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=UNAeSgalheayfngcXmqF7oID/vNqG8htPd0A4LqpuaA=; b=Ee28Yq/5/3SLMy4wijpiwi31awNE4C1r/xPyV88uO8FZbbVQRolh5HyoqNPiFk708G 7NXF9er+P/PbdLlBKdMJMs2VdWjGpZSWn6PFyWtTwYnu0WWjLXiHyZUtymJdw5bcrIbw EamWU+SOwOtCBER2Z310ZFAickLYACLUl9LzM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=k+f2PI2hUOkDl60PAB08tdAyeM+cGlnvq37xTp6smsHkkAufB4lWQc07OSoUnZYec4 k1WDfqxzDeHDce+0CF9EBeBqY4qq3yqLj7mkMQdrOofwXKEnzI9/D0u3IREmO1HaiygC eVRFIJvRgmJbRcuNk5bvciP5S81tREiguY/Sg= MIME-Version: 1.0 Received: by 10.229.39.69 with SMTP id f5mr35425qce.107.1257269842172; Tue, 03 Nov 2009 09:37:22 -0800 (PST) In-Reply-To: <1257268977-sup-4810@masanjin.net> References: <1257111816-sup-4397@peray> <1257169654-sup-6224@masanjin.net> <02055f053011496a2dcb9085b7e7535f@localhost> <1257261315-sup-977@masanjin.net> <20091103162047.GD2963@pineapple.q.wohnheim-jahnplatz.de> <1257268977-sup-4810@masanjin.net> Date: Tue, 3 Nov 2009 13:37:22 -0400 Message-ID: From: Dan Falcone To: William Morgan Cc: sup-talk Subject: Re: [sup-talk] Choosing a bug tracker for Sup X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1959879260==" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org --===============1959879260== Content-Type: multipart/alternative; boundary=0016364275f7545da304777af2d9 --0016364275f7545da304777af2d9 Content-Type: text/plain; charset=ISO-8859-1 Hi all, Thought I'd chime in regarding RT. I've never configured it, but we use it internally where I work, so I can comment on it from a user perspective. I mainly use the email interface, which is very finicky. If you include attachments that are too large, RT will ignore your message and will not attach it to an existing ticket or open a new ticket. Our instance is well known to modify attachments (changing the md5sums), which causes all kinds of problems for us. Maybe this part is user error, but it also sends 2 copies of every message and doesn't always CC everyone on the ticket when it is supposed to. So you either get 2 copies of each email, or zero. Either way it sucks. We have lots of processes in place to work around the issues RT creates for us. Basically the only reason we use it is for archival purposes. Again, I did not install and do not administer this instance, so there could be configuration issues or possibly newer versions that address these shortcomings. However, given my past experience, I wouldn't recommend it. -Dan On Tue, Nov 3, 2009 at 1:25 PM, William Morgan wrote: > Reformatted excerpts from Sebastian Schwarz's message of 2009-11-03: > > Moreover I'd like to advertise/suggest [Roundup][1]. Apart form a slim > > web interface -- [here][2] Python's issue tracker as an example -- it > > also offers a fully functional [email interface][3], which allows -- > > from what I understand -- creating, discussing and setting properties > > like status and labels of issues. > > Nicolas suggested this too. I tried installing it locally (late on a > Sunday night, with a screaming infant in my ear) and couldn't get it to > behave. But, bugs.python.org looks great, and it looks like they're using > email to discuss and change issue state, which is awesome. I'll give it > another shot. > -- > William > _______________________________________________ > sup-talk mailing list > sup-talk@rubyforge.org > http://rubyforge.org/mailman/listinfo/sup-talk > --0016364275f7545da304777af2d9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,

Thought I'd chime in regarding RT.=A0 I've never co= nfigured it, but we use it internally where I work, so I can comment on it = from a user perspective.=A0 I mainly use the email interface, which is very= finicky.=A0 If you include attachments that are too large, RT will ignore = your message and will not attach it to an existing ticket or open a new tic= ket.=A0 Our instance is well known to modify attachments (changing the md5s= ums), which causes all kinds of problems for us.=A0 Maybe this part is user= error, but it also sends 2 copies of every message and doesn't always = CC everyone on the ticket when it is supposed to.=A0 So you either get 2 co= pies of each email, or zero.=A0 Either way it sucks. We have lots of proces= ses in place to work around the issues RT creates for us.=A0 Basically the = only reason we use it is for archival purposes.=A0

Again, I did not install and do not administer this instance, so there = could be configuration issues or possibly newer versions that address these= shortcomings.=A0 However, given my past experience, I wouldn't recomme= nd it.=A0

-Dan

On Tue, Nov 3, 2009 at 1:25 PM, = William Morgan <wmorgan-sup@masanjin.net> wrote:
Reformatted excerpts from Sebastian Schwarz's message of 2009-11-03:
> Moreover I'd like to advertise/suggest [Roundup]= [1]. =A0Apart form a slim
> web interface -- [here][2] Python's issue tracker as an example --= it
> also offers a fully functional [email interface][3], which allows -- > from what I understand -- creating, discussing and setting properties<= br> > like status and labels of issues.

Nicolas suggested this too. I tried installing it locally (late on a<= br> Sunday night, with a screaming infant in my ear) and couldn't get it to=
behave. But, bugs.pyth= on.org looks great, and it looks like they're using
email to discuss and change issue state, which is awesome. I'll give it=
another shot.
--
William <wmorgan-sup@masanji= n.net>
_______________________________________________

--0016364275f7545da304777af2d9-- --===============1959879260== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk --===============1959879260==--