From: Matt Swift <swift@alum.mit.edu>
Subject: Re: Gnus development remains haphazard?
Date: 02 Apr 2001 06:58:56 -0400 [thread overview]
Message-ID: <m2hf07tvnz.fsf@swift.shore.net> (raw)
In-Reply-To: <86n1a5ungg.fsf@muspellheim.bp.aventail.com>
>> "W" == William wrote:
W> Alan Shutko <ats@acm.org> writes:
>> Matt Swift <swift@alum.mit.edu> writes:
>>
>> > I don't have the resources or knowledge to establish a bug tracking
>> > system,
>>
>> Both sourceforge and savannah do, though. It might be useful to start
>> taking advantage of some of their tools.
W> Savannah is very nice, and would probably make a better 'official' home
W> than sourceforge. Gnus is an official GNU component, eh?
I thought of sourceforge soon after my original posting. I didn't
know about savannah.gnu.org yet, thanks.
There are also independent bug-tracking systems like Debian's BTS (I
am familiar with this as a user of it -- I think it's fantastic),
Bugzilla, and Gnats (I've never used either of these).
Gnus is an official GNU component, according the gnus.el that comes
with my Emacs 20.7, but Gnus doesn't have a page on www.gnu.org or
savannah.gnu.org, I don't think.
I am willing to help establish or maintain a Gnus presence at gnu.org,
or a different bug-tracking initiative. I have some relevant skills,
but I don't have the global knowledge of Gnus and its development to
make good high-level decisions. I invite anyone who does and wants to
coordinate an effort like this to write me privately, and I will make
some time to give some assistance.
next prev parent reply other threads:[~2001-04-02 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-28 23:14 Matt Swift
2001-03-29 0:15 ` Alan Shutko
2001-03-29 5:57 ` William M. Perry
2001-04-02 10:58 ` Matt Swift [this message]
2001-04-02 11:29 ` Kai Großjohann
2001-04-02 13:33 ` Lars Magne Ingebrigtsen
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=m2hf07tvnz.fsf@swift.shore.net \
--to=swift@alum.mit.edu \
/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).