Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Subject: Re: emacs21-branch (Re: ognus)
Date: Fri, 3 Nov 2000 19:14:54 GMT	[thread overview]
Message-ID: <200011031914.TAA14435@djlvig.dl.ac.uk> (raw)
In-Reply-To: <is66m6nl69.fsf@elk.ps.uni-sb.de>

>>>>> "DD" == Denys Duchier <Denys.Duchier@ps.uni-sb.de> writes:

 DD> Why does the general public have no information and no access to
 DD> the current developments?  Why should I have to be an
 DD> `accredited' contributor in order to have access to this
 DD> information?

I'm not aware of an accreditation scheme.

Why should maintainers expend the effort to do that if it's better
devoted to improving the software?  If you are volunteering to provide
that effort, and can you show competence to do it, great, contact the
maintainer and perhaps you can change things.  (If you're competent,
you know what's involved and may think twice.)

I don't think the general public has any particular right to demand
that I, say, do this.  GNU is about cooperation and volunteers make
things happen.

 DD> When I read the user manual for a piece of software, I usually
 DD> look for urls that would let me know where it is currently
 DD> maintained and developed.  I think the Gnus user manual should of
 DD> course contain this information.

Yes.  If it doesn't you might contribute a fix.  It _is_ listed in the
released Emacs along with a bunch of other URLs which I've failed to
keep secret.  URLs are also scattered in Lisp library files'
commentary and a number have been added to defgroups, particularly in
the development sources.  They are often already out-of-date in the
released version, of course.



  parent reply	other threads:[~2000-11-03 19:14 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-27 22:59 ognus Simon Josefsson
2000-10-28  0:25 ` ognus ShengHuo ZHU
2000-10-28 13:41   ` ognus Simon Josefsson
2000-10-28 15:34     ` ognus Kai Großjohann
2000-10-28 15:41       ` ognus Simon Josefsson
2000-10-29 17:47       ` ognus Dave Love
2000-10-31 22:09     ` S/MIME and PGP/MIME (Was: Re: ognus) Bjørn Mork
2000-10-31 23:18       ` ShengHuo ZHU
2000-11-01 20:41         ` Bjørn Mork
2000-10-28 19:22   ` emacs21-branch (Re: ognus) Karl Eichwalder
2000-10-29 17:47     ` Dave Love
2000-10-29 18:48     ` Karl Eichwalder
2000-10-29 19:50       ` Kai Großjohann
2000-10-29 21:26         ` Florian Weimer
2000-10-29 22:53         ` ShengHuo ZHU
2000-10-30 22:53         ` Dave Love
2000-10-30 23:20           ` Denys Duchier
2000-10-30 23:38             ` Laura Conrad
2000-10-31  9:50               ` Denys Duchier
2000-11-02 17:25                 ` Dave Love
2000-11-02 17:34                   ` Gunnar Evermann
2000-11-03 19:09                     ` Dave Love
2000-11-03 22:07                       ` Gunnar Evermann
2000-11-02 21:01                   ` Denys Duchier
2000-11-02 22:53                     ` Kai Großjohann
2000-11-03 14:31                       ` Per Abrahamsen
2000-11-03 14:42                         ` luis fernandes
2000-11-04 11:42                         ` Steinar Bang
2000-11-04  2:52                       ` Russ Allbery
2000-11-03 19:14                     ` Dave Love [this message]
2000-11-03 19:42                       ` Denys Duchier
2000-11-04  0:04                         ` Kai Großjohann
2000-11-04 15:04                         ` Per Abrahamsen
2000-11-04 20:15                           ` Denys Duchier
2000-11-04 22:59                             ` Andreas Fuchs
2000-11-05  1:15                           ` Russ Allbery
2000-11-02 17:23             ` Dave Love
2000-10-31  0:17           ` Steven E. Harris
2000-10-31 10:09           ` Kai Großjohann
2000-10-29 17:39   ` ognus Dave Love
2000-10-30 11:35     ` ognus Per Abrahamsen
2000-10-30 13:05       ` ognus Kai Großjohann
2000-10-30 23:24         ` ognus Dave Love
2000-10-31 10:16           ` ognus Kai Großjohann
2000-11-04 20:23             ` ognus Lars Magne Ingebrigtsen
2000-11-04 22:04               ` ognus Kai Großjohann
2000-11-04 22:34                 ` ognus Lars Magne Ingebrigtsen
2000-10-30 23:22       ` ognus Dave Love
2000-10-31  9:07         ` ognus Russ Allbery
2000-10-31 13:06           ` ognus Karl Kleinpaste
2000-10-31 17:00           ` ognus Sean Doran
2000-10-31 17:55             ` ognus Kai Großjohann
2000-10-31 13:36         ` ognus Per Abrahamsen
2000-10-31 16:49           ` ognus Sean Doran
2000-11-02 17:35           ` ognus Dave Love
2000-11-02 18:08             ` ognus ShengHuo ZHU
2000-11-02 19:31               ` uunassigned code (was: Re: ognus) Per Abrahamsen
2000-11-03 19:01               ` ognus Dave Love
2000-11-02 19:18             ` ognus Per Abrahamsen
2000-11-02 23:01               ` ognus Kai Großjohann
2000-11-03 14:11                 ` ognus Per Abrahamsen
2000-11-03 19:04               ` ognus Dave Love
2000-11-04 15:11                 ` ognus Per Abrahamsen
2000-11-03 15:39             ` ognus Simon Josefsson
2000-11-04 20:31             ` ognus Lars Magne Ingebrigtsen
2000-10-31 16:37         ` ognus Sean Doran
2000-11-02 17:22           ` ognus Dave Love
2000-11-04 11:48         ` ognus Steinar Bang
2000-11-04 11:45       ` ognus Steinar Bang

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=200011031914.TAA14435@djlvig.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    /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).