INN commit: trunk (8 files)
INN Commit
Russ_Allbery at isc.org
Sat Apr 4 08:06:08 UTC 2009
Date: Saturday, April 4, 2009 @ 01:06:07
Author: iulius
Revision: 8401
* Consolidate INN mailing-lists and use inn-workers instead of
inn-bugs and inn-patches.
* Mention Trac notifications in inn-bugs.
* Fix a few https links to ISC.
Modified:
trunk/TODO
trunk/contrib/README
trunk/contrib/auth_pass.README
trunk/doc/FAQ
trunk/doc/pod/hook-perl.pod
trunk/doc/pod/hook-python.pod
trunk/doc/pod/install.pod
trunk/doc/pod/readme.pod
--------------------------+
TODO | 5 +++
contrib/README | 6 ++--
contrib/auth_pass.README | 21 +++++++++++-----
doc/FAQ | 58 +++++++++++++++++++++------------------------
doc/pod/hook-perl.pod | 4 +--
doc/pod/hook-python.pod | 2 -
doc/pod/install.pod | 6 ++--
doc/pod/readme.pod | 55 ++++++++++++++++++------------------------
8 files changed, 80 insertions(+), 77 deletions(-)
Modified: TODO
===================================================================
--- TODO 2009-04-03 21:49:55 UTC (rev 8400)
+++ TODO 2009-04-04 08:06:07 UTC (rev 8401)
@@ -2,9 +2,12 @@
of INN that need work, and other tasks yet undone. Some of these may be
in progress, in which case the person working on them will be noted in
square brackets and should be contacted if you want to help. Otherwise,
-let <inn-workers at isc.org> know if you'd like to work on any item listed
+let <inn-workers at lists.isc.org> know if you'd like to work on any item listed
below.
+This list is currently being migrated to INN's issue tracking system
+<http://inn.eyrie.org/trac/>.
+
The list is divided into changes already tentatively scheduled for a
particular release, higher priority changes that will hopefully be done in
the near future, small or medium-scale projects for the future, and
Modified: contrib/README
===================================================================
--- contrib/README 2009-04-03 21:49:55 UTC (rev 8400)
+++ contrib/README 2009-04-04 08:06:07 UTC (rev 8401)
@@ -8,9 +8,9 @@
Volunteers who would like to take particularly useful applications in this
directory and make them suitable for inclusion in INN proper are heartily
-encouraged, but discuss this on <inn-workers at isc.org>. Sometimes there's a
-reason why this hasn't already been done or something specific that's
-needed before they can be included.
+encouraged, but discuss this on <inn-workers at lists.isc.org>. Sometimes
+there's a reason why this hasn't already been done or something specific
+that's needed before they can be included.
Type "make <program>" to build any of the following programs and then copy
the binary to somewhere on your PATH to use it. For details on what each
Modified: contrib/auth_pass.README
===================================================================
--- contrib/auth_pass.README 2009-04-03 21:49:55 UTC (rev 8400)
+++ contrib/auth_pass.README 2009-04-04 08:06:07 UTC (rev 8401)
@@ -1,15 +1,24 @@
This directory contains sample authorization programs for use with the
-'authinfo generic' command in nnrpd.
+AUTHINFO GENERIC command in nnrpd.
-The first program in here is from Doug Needham I have successfully
+The first program in here is from Doug Needham. I have successfully
tested this program when connecting to nnrpd by hand, but I've not
taken the time to figure out how to get my newsreader to use
-'authinfo generic'. There is no Makefile here and no serious
-testing of it, so it's not integrated. If you have success using
-it and care to share what you've done. Please drop me a note
-(<inn at isc.org>). Thanks.
+AUTHINFO GENERIC. There is no Makefile here and no serious
+testing of it, so it's not integrated. If you have success using
+it and care to share what you've done. Please drop me a note
+(<inn at isc.org>). Thanks.
+Notes:
+ * AUTHINFO GENERIC is currently deprecated in favour of
+ AUTHINFO USER/PASS and AUTHINFO SASL, as described
+ in RFC 4643.
+
+ * In case you write to <inn at isc.org>, please CC
+ <inn-workers at lists.isc.org> too.
+
+
---------------------------------------------------------------------------
Replied: Fri, 26 Jul 1996 19:29:17 +0200
Modified: doc/FAQ
===================================================================
--- doc/FAQ 2009-04-03 21:49:55 UTC (rev 8400)
+++ doc/FAQ 2009-04-04 08:06:07 UTC (rev 8401)
@@ -191,7 +191,7 @@
<http://www.eyrie.org/~eagle/software/inn/>
For additional documentation beyond what is distributed with INN, start at
-<http://www.isc.org/inn.html> and follow the links.
+<https://www.isc.org/software/inn/> and follow the links.
The documentation that comes with INN is fairly technical in nature and
lacking in some more general details on configuring news servers. Some of
@@ -242,41 +242,39 @@
There are several INN-related mailing lists:
-inn-announce at isc.org
+inn-announce at lists.isc.org
Where announcements about INN are set (no posting allowed).
-inn-workers at isc.org
- Discussion of INN development (postings by members only).
+inn-workers at lists.isc.org
+ Discussion of INN development. It is also where to send bug reports
+ and patches for consideration for inclusion into INN (postings by
+ members only). If you're an INN expert and have the time to help out
+ other users, we encourage you to join this mailing list to answer
+ questions. (You may also want to read the newsgroup
+ news.software.nntp, which gets a lot of INN-related questions.)
-inn-patches at isc.org
- Where to send patches for consideration for inclusion into INN (open
- posting).
+inn-committers at lists.isc.org
+ Subversion commit messages for INN are sent to this list (only the
+ automated messages are sent here, no regular posting).
-inn-committers at isc.org
- Subversion commit messages for INN are sent to this list (no posting
- allowed).
+inn-bugs at lists.isc.org
+ Trac tickets for INN are sent to this list (only the automated
+ messages are sent here, no regular posting). Bug reports should be
+ sent to the inn-workers mailing list.
-inn-bugs at isc.org
- Where to send bug reports (open posting). If you're an INN expert and
- have the time to help out other users, we encourage you to join this
- mailing list to answer questions. (You may also want to read the
- newsgroup news.software.nntp, which gets a lot of INN-related
- questions.)
-
To join these lists, send a subscription request to the `-request'
address. The addresses for the above lists are:
- inn-workers-request at isc.org
- inn-patches-request at isc.org
- inn-committers-request at isc.org
- inn-bugs-request at isc.org
- inn-announce-request at isc.org
+ inn-announce-request at lists.isc.org
+ inn-workers-request at lists.isc.org
+ inn-committers-request at lists.isc.org
+ inn-bugs-request at lists.isc.org
inn-workers tends to be moderate volume (3-5 messages a day, but varying a
-lot depending on what's being discussed). inn-committers is occasionally
-higher volume but entirely automatically generated commit notifications.
-inn-announce is a low-volume moderated list containing only major
-announcements. The others see sporadic, mostly low, traffic.
+lot depending on what's being discussed). inn-bugs and inn-committers are
+occasionally higher volume but entirely automatically generated Trac
+or Subversion notifications. inn-announce is a low-volume moderated list
+containing only major announcements.
------------------------------
@@ -318,7 +316,7 @@
Internet Systems Consortium has also commissioned a DHCP server
implementation and handles the official support/release of BIND. You
can learn more about the ISC's goals and accomplishments from the web
- page at <http://www.isc.org/>.
+ page at <https://www.isc.org/>.
The ISC provides ftp and web space and mailing lists and archives.
Donations to help support all of that are greatly appreciated.
@@ -349,7 +347,7 @@
doesn't currently and which you have available is often a great start, or
working on one of the supporting programs or scripts that's a bit easier
to wrap one's mind around than the core INN daemons). Patches to INN
-should be sent to inn-patches at isc.org, or put on an ftp or web site
+should be sent to inn-workers at lists.isc.org, or put on an ftp or web site
somewhere and the URL sent to inn-workers if they're extremely large.
------------------------------
@@ -495,8 +493,8 @@
This section contains specific problems that are frequently reported when
using INN, and includes fixes or suggestions for fixes. Candidates for
inclusion in this section are any problems reported frequently on
-news.software.nntp or inn-bugs at isc.org. Contributions, including fixes,
-are very welcome.
+news.software.nntp or inn-workers at lists.isc.org. Contributions, including
+fixes, are very welcome.
------------------------------
Modified: doc/pod/hook-perl.pod
===================================================================
--- doc/pod/hook-perl.pod 2009-04-03 21:49:55 UTC (rev 8400)
+++ doc/pod/hook-perl.pod 2009-04-04 08:06:07 UTC (rev 8401)
@@ -3,7 +3,7 @@
This file documents INN's built-in support for Perl filtering and reader
authentication. The code is based very heavily on work by Christophe
Wolfhugel <wolf at pasteur.fr>, and his work was in turn inspired by the
-existing TCL support. Please send any bug reports to <inn-bugs at isc.org>,
+existing TCL support. Please send any bug reports to <inn-workers at lists.isc.org>,
not to Christophe, as the code has been modified heavily since he
originally wrote it.
@@ -369,7 +369,7 @@
The old authentication functionality has been combined with the new
readers.conf mechanism by Erik Klavon <erik at eriq.org>; bug reports
-should however go to <inn-bugs at isc.org>, not Erik.
+should however go to <inn-workers at lists.isc.org>, not Erik.
The remainder of this section is an introduction to the new mechanism
(which uses the perl_auth: and perl_access: F<readers.conf> parameters)
Modified: doc/pod/hook-python.pod
===================================================================
--- doc/pod/hook-python.pod 2009-04-03 21:49:55 UTC (rev 8400)
+++ doc/pod/hook-python.pod 2009-04-04 08:06:07 UTC (rev 8401)
@@ -330,7 +330,7 @@
The old authentication and access control functionality has been
combined with the new F<readers.conf> mechanism by Erik Klavon
-<erik at eriq.org>; bug reports should however go to <inn-bugs at isc.org>,
+<erik at eriq.org>; bug reports should however go to <inn-workers at lists.isc.org>,
not Erik.
The remainder of this section is an introduction to the new mechanism
Modified: doc/pod/install.pod
===================================================================
--- doc/pod/install.pod 2009-04-03 21:49:55 UTC (rev 8400)
+++ doc/pod/install.pod 2009-04-04 08:06:07 UTC (rev 8401)
@@ -61,7 +61,7 @@
UX/4800 R11 and up
If you have gotten INN working on an operating system other than the ones
-listed above, please let us know at <inn-bugs at isc.org>.
+listed above, please let us know at <inn-workers at lists.isc.org>.
=head1 Before You Begin
@@ -176,7 +176,7 @@
=head1 Unpacking the Distribution
Released versions of INN are available from L<ftp://ftp.isc.org/isc/inn/>.
-New major releases will be announced on <inn-announce at isc.org> (see
+New major releases will be announced on <inn-announce at lists.isc.org> (see
F<README>) when they're made.
If you want a more cutting-edge version, you can obtain current
@@ -449,7 +449,7 @@
supporting programs. This option should be considered developmental at
present. For more information see F<doc/IPv6-info> (and if you have any
particularly good or bad news to report, please let us know at
-<inn-bugs at isc.org>).
+<inn-workers at lists.isc.org>).
=back
Modified: doc/pod/readme.pod
===================================================================
--- doc/pod/readme.pod 2009-04-03 21:49:55 UTC (rev 8400)
+++ doc/pod/readme.pod 2009-04-04 08:06:07 UTC (rev 8401)
@@ -125,15 +125,11 @@
We're interested in all bug reports. Not just on the programs, but on the
documentation too. Please send I<all> such reports to
- inn-bugs at isc.org
+ inn-workers at lists.isc.org
(patches are certainly welcome, see below). Even if you post to Usenet,
-please CC the above address. All other INN mail should go to
+please CC the above address.
- inn at isc.org
-
-(please do I<not> send bug reports to this address).
-
If you have general "how do I do this" questions or problems configuring
your server that you don't believe are due to a bug in INN, you should
post them to news.software.nntp. A lot of experienced INN users,
@@ -147,12 +143,11 @@
If you have a patch or a utility that you'd like to be considered for
inclusion into INN, please mail it to
- inn-patches at isc.org
+ inn-workers at lists.isc.org
-in the body of the message (not as an attachment), or put it on a
-webpage and send a link. Patches included with a bug report as
-described above should follow the same procedure, but need not be sent
-to both addresses (either will do).
+in the body of the message (not as an attachment because the mailing-list
+might strip it), or put it on a webpage and send a link. Patches included
+with a bug report as described above should follow the same procedure.
Have fun!
@@ -165,41 +160,39 @@
=over 24
-=item inn-announce at isc.org
+=item inn-announce at lists.isc.org
Where announcements about INN are set (only maintainers may post).
-=item inn-workers at isc.org
+=item inn-workers at lists.isc.org
-Discussion of INN development (postings by members only).
+Discussion of INN development. It is also where to send bug reports
+and patches for consideration for inclusion into INN (postings by
+members only). If you're an INN expert and have the time to help
+out other users, we encourage you to join this mailing list to answer
+questions. (You may also want to read the newsgroup news.software.nntp,
+which gets a lot of INN-related questions.)
-=item inn-patches at isc.org
+=item inn-committers at lists.isc.org
-Where to send patches for consideration for inclusion into INN (open
-posting).
-
-=item inn-committers at isc.org
-
Subversion commit messages for INN are sent to this list (only the automated
messages are sent here, no regular posting).
-=item inn-bugs at isc.org
+=item inn-bugs at lists.isc.org
-Where to send bug reports (open posting). If you're an INN expert and
-have the time to help out other users, we encourage you to join this
-mailing list to answer questions. (You may also want to read the
-newsgroup news.software.nntp, which gets a lot of INN-related questions.)
+Trac tickets for INN are sent to this list (only the automated messages
+are sent here, no regular posting). Bug reports should be sent to
+the inn-workers mailing list.
=back
To join these lists, send a subscription request to the C<-request>
address. The addresses for the above lists are:
- inn-announce-request at isc.org
- inn-workers-request at isc.org
- inn-patches-request at isc.org
- inn-committers-request at isc.org
- inn-bugs-request at isc.org
+ inn-announce-request at lists.isc.org
+ inn-workers-request at lists.isc.org
+ inn-committers-request at lists.isc.org
+ inn-bugs-request at lists.isc.org
=head1 Who's Responsible / Who to Thank
@@ -303,7 +296,7 @@
Internet Systems Consortium has also commissioned a DHCP server
implementation and handles the official support/release of BIND. You can
learn more about the ISC's goals and accomplishments from the web page at
-<http://www.isc.org/>.
+<https://www.isc.org/>.
Russ Allbery
Katsuhiro Kondou
More information about the inn-committers
mailing list