Date: Thu, 27 Apr 1995 14:51:37 -0400 (EDT) From: Peter Dufault <dufault@hda.com> To: hackers@FreeBSD.org Subject: mailing list charters Message-ID: <199504271851.OAA05319@hda.com>
next in thread | raw e-mail | index | archive | help
The freebsd-hackers mailing list has filled with mail to the point
that many are considering (and some have) dropped out of the -hackers
list. In my opinion, this is unfortunate for FreeBSD.
Attached is a modified version of the Mailing List FAQ. It includes
charters for all lists (some minimal and needing expansion) and
proposes two new mailing lists: -chat and -policy. The charters
for the proposed new lists are:
> FREEBSD-CHAT Non technical items related to the community
> This list contains the overflow from the other lists about
> non-technical, social information. It includes discussion about
> whether Jordan looks like a tune ferret or not, whether or not to type
> in capitals, who is drinking
> too much coffee, where the best beer is brewed, and so on. Occasional
> announcements of important events (such as upcoming parties,
> weddings, births, new jobs, etc) can be made to the technical lists,
> but the follow ups should be directed to this -chat list.
> FREEBSD-POLICY Policy issues and suggestions
> This is a forum for policy discussions related to FreeBSD. This
> includes where FreeBSD is going, how to set up a consortium, whether
> or not and how to make FreeBSD pay for itself, how to attract more
> users, and so on. When a topic relates directly to FreeBSD but has
> little or no technical content then it should be sent to this list.
I propose that we add the two new lists, that we change the
description that majordomo sends about the lists to match the FAQ,
and that we gently nudge those who step outside the charter back
in line.
I shall happily do the gentle nudging for a while.
Please review this and send diffs and comments back to me, ESPECIALLY
if you know more about the lists that I'm not on and the charter
I gave them is stupid, or if you think I'm wrong and everything is
dandy the way it is. I shall summarize to the list.
....
THE FREEBSD MAILING LIST FAQ
$Id: mailing-list.FAQ,v 1.1 1995/03/21 20:19:32 jkh Exp $
--
Though many of the FreeBSD development members read USENET, we cannot
always guarantee that we'll get to your questions in a timely fashion
(or at all) if you post them only to one of the comp.unix.bsd.freebsd.*
groups. By addressing your questions to the appropriate mailing list
you will reach both us and a concentrated FreeBSD audience, hopefully
assuring a better (or at least faster) response.
There are mailing list charters at the bottom of this document.
Please read the list charter before joining a list.
LIST SUMMARY
General lists: The following are general lists that are open to
anyone.
List Purpose
-----------------------------------------------------------------------------
freebsd-announce Important events / milestones
freebsd-bugs Bug reports
freebsd-chat Non technical items related to the community
freebsd-commit Commit messages to source repository
freebsd-policy Policy issues and suggestions
freebsd-questions User questions
freebsd-current Discussions about the use of FreeBSD-current
-----------------------------------------------------------------------------
Technical lists: The following are the technical lists. You should
read the charter carefully before joining them, and you should keep
your e-mail within the scope of the guidelines. It is important to
strive to keep the signal to noise ratio of the technical lists high.
List Purpose
-----------------------------------------------------------------------------
freebsd-doc Documentation project
freebsd-fs Filesystems
freebsd-hackers General Technical discussions
freebsd-hardware General discussion of FreeBSD hardware
freebsd-platforms Porting to Non-Intel platforms
freebsd-ports Discussion of "ports"
freebsd-security Security issues
freebsd-scsi SCSI subsystem
-----------------------------------------------------------------------------
Limited lists: The following are limited lists that you will need
approval to join. Even though access to these lists is controled,
anyone is free to send suggestions and comments to them. It is a
good idea establish a presence in the technical lists before asking
to join one of these limited lists.
List Purpose
-----------------------------------------------------------------------------
freebsd-admin Administrative issues
freebsd-arch Architecture and design discussions
freebsd-core FreeBSD core team
freebsd-install Installation development
-----------------------------------------------------------------------------
CVS lists: The following lists are for people seeing the log messages
for source changes in specific areas:
List name Source area Area Description (source for)
-----------------------------------------------------------------------------
cvs-CVSROOT /usr/src/[A-Z]* Top level /usr/src file changes
cvs-all /usr/src All changes to the tree (superset)
cvs-bin /usr/src/bin System binaries
cvs-etc /usr/src/etc System files
cvs-games /usr/src/games Games
cvs-gnu /usr/src/gnu GPL'd utilities
cvs-include /usr/src/include Include files
cvs-kerberosIV /usr/src/kerberosIV Kerberos encryption code
cvs-lib /usr/src/lib System libraries
cvs-libexec /usr/src/libexec System binaries
cvs-ports /usr/ports Ported software
cvs-sbin /usr/src/sbin System binaries
cvs-share /usr/src/share System shared files
cvs-sys /usr/src/sys Kernel
cvs-usrbin /usr/src/usr.bin Use binaries
cvs-usrsbin /usr/src/usr.sbin System binaries
-----------------------------------------------------------------------------
TO SUBSCRIBE TO THE LISTS
All mailing lists live on `FreeBSD.ORG', so to post to a list you
simply mail to `<listname>@FreeBSD.ORG'. It will then be redistributed
to mailing list members throughout the world.
To subscribe to a list, send mail to:
majordomo@FreeBSD.ORG
And include the keyword
subscribe <listname> [<optional address>]
In the body of your message. For example, to subscribe yourself to
freebsd-announce, you'd do:
% mail majordomo@FreeBSD.ORG
subscribe freebsd-announce
^D
If you want to subscribe yourself under a different name, or submit a
subscription request for a local mailing list (note: this is more efficient
if you have several interested parties at one site, and highly appreciated by
us!), you would do something like:
% mail majordomo@FreeBSD.ORG
subscribe freebsd-announce local-announce@somesite.com
^D
Finally, it is also possible to unsubscribe yourself from a list, get a
list of other list members or see the list of mailing lists again by
sending other types of control messages to majordomo. For a complete
list of available commands, do this:
% mail majordomo@FreeBSD.ORG
help
^D
Finally, we again request that you keep the technical mailing lists
on a technical track. If you're only interested in the "high
points", then we suggest that you join freebsd-announce, which
contains only infrequent traffic.
LIST CHARTERS
FREEBSD-ADMIN Administrative issues
???
FREEBSD-ANNOUNCE Important events / milestones
This is the mailing list for people interested only in occasional
announcements of significant freebsd events. This includes
announcements of snapshots and other releases. It contains
announcements of new FreeBSD capabilities. It may contain calls
for volunteers etc. This is a low volume list.
FREEBSD-ARCH Architecture and design discussions
This is the mailing list for people discussing FreeBSD architectural
issues. It is a limited list requiring approval to joing
FREEBSD-BUGS Bug reports
This is the mailing list for reporting bugs in FreeBSD Whenever
possible, bugs should be submitted using "send-pr".
FREEBSD-CHAT Non technical items related to the community
This list contains the overflow from the other lists about
non-technical, social information. It includes discussion about
whether Jordan looks like a tune ferret or not, whether or not to
type in capitals, who is drinking too much coffee, where the best
beer is brewed, who is brewing beer in their basement, and so on.
Occasional announcements of important events (such as upcoming
parties, weddings, births, new jobs, etc) can be made to the
technical lists, but the follow ups should be directed to this
-chat list.
FREEBSD-COMMIT Commit messages to source repository
This is the mailing list that cvs commit messages go out to. No messages
should be sent to this list except via a cvs commit command
run on freefall.cdrom.com.
NOTE: this list will be replaced by cvs-all; please subscribe to
that list in place of freebsd-commit.
FREEBSD-CORE FreeBSD core team
This list is for use by the core team members.
???Could a core member please describe the list purpose?
FREEBSD-CURRENT Discussions about the use of FreeBSD-current
This is the mailing list for users of freebsd-current. It includes
warnings about new features coming out in -current that will affect
the users, and instructions on steps that must be taken to remain
-current. Anyone running "current" must subscribe to this list.
FREEBSD-DOC Documentation project
This mailing list belongs to the FreeBSD Documentation Project
FREEBSD-FS Filesystems
Discussions concerning FreeBSD filesystems.
FREEBSD-HACKERS Technical discussions
This is a forum for technical discussions related to FreeBSD. This
is the highest volume technical mailing list.
Individuals actively working on FreeBSD bring up problems they
are working on and discuss solutions. Individuals interested in
following the technical discussion are also welcome.
FREEBSD-HARDWARE General discussion of FreeBSD hardware
General discussion about the types of hardware that FreeBSD runs on,
various problems and suggestions concerning what to buy or avoid.
FREEBSD-INSTALL Installation discussion
This is the mailing list for people discussing FreeBSD installation
development for the new releases.
FREEBSD-PLATFORMS Porting to Non-Intel platforms
This list discusses cross-platform freebsd issues, general discussion
and proposals for non-Intel FreeBSD ports.
FREEBSD-POLICY Policy issues and suggestions
This is a forum for policy discussions related to FreeBSD. This
includes where FreeBSD is going, how to set up a consortium, whether
or not and how to make FreeBSD pay for itself, how to attract more
users, and so on. Whenever a topic is important and relates directly
to FreeBSD but has little or no technical content then it should
be sent to this list.
FREEBSD-PORTS Discussion of "ports"
Discussions concerning FreeBSD's "ports collection" (/usr/ports),
proposed ports, modifications to ports collection infrastructure
and general coordination efforts.
FREEBSD-QUESTIONS User questions
This is the mailing list for questions about FreeBSD. Most user
questions should be directed to this list, unless it is to open a
technical discussion or relates specifically to -current.
FREEBSD-SCSI SCSI subsystem
This is the mailing list for people working on the scsi subsystem
for FreeBSD.
FREEBSD-SECURITY Security issues
FreeBSD computer security issues (DES, Kerberos, known security
holes and fixes, etc).
Thank you!
--
Peter Dufault Real Time Machine Control and Simulation
HD Associates, Inc. Voice: 508 433 6936
dufault@hda.com Fax: 508 433 5267
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504271851.OAA05319>