From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6638 invoked from network); 9 Jun 2004 18:45:16 -0000 Received: from unknown (HELO lists.gnu.org) (199.232.76.165) by sourceware.org with SMTP; 9 Jun 2004 18:45:16 -0000 Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BY85F-0004Fl-7L for listarch-gnats-devel@sources.redhat.com; Wed, 09 Jun 2004 14:45:57 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BY85A-0004FU-QD for help-gnats@gnu.org; Wed, 09 Jun 2004 14:45:52 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BY858-0004FB-VB for help-gnats@gnu.org; Wed, 09 Jun 2004 14:45:52 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BY858-0004F1-TU for help-gnats@gnu.org; Wed, 09 Jun 2004 14:45:50 -0400 Received: from [207.17.137.57] (helo=colo-dns-ext1.juniper.net) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1BY83v-0001Va-MT for help-gnats@gnu.org; Wed, 09 Jun 2004 14:44:36 -0400 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id i59IiX917858 for ; Wed, 9 Jun 2004 11:44:34 -0700 (PDT) (envelope-from hatzis@juniper.net) Received: from juniper.net (ssh2.juniper.net [207.17.136.44]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i59IiSJ27207 for ; Wed, 9 Jun 2004 11:44:28 -0700 (PDT) (envelope-from hatzis@juniper.net) Message-ID: <40C75A52.3070400@juniper.net> Date: Thu, 10 Jun 2004 20:24:00 -0000 From: Mel Hatzis User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: help-gnats@gnu.org References: <40C72505.9070501@mitre.org> <20040609155225.GE23666@wookimus.net> In-Reply-To: <20040609155225.GE23666@wookimus.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: What will I dislike about GNATS? X-BeenThere: help-gnats@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: General discussion about GNU GNATS List-Archive: List-Post: List-Help: List-Subscribe: , Sender: help-gnats-bounces+listarch-gnats-devel=sources.redhat.com@gnu.org Errors-To: help-gnats-bounces+listarch-gnats-devel=sources.redhat.com@gnu.org X-SW-Source: 2004-q2/txt/msg00149.txt.bz2 On 06/09/2004 08:52 AM, Chad Walstrom submitted: > Jeff Blaine wrote: > >>Coming from the world of Req and having looked into RT and roundup, >>what makes GNATS stand out in comparison? I don't necessarily mean >>"What makes GNATS better?" I am curious to hear of its quirks or odd >>modes of workflow if they exist. I've browsed the docs and FAQ. > > > I think the biggest complaint people have is over GNATS poor > understanding of MIME. Currently, much of this can be avoided through > the use of procmail scripts and auto-responders. I have a custom > procmail script that does a pretty good job of filtering out marked > spam, viruses, and overly large emails. HTML-only emails are converted > to text, and emails that fail to enter the queue are saved to separate > mail folders. If you're interested in the RC file, just send me an > email and I'll forward it to you. > > MIME-handling enhancement is one of those big TODO's that would bring > GNATS around to modern email technology. > > While we're discussing GNATS email functionality, I have a couple of major enhancements to offer: - I've replaced the hard-coded mail-format references in the code with a new "trigger" element which makes it possible to define any number of mail-formats per trigger event. I've defined four trigger elements: on-create, on-edit, on-append and on-delete. This was accomplished with a fairly small change to the dbconfig which involves the addition of a mandatory 'trigger' clause at the beginning of each mail-format body. For example: mail-format "appended-email-response" { trigger on-append from-address { ... } Furthermore, each trigger can have an optional expression defined for it, making the mail notification conditional on PR state. For example: mail-format "initial-pr-notification-pending" { trigger on-create "Category==\"pending\"" from-address { ... } With this change, it's possible to define any number of mail-formats in the dbconfig file and place constraints on when the mail notification occurs. This is proving to be a very useful enhancement wrt work-flow. - With the assistance of a work colleague, I've made some significant changes to queue-pr providing an "edit-via-email-submission" feature. This is enabled using an "enable-edits" command line option to queue-pr. With "enable-edits" defined, the mail message is parsed for special edit directives placed at the start of the message body. These edit directives are of the form: @gnats [= | +] or @gnats + @gnats With this change, it's possible for queue-pr to update more than just the Audit-Trail. This is helping us to spread out all the valuable data captured in the Audit-Trail into other fields, significantly enhancing our query capabilities. We've also used this to build our own request system (along the lines of RT) using GNATS. I'd be happy to contribute both patches for review and possible inclusion to GNATS if people are interested. I'd also be happy to assist with an integration of these features to the GNATS code...if the folks with commit priveleges see fit to provide me with access to the CVS repository. -- Mel Hatzis _______________________________________________ Help-gnats mailing list Help-gnats@gnu.org http://lists.gnu.org/mailman/listinfo/help-gnats