os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Clarify roles of the -questions and -doc lists. Based on suggestions from

Browse source 
Jason C. Wells" <jcwells@u.washington.edu> on the freebsd-doc mailing
lists.  (ref message-id:
<Pine.BSF.4.05.9812151123040.962-100000@s8-37-26.student.washington.edu>).

Reviewed by: 	nik
This commit is contained in:
Joseph Koshy 1998-12-18 03:07:24 +00:00
parent 3e6d92344e
commit c67b438dfc
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=3938
1 changed files with 18 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
handbook/eresources.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: eresources.sgml,v 1.52 1998-12-09 13:07:28 wosch Exp $ -->
<!-- $Id: eresources.sgml,v 1.53 1998-12-18 03:07:24 jkoshy Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt>
@ -55,11 +55,11 @@ freebsd-announce Important events and project milestones
freebsd-bugs Bug reports
freebsd-chat Non-technical items related to the FreeBSD community
freebsd-current Discussion concerning the use of FreeBSD-current
freebsd-stable Discussion concerning the use of FreeBSD-stable
freebsd-isp Issues for Internet Service Providers using FreeBSD
freebsd-jobs FreeBSD employment and consulting opportunities
freebsd-newbies New FreeBSD users activities and discussion
freebsd-questions User questions
freebsd-questions User questions and technical support
freebsd-stable Discussion concerning the use of FreeBSD-stable
</verb>
<bf>Technical lists:</bf> The following lists are for technical discussion.
@ -70,7 +70,7 @@ List Purpose
----------------------------------------------------------------------
freebsd-afs Porting AFS to FreeBSD
freebsd-alpha Porting FreeBSD to the Alpha
freebsd-doc The FreeBSD Documentation project
freebsd-doc Creating FreeBSD related documents
freebsd-database Discussing database use and developement under FreeBSD
freebsd-emulation Emulation of other systems such as Linux/DOS/Windows
freebsd-fs Filesystems
@ -286,20 +286,11 @@ messages sent to freebsd-current bundled together and mailed out
as a single message. The average digest size is about 40kB.
This list is <bf>Read-Only</bf> and should not be posted to.
<tag/FREEBSD-STABLE/ <em>Discussions about the use of
FreeBSD-stable</em><newline> This is the mailing list for users
of freebsd-stable. It includes warnings about new features
coming out in -stable that will affect the users, and
instructions on steps that must be taken to remain -stable.
Anyone running ``stable'' should subscribe to this list.
This is a technical mailing list for which strictly technical
content is expected.
<tag/FREEBSD-DOC/ <em>Documentation project</em><newline>
This mailing list is for the discussion of documentation related
issues and projects. The members of this mailing list is collectively
referred to as 'The FreeBSD Documentation project'. It is an open
list; feel free to join and contribute!
<tag/FREEBSD-DOC/ <em>The FreeBSD Documentation project</em><newline>
This mailing list is for the discussion of issues and projects related
to the creation of documentation for FreeBSD. The members of this mailing
list are collectively referred to as 'The FreeBSD Documentation project'.
It is an open list; feel free to join and contribute!
<tag/FREEBSD-FS/ <em>Filesystems</em><newline>
Discussions concerning FreeBSD filesystems.
@ -402,6 +393,15 @@ FreeBSD installations.
This is a technical mailing list for which strictly technical
content is expected.
<tag/FREEBSD-STABLE/ <em>Discussions about the use of
FreeBSD-stable</em><newline> This is the mailing list for users
of freebsd-stable. It includes warnings about new features
coming out in -stable that will affect the users, and
instructions on steps that must be taken to remain -stable.
Anyone running ``stable'' should subscribe to this list.
This is a technical mailing list for which strictly technical
content is expected.
<tag/FREEBSD-USER-GROUPS/ <em>User Group Coordination List</em><newline>
This is the mailing list for the coordinators from each of the
local area Users Groups to discuss matters with each other and a