Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wes@hardakers.net>
Subject: Re: GNATS backend?
Date: Mon, 14 Jan 2002 10:22:15 -0800	[thread overview]
Message-ID: <sd4rlohjxk.fsf@wanderer.hardakers.net> (raw)
In-Reply-To: <microsoft-free.x4n0zkgj24.fsf@slackware.mynet.pc> (Steve Youngs's message of "Sat, 12 Jan 2002 16:49:39 +1000")

>>>>> On Sat, 12 Jan 2002 16:49:39 +1000, Steve Youngs <youngs@xemacs.org> said:

SY> As someone who maintains a project on SF (and is on a couple of
SY> others), you've got my interest.

Yep.  ;-)  I maintain one as well and hence my reason for wanting
something in gnus.

SY> What features do you envisage nnsourceforge having?  

I want something to interact with the tracking databases.  I hate the
web interface and would love something that would let me:

Enter the group: download the current bug (say) list and display as a
   summary buffer.  A different article would be shown for the various
   reply sections within a bug report
Reply: respond to a bug request by posting the response back.
Update the various marks:
  (I'm not sure the best way to do this within gnus.  Many
  alternatives exist, like editing text field inserted into the
  message, or headers, or...)  Closing the request, "won't fix",
  "accepted", "fixed", etc.
Some gnus functions can be used to update marks in some ways as they
seem to map right in line:
  Expire: mark the item as "pending"
  Delete: delete it.
  ...

-- 
"Ninjas aren't dangerous.  They're more afraid of you than you are of them."



  parent reply	other threads:[~2002-01-14 18:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10 10:37 Pavel Janík
2002-01-12  6:08 ` Wes Hardaker
2002-01-12  6:49   ` Steve Youngs
2002-01-12 10:03     ` Kai Großjohann
2002-01-14 18:22     ` Wes Hardaker [this message]
2002-01-15  8:50       ` Kai Großjohann
2002-01-25 16:17         ` Wes Hardaker
2002-01-19 21:22       ` Lars Magne Ingebrigtsen
2002-01-25 16:20         ` Wes Hardaker
2002-01-26 22:55           ` Lars Magne Ingebrigtsen
2002-01-27  0:01             ` Daniel Pittman

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=sd4rlohjxk.fsf@wanderer.hardakers.net \
    --to=wes@hardakers.net \
    /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;
as well as URLs for NNTP newsgroup(s).