svn commit: r40661 - head/en_US.ISO8859-1/books/handbook/eresources
Glen Barber
gjb at FreeBSD.org
Thu Jan 17 01:06:41 UTC 2013
Author: gjb
Date: Thu Jan 17 01:06:40 2013
New Revision: 40661
URL: http://svnweb.freebsd.org/changeset/doc/40661
Log:
Style/whitespace fixes for the eresources chapter.
Translators please ignore.
Submitted by: Dru Lavigne (via -doc, original)
Modified:
head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml Thu Jan 17 00:21:13 2013 (r40660)
+++ head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml Thu Jan 17 01:06:40 2013 (r40661)
@@ -8,18 +8,19 @@
<appendix id="eresources">
<title>Resources on the Internet</title>
- <para>The rapid pace of FreeBSD progress makes print media impractical as a
- means of following the latest developments. Electronic resources are the
- best, if not often the only, way to stay informed of the latest advances.
- Since FreeBSD is a volunteer effort, the user community itself also
- generally serves as a <quote>technical support department</quote> of sorts,
- with electronic mail, web forums, and USENET news being the most
+ <para>The rapid pace of FreeBSD progress makes print media
+ impractical as a means of following the latest developments.
+ Electronic resources are the best, if not often the only, way
+ to stay informed of the latest advances. Since FreeBSD is a
+ volunteer effort, the user community itself also generally serves
+ as a <quote>technical support department</quote> of sorts, with
+ electronic mail, web forums, and USENET news being the most
effective way of reaching that community.</para>
- <para>The most important points of contact with the FreeBSD user community
- are outlined below. If you are aware of other resources not mentioned
- here, please send them to the &a.doc; so that they may also be
- included.</para>
+ <para>The most important points of contact with the FreeBSD user
+ community are outlined below. If you are aware of other resources
+ not mentioned here, please send them to the &a.doc; so that they
+ may also be included.</para>
<sect1 id="eresources-mail">
<title>Mailing Lists</title>
@@ -31,45 +32,50 @@
most appropriate mailing list will invariably assure a faster
and more accurate response.</para>
- <para>The charters for the various lists are given at the bottom of this
- document. <emphasis>Please read the charter before joining or sending
- mail to any list</emphasis>. Most of our list subscribers now receive
- many hundreds of FreeBSD related messages every day, and by setting down
- charters and rules for proper use we are striving to keep the
- signal-to-noise ratio of the lists high. To do less would see the
- mailing lists ultimately fail as an effective communications medium for
- the project.</para>
+ <para>The charters for the various lists are given at the bottom
+ of this document. <emphasis>Please read the charter before
+ joining or sending mail to any list</emphasis>. Most of our
+ list subscribers now receive many hundreds of FreeBSD related
+ messages every day, and by setting down charters and rules for
+ proper use we are striving to keep the signal-to-noise ratio
+ of the lists high. To do less would see the mailing lists
+ ultimately fail as an effective communications medium for the
+ project.</para>
<note>
<para><emphasis>If you wish to test your ability to send to
- &os; lists, send a test message to &a.test.name;.</emphasis>
+ &os; lists, send a test message to &a.test.name;.</emphasis>
Please do not send test messages to any other list.</para>
</note>
- <para>When in doubt about what list to post a question to, see <ulink
- url="&url.articles.freebsd-questions;">How to get best results from
- the FreeBSD-questions mailing list</ulink>.</para>
-
- <para>Before posting to any list, please learn about how to best use
- the mailing lists, such as how to help avoid frequently-repeated
- discussions, by reading the <ulink url="&url.articles.mailing-list-faq;">
- Mailing List Frequently Asked Questions</ulink> (FAQ) document.</para>
-
- <para>Archives are kept for all of the mailing lists and can be searched
- using the <ulink url="&url.base;/search/index.html">FreeBSD World
- Wide Web server</ulink>. The keyword searchable archive offers an
- excellent way of finding answers to frequently asked questions and
- should be consulted before posting a question. Note that this
- also means that messages sent to FreeBSD mailing lists are
- archived in perpetuity. When protecting privacy is a
- concern, consider using a disposable secondary email address and
- posting only public information.</para>
+ <para>When in doubt about what list to post a question to, see
+ <ulink url="&url.articles.freebsd-questions;">How to get best
+ results from the FreeBSD-questions mailing
+ list</ulink>.</para>
+
+ <para>Before posting to any list, please learn about how to
+ best use the mailing lists, such as how to help avoid
+ frequently-repeated discussions, by reading the <ulink
+ url="&url.articles.mailing-list-faq;"> Mailing List Frequently
+ Asked Questions</ulink> (FAQ) document.</para>
+
+ <para>Archives are kept for all of the mailing lists and can be
+ searched using the <ulink
+ url="&url.base;/search/index.html">FreeBSD World Wide Web
+ server</ulink>. The keyword searchable archive offers an
+ excellent way of finding answers to frequently asked questions
+ and should be consulted before posting a question. Note that
+ this also means that messages sent to FreeBSD mailing lists
+ are archived in perpetuity. When protecting privacy is a
+ concern, consider using a disposable secondary email address
+ and posting only public information.</para>
<sect2 id="eresources-summary">
<title>List Summary</title>
- <para><emphasis>General lists:</emphasis> The following are general
- lists which anyone is free (and encouraged) to join:</para>
+ <para><emphasis>General lists:</emphasis> The following are
+ general lists which anyone is free (and encouraged) to
+ join:</para>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
@@ -98,11 +104,12 @@
<row>
<entry>&a.bugbusters.name;</entry>
- <entry>Discussions pertaining to the maintenance of the FreeBSD
- problem report database and related tools</entry>
+ <entry>Discussions pertaining to the maintenance of
+ the FreeBSD problem report database and related
+ tools</entry>
</row>
- <row>
+ <row>
<entry>&a.bugs.name;</entry>
<entry>Bug reports</entry>
</row>
@@ -154,17 +161,18 @@
<row>
<entry>&a.test.name;</entry>
- <entry>Where to send your test messages instead of one of
- the actual lists</entry>
+ <entry>Where to send your test messages instead of
+ one of the actual lists</entry>
</row>
</tbody>
</tgroup>
</informaltable>
- <para><emphasis>Technical lists:</emphasis> The following lists are for
- technical discussion. You should read the charter for each list
- carefully before joining or sending mail to one as there are firm
- guidelines for their use and content.</para>
+ <para><emphasis>Technical lists:</emphasis> The following
+ lists are for technical discussion. You should read the
+ charter for each list carefully before joining or sending
+ mail to one as there are firm guidelines for their use and
+ content.</para>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
@@ -188,7 +196,8 @@
<row>
<entry>&a.aic7xxx.name;</entry>
- <entry>Developing drivers for the &adaptec; AIC 7xxx</entry>
+ <entry>Developing drivers for the &adaptec;
+ AIC 7xxx</entry>
</row>
<row>
@@ -198,7 +207,9 @@
<row>
<entry>&a.apache.name;</entry>
- <entry>Discussion about <application>Apache</application> related ports</entry>
+ <entry>Discussion about
+ <application>Apache</application> related
+ ports</entry>
</row>
<row>
@@ -250,7 +261,7 @@
<row>
<entry>&a.eclipse.name;</entry>
<entry>FreeBSD users of Eclipse IDE, tools, rich client
- applications and ports.</entry>
+ applications and ports.</entry>
</row>
<row>
@@ -283,17 +294,20 @@
<row>
<entry>&a.gecko.name;</entry>
- <entry><application>Gecko Rendering Engine</application> issues</entry>
+ <entry><application>Gecko Rendering
+ Engine</application> issues</entry>
</row>
<row>
<entry>&a.geom.name;</entry>
- <entry>GEOM-specific discussions and implementations</entry>
+ <entry>GEOM-specific discussions and
+ implementations</entry>
</row>
<row>
<entry>&a.gnome.name;</entry>
- <entry>Porting <application>GNOME</application> and <application>GNOME</application> applications</entry>
+ <entry>Porting <application>GNOME</application> and
+ <application>GNOME</application> applications</entry>
</row>
<row>
@@ -314,12 +328,14 @@
<row>
<entry>&a.ia32.name;</entry>
- <entry>FreeBSD on the IA-32 (&intel; x86) platform</entry>
+ <entry>FreeBSD on the IA-32 (&intel; x86)
+ platform</entry>
</row>
<row>
<entry>&a.ia64.name;</entry>
- <entry>Porting FreeBSD to &intel;'s upcoming IA64 systems</entry>
+ <entry>Porting FreeBSD to &intel;'s upcoming IA64
+ systems</entry>
</row>
<row>
@@ -329,8 +345,8 @@
<row>
<entry>&a.ipfw.name;</entry>
- <entry>Technical discussion concerning the redesign of the IP
- firewall code</entry>
+ <entry>Technical discussion concerning the redesign
+ of the IP firewall code</entry>
</row>
<row>
@@ -340,7 +356,8 @@
<row>
<entry>&a.jail.name;</entry>
- <entry>Discussion about the &man.jail.8; facility</entry>
+ <entry>Discussion about the &man.jail.8;
+ facility</entry>
</row>
<row>
@@ -351,7 +368,8 @@
<row>
<entry>&a.kde.name;</entry>
- <entry>Porting <application>KDE</application> and <application>KDE</application> applications</entry>
+ <entry>Porting <application>KDE</application> and
+ <application>KDE</application> applications</entry>
</row>
<row>
@@ -376,7 +394,8 @@
<row>
<entry>&a.mozilla.name;</entry>
- <entry>Porting <application>Mozilla</application> to FreeBSD</entry>
+ <entry>Porting <application>Mozilla</application> to
+ FreeBSD</entry>
</row>
<row>
@@ -386,17 +405,20 @@
<row>
<entry>&a.newbus.name;</entry>
- <entry>Technical discussions about bus architecture</entry>
+ <entry>Technical discussions about bus
+ architecture</entry>
</row>
<row>
<entry>&a.net.name;</entry>
- <entry>Networking discussion and TCP/IP source code</entry>
+ <entry>Networking discussion and TCP/IP source
+ code</entry>
</row>
<row>
<entry>&a.numerics.name;</entry>
- <entry>Discussions of high quality implementation of libm functions</entry>
+ <entry>Discussions of high quality implementation of
+ libm functions</entry>
</row>
<row>
@@ -435,7 +457,8 @@
<row>
<entry>&a.ports-announce.name;</entry>
- <entry>Important news and instructions about the Ports Collection</entry>
+ <entry>Important news and instructions about the Ports
+ Collection</entry>
</row>
<row>
@@ -450,7 +473,8 @@
<row>
<entry>&a.proliant.name;</entry>
- <entry>Technical discussion of FreeBSD on HP ProLiant server platforms</entry>
+ <entry>Technical discussion of FreeBSD on HP ProLiant
+ server platforms</entry>
</row>
<row>
@@ -460,12 +484,15 @@
<row>
<entry>&a.rc.name;</entry>
- <entry>Discussion related to the <filename>rc.d</filename> system and its development</entry>
+ <entry>Discussion related to the
+ <filename>rc.d</filename> system and its
+ development</entry>
</row>
<row>
<entry>&a.realtime.name;</entry>
- <entry>Development of realtime extensions to FreeBSD</entry>
+ <entry>Development of realtime extensions to
+ FreeBSD</entry>
</row>
<row>
@@ -522,7 +549,8 @@
<row>
<entry>&a.tilera.name;</entry>
- <entry>Porting FreeBSD to the Tilera family of CPUs</entry>
+ <entry>Porting FreeBSD to the Tilera family of
+ CPUs</entry>
</row>
<row>
@@ -532,7 +560,8 @@
<row>
<entry>&a.toolchain.name;</entry>
- <entry>Maintenance of &os;'s integrated toolchain</entry>
+ <entry>Maintenance of &os;'s integrated
+ toolchain</entry>
</row>
<row>
@@ -542,8 +571,8 @@
<row>
<entry>&a.virtualization.name;</entry>
- <entry>Discussion of various virtualization techniques supported
- by &os;</entry>
+ <entry>Discussion of various virtualization techniques
+ supported by &os;</entry>
</row>
<row>
@@ -558,12 +587,14 @@
<row>
<entry>&a.xen.name;</entry>
- <entry>Discussion of the &os; port to &xen; — implementation and usage</entry>
+ <entry>Discussion of the &os; port to &xen; —
+ implementation and usage</entry>
</row>
<row>
<entry>&a.xfce.name;</entry>
- <entry><application>XFCE</application> for &os; — porting and maintaining</entry>
+ <entry><application>XFCE</application> for &os; —
+ porting and maintaining</entry>
</row>
<row>
@@ -575,11 +606,12 @@
</tgroup>
</informaltable>
- <para><emphasis>Limited lists:</emphasis> The following lists are for
- more specialized (and demanding) audiences and are probably not of
- interest to the general public. It is also a good idea to establish a
- presence in the technical lists before joining one of these limited
- lists so that you will understand the communications etiquette involved.</para>
+ <para><emphasis>Limited lists:</emphasis> The following lists
+ are for more specialized (and demanding) audiences and are
+ probably not of interest to the general public. It is also
+ a good idea to establish a presence in the technical lists
+ before joining one of these limited lists so that you will
+ understand the communications etiquette involved.</para>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
@@ -620,7 +652,9 @@
<row>
<entry>&a.www.name;</entry>
- <entry>Maintainers of <ulink url="&url.base;/index.html">www.FreeBSD.org</ulink></entry>
+ <entry>Maintainers of
+ <ulink
+ url="&url.base;/index.html">www.FreeBSD.org</ulink></entry>
</row>
</tbody>
</tgroup>
@@ -632,10 +666,10 @@
section.</para>
<para><emphasis>SVN lists:</emphasis> The following lists
- are for people interested in seeing the log messages for changes to
- various areas of the source tree. They are
- <emphasis>Read-Only</emphasis> lists and should not have mail sent to
- them.</para>
+ are for people interested in seeing the log messages for
+ changes to various areas of the source tree. They are
+ <emphasis>Read-Only</emphasis> lists and should not have
+ mail sent to them.</para>
<informaltable frame="none" pgwide="1">
<tgroup cols="3">
@@ -651,10 +685,10 @@
<row>
<entry>&a.svn-doc-all.name;</entry>
<entry><filename>/usr/doc</filename></entry>
- <entry>All changes to the doc Subversion repository (except
- for <filename>user</filename>,
- <filename>projects</filename>
- and <filename>translations</filename>)</entry>
+ <entry>All changes to the doc Subversion repository
+ (except for <filename>user</filename>,
+ <filename>projects</filename>
+ and <filename>translations</filename>)</entry>
</row>
<row>
@@ -682,14 +716,15 @@
<row>
<entry>&a.svn-ports-all.name;</entry>
<entry><filename>/usr/ports</filename></entry>
- <entry>All changes to the ports Subversion repository</entry>
+ <entry>All changes to the ports Subversion
+ repository</entry>
</row>
<row>
<entry>&a.svn-ports-head.name;</entry>
<entry><filename>/usr/ports</filename></entry>
- <entry>All changes to the <quote>head</quote> branch of
- the ports Subversion repository</entry>
+ <entry>All changes to the <quote>head</quote> branch
+ of the ports Subversion repository</entry>
</row>
<row>
@@ -703,16 +738,16 @@
<row>
<entry>&a.svn-src-all.name;</entry>
<entry><filename>/usr/src</filename></entry>
- <entry>All changes to the src Subversion repository (except
- for <filename>user</filename>
+ <entry>All changes to the src Subversion repository
+ (except for <filename>user</filename>
and <filename>projects</filename>)</entry>
</row>
<row>
<entry>&a.svn-src-head.name;</entry>
<entry><filename>/usr/src</filename></entry>
- <entry>All changes to the <quote>head</quote> branch of
- the src Subversion repository (the &os;-CURRENT
+ <entry>All changes to the <quote>head</quote> branch
+ of the src Subversion repository (the &os;-CURRENT
branch)</entry>
</row>
@@ -812,85 +847,90 @@
<title>How to Subscribe</title>
<para>To subscribe to a list, click on the list name above or
- go to &a.mailman.lists.link;
- and click on the list that you are interested in. The list
- page should contain all of the necessary subscription
- instructions.</para>
+ go to &a.mailman.lists.link; and click on the list that you
+ are interested in. The list page should contain all of the
+ necessary subscription instructions.</para>
<para>To actually post to a given list, send mail to
- <email><replaceable>listname</replaceable>@FreeBSD.org</email>. It will then
- be redistributed to mailing list members world-wide.</para>
+ <email><replaceable>listname</replaceable>@FreeBSD.org</email>.
+ It will then be redistributed to mailing list members
+ world-wide.</para>
<para>To unsubscribe yourself from a list, click on the URL
- found at the bottom of every email received from the list. It
- is also possible to send an email to
- <email><replaceable>listname</replaceable>-unsubscribe at FreeBSD.org</email> to unsubscribe
- yourself.</para>
-
- <para>Again, we would like to request that you keep discussion in the
- technical mailing lists on a technical track. If you are only
- interested in important announcements then it is suggested that
- you join the &a.announce;, which is intended only for infrequent
- traffic.</para>
+ found at the bottom of every email received from the list.
+ It is also possible to send an email to
+ <email><replaceable>listname</replaceable>-unsubscribe at FreeBSD.org</email>
+ to unsubscribe yourself.</para>
+
+ <para>Again, we would like to request that you keep discussion
+ in the technical mailing lists on a technical track. If you
+ are only interested in important announcements then it is
+ suggested that you join the &a.announce;, which is intended
+ only for infrequent traffic.</para>
</sect2>
<sect2 id="eresources-charters">
<title>List Charters</title>
- <para><emphasis>All</emphasis> FreeBSD mailing lists have certain basic
- rules which must be adhered to by anyone using them. Failure to comply
- with these guidelines will result in two (2) written warnings from the
- FreeBSD Postmaster <email>postmaster at FreeBSD.org</email>, after which,
- on a third offense, the poster will removed from all FreeBSD mailing
- lists and filtered from further posting to them. We regret that such
- rules and measures are necessary at all, but today's Internet is a
- pretty harsh environment, it would seem, and many fail to appreciate
- just how fragile some of its mechanisms are.</para>
+ <para><emphasis>All</emphasis> FreeBSD mailing lists have
+ certain basic rules which must be adhered to by anyone using
+ them. Failure to comply with these guidelines will result
+ in two (2) written warnings from the FreeBSD Postmaster
+ <email>postmaster at FreeBSD.org</email>, after which, on a
+ third offense, the poster will removed from all FreeBSD
+ mailing lists and filtered from further posting to them. We
+ regret that such rules and measures are necessary at all,
+ but today's Internet is a pretty harsh environment, it would
+ seem, and many fail to appreciate just how fragile some of
+ its mechanisms are.</para>
<para>Rules of the road:</para>
<itemizedlist>
<listitem>
- <para>The topic of any posting should adhere to the basic charter of
- the list it is posted to, e.g., if the list is about technical
- issues then your posting should contain technical discussion.
- Ongoing irrelevant chatter or flaming only detracts from the value
- of the mailing list for everyone on it and will not be tolerated.
- For free-form discussion on no particular topic, the &a.chat;
+ <para>The topic of any posting should adhere to the basic
+ charter of the list it is posted to, e.g., if the list
+ is about technical issues then your posting should contain
+ technical discussion. Ongoing irrelevant chatter or
+ flaming only detracts from the value of the mailing list
+ for everyone on it and will not be tolerated. For
+ free-form discussion on no particular topic, the &a.chat;
is freely available and should be used instead.</para>
</listitem>
<listitem>
- <para>No posting should be made to more than 2 mailing lists, and
- only to 2 when a clear and obvious need to post to both lists
- exists. For most lists, there is already a great deal of
- subscriber overlap and except for the most esoteric mixes (say
- <quote>-stable & -scsi</quote>), there really is no reason to post to more
- than one list at a time. If a message is sent to you in such a
- way that multiple mailing lists appear on the
- <literal>Cc</literal> line then the <literal>Cc</literal>
- line should also be trimmed before sending it out again.
- <emphasis>You are still responsible for your
- own cross-postings, no matter who the originator might have
- been.</emphasis></para>
+ <para>No posting should be made to more than 2 mailing
+ lists, and only to 2 when a clear and obvious need to post
+ to both lists exists. For most lists, there is already
+ a great deal of subscriber overlap and except for the most
+ esoteric mixes (say <quote>-stable & -scsi</quote>),
+ there really is no reason to post to more than one list at
+ a time. If a message is sent to you in such a way that
+ multiple mailing lists appear on the <literal>Cc</literal>
+ line then the <literal>Cc</literal> line should also be
+ trimmed before sending it out again. <emphasis>You are
+ still responsible for your own cross-postings, no matter
+ who the originator might have been.</emphasis></para>
</listitem>
<listitem>
- <para>Personal attacks and profanity (in the context of an argument)
- are not allowed, and that includes users and developers alike.
- Gross breaches of netiquette, like excerpting or reposting private
- mail when permission to do so was not and would not be
- forthcoming, are frowned upon but not specifically enforced.
- <emphasis>However</emphasis>, there are also very few cases where
- such content would fit within the charter of a list and it would
- therefore probably rate a warning (or ban) on that basis
- alone.</para>
+ <para>Personal attacks and profanity (in the context of
+ an argument) are not allowed, and that includes users
+ and developers alike. Gross breaches of netiquette,
+ like excerpting or reposting private mail when permission
+ to do so was not and would not be forthcoming, are frowned
+ upon but not specifically enforced.
+ <emphasis>However</emphasis>, there are also very few
+ cases where such content would fit within the charter
+ of a list and it would therefore probably rate a warning
+ (or ban) on that basis alone.</para>
</listitem>
<listitem>
- <para>Advertising of non-FreeBSD related products or services is
- strictly prohibited and will result in an immediate ban if it is
- clear that the offender is advertising by spam.</para>
+ <para>Advertising of non-FreeBSD related products or
+ services is strictly prohibited and will result in an
+ immediate ban if it is clear that the offender is
+ advertising by spam.</para>
</listitem>
</itemizedlist>
@@ -903,7 +943,7 @@
<listitem>
<para><emphasis>ACPI and power management
- development</emphasis></para>
+ development</emphasis></para>
</listitem>
</varlistentry>
@@ -913,8 +953,8 @@
<listitem>
<para><emphasis>Andrew File System</emphasis></para>
- <para>This list is for discussion on porting and using AFS from
- CMU/Transarc</para>
+ <para>This list is for discussion on porting and using
+ AFS from CMU/Transarc</para>
</listitem>
</varlistentry>
@@ -922,13 +962,15 @@
<term>&a.announce.name;</term>
<listitem>
- <para><emphasis>Important events / milestones</emphasis></para>
+ <para><emphasis>Important events /
+ milestones</emphasis></para>
- <para>This is the mailing list for people interested only in
- occasional announcements of significant FreeBSD events. This
- includes announcements about snapshots and other releases. It
- contains announcements of new FreeBSD capabilities. It may
- contain calls for volunteers etc. This is a low volume, strictly
+ <para>This is the mailing list for people interested
+ only in occasional announcements of significant FreeBSD
+ events. This includes announcements about snapshots
+ and other releases. It contains announcements of new
+ FreeBSD capabilities. It may contain calls for
+ volunteers etc. This is a low volume, strictly
moderated mailing list.</para>
</listitem>
</varlistentry>
@@ -940,7 +982,7 @@
<para><emphasis>Architecture and design
discussions</emphasis></para>
- <para>This list is for discussion of the FreeBSD
+ <para>This list is for discussion of the FreeBSD
architecture. Messages will mostly be kept strictly
technical in nature. Examples of suitable topics
are:</para>
@@ -952,14 +994,14 @@
</listitem>
<listitem>
- <para>What needs to be fixed with VFS to make Heidemann layers
- work.</para>
- </listitem>
+ <para>What needs to be fixed with VFS to make
+ Heidemann layers work.</para>
+ </listitem>
<listitem>
- <para>How do we change the device driver interface to be able
- to use the same drivers cleanly on many buses and
- architectures.</para>
+ <para>How do we change the device driver interface
+ to be able to use the same drivers cleanly on many
+ buses and architectures.</para>
</listitem>
<listitem>
@@ -976,10 +1018,10 @@
<para><emphasis>&bluetooth; in FreeBSD</emphasis></para>
<para>This is the forum where FreeBSD's &bluetooth; users
- congregate. Design issues, implementation details,
- patches, bug reports, status reports, feature requests,
- and all matters related to &bluetooth; are fair
- game.</para>
+ congregate. Design issues, implementation details,
+ patches, bug reports, status reports, feature requests,
+ and all matters related to &bluetooth; are fair
+ game.</para>
</listitem>
</varlistentry>
@@ -987,12 +1029,14 @@
<term>&a.bugbusters.name;</term>
<listitem>
- <para><emphasis>Coordination of the Problem Report handling effort</emphasis></para>
+ <para><emphasis>Coordination of the Problem Report
+ handling effort</emphasis></para>
- <para>The purpose of this list is to serve as a coordination and
- discussion forum for the Bugmeister, his Bugbusters, and any other
- parties who have a genuine interest in the PR database. This list
- is not for discussions about specific bugs, patches or PRs.</para>
+ <para>The purpose of this list is to serve as a
+ coordination and discussion forum for the Bugmeister,
+ his Bugbusters, and any other parties who have a genuine
+ interest in the PR database. This list is not for
+ discussions about specific bugs, patches or PRs.</para>
</listitem>
</varlistentry>
@@ -1002,10 +1046,9 @@
<listitem>
<para><emphasis>Bug reports</emphasis></para>
- <para>This is the mailing list for reporting bugs in FreeBSD.
- Whenever possible, bugs should be submitted using the
- &man.send-pr.1;
- command or the <ulink
+ <para>This is the mailing list for reporting bugs in
+ FreeBSD. Whenever possible, bugs should be submitted
+ using the &man.send-pr.1; command or the <ulink
url="&url.base;/send-pr.html">WEB
interface</ulink> to it.</para>
</listitem>
@@ -1018,15 +1061,16 @@
<para><emphasis>Non technical items related to the FreeBSD
community</emphasis></para>
- <para>This list contains the overflow from the other lists about
- non-technical, social information. It includes discussion about
- whether Jordan looks like a toon 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.</para>
+ <para>This list contains the overflow from the other
+ lists about non-technical, social information. It
+ includes discussion about whether Jordan looks like a
+ toon 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.</para>
</listitem>
</varlistentry>
@@ -1034,11 +1078,12 @@
<term>&a.chromium.name;</term>
<listitem>
- <para><emphasis>FreeBSD-specific Chromium issues</emphasis></para>
+ <para><emphasis>FreeBSD-specific Chromium
+ issues</emphasis></para>
<para>This is a list for the discussion of Chromium
- support for FreeBSD. This is a technical list to discuss
- development and installation of Chromium.</para>
+ support for FreeBSD. This is a technical list to
+ discuss development and installation of Chromium.</para>
</listitem>
</varlistentry>
@@ -1050,8 +1095,8 @@
<para>This is an internal mailing list for use by the core
members. Messages can be sent to it when a serious
- FreeBSD-related matter requires arbitration or high-level
- scrutiny.</para>
+ FreeBSD-related matter requires arbitration or
+ high-level scrutiny.</para>
</listitem>
</varlistentry>
@@ -1062,12 +1107,13 @@
<para><emphasis>Discussions about the use of
&os.current;</emphasis></para>
- <para>This is the mailing list for users of &os.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 <quote>CURRENT</quote>
- must subscribe to this list. This is a technical mailing list
- for which strictly technical content is expected.</para>
+ <para>This is the mailing list for users of &os.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 <quote>CURRENT</quote> must subscribe to this
+ list. This is a technical mailing list for which
+ strictly technical content is expected.</para>
</listitem>
</varlistentry>
@@ -1077,8 +1123,8 @@
<listitem>
<para><emphasis>FreeBSD CVSweb Project</emphasis></para>
- <para>Technical discussions about use, development and maintenance
- of FreeBSD-CVSweb.</para>
+ <para>Technical discussions about use, development and
+ maintenance of FreeBSD-CVSweb.</para>
</listitem>
</varlistentry>
@@ -1086,7 +1132,8 @@
<term>&a.desktop.name;</term>
<listitem>
- <para><emphasis>Using and improving &os; on the desktop</emphasis></para>
+ <para><emphasis>Using and improving &os; on the
+ desktop</emphasis></para>
<para>This is a forum for discussion of &os; on the
desktop. It is primarily a place for desktop porters
@@ -1101,11 +1148,12 @@
<listitem>
<para><emphasis>Documentation project</emphasis></para>
- <para>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
- <quote>The FreeBSD Documentation Project</quote>. It is an open
- list; feel free to join and contribute!</para>
+ <para>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 <quote>The FreeBSD
+ Documentation Project</quote>. It is an open list;
+ feel free to join and contribute!</para>
</listitem>
</varlistentry>
@@ -1113,13 +1161,14 @@
<term>&a.drivers.name;</term>
<listitem>
- <para><emphasis>Writing device drivers for &os;</emphasis></para>
+ <para><emphasis>Writing device drivers for
+ &os;</emphasis></para>
- <para>This is a forum for technical discussions related to
- device drivers on &os;. It is primarily a place
- for device driver writers to ask questions about
- how to write device drivers using the APIs in the
- &os; kernel.</para>
+ <para>This is a forum for technical discussions related
+ to device drivers on &os;. It is primarily a place
+ for device driver writers to ask questions about how
+ to write device drivers using the APIs in the &os;
+ kernel.</para>
</listitem>
</varlistentry>
@@ -1128,7 +1177,7 @@
<listitem>
<para><emphasis>&os; users of Eclipse IDE, tools, rich
- client applications and ports.</emphasis></para>
+ client applications and ports.</emphasis></para>
<para>The intention of this list is to provide mutual
support for everything to do with choosing, installing,
@@ -1144,8 +1193,7 @@
<para>Although this list is focused primarily on the needs
of Eclipse users it will also provide a forum for those
who would like to develop &os; specific applications
- using the Eclipse framework.
- </para>
+ using the Eclipse framework.</para>
</listitem>
</varlistentry>
@@ -1154,18 +1202,19 @@
<listitem>
<para><emphasis>Using FreeBSD in embedded
- applications</emphasis></para>
+ applications</emphasis></para>
- <para>This list discusses topics related to using FreeBSD in
- embedded systems. This is a technical mailing list for which
- strictly technical content is expected. For the purpose of
- this list we define embedded systems as those computing
- devices which are not desktops and which usually serve a
- single purpose as opposed to being general computing
- environments. Examples include, but are not limited to,
- all kinds of phone handsets, network equipment such as
- routers, switches and PBXs, remote measuring equipment,
- PDAs, Point Of Sale systems, and so on.</para>
+ <para>This list discusses topics related to using FreeBSD
+ in embedded systems. This is a technical mailing list
+ for which strictly technical content is expected. For
+ the purpose of this list we define embedded systems as
+ those computing devices which are not desktops and which
+ usually serve a single purpose as opposed to being
+ general computing environments. Examples include, but
+ are not limited to, all kinds of phone handsets, network
+ equipment such as routers, switches and PBXs, remote
+ measuring equipment, PDAs, Point Of Sale systems, and
+ so on.</para>
</listitem>
</varlistentry>
@@ -1176,9 +1225,9 @@
<para><emphasis>Emulation of other systems such as
Linux/&ms-dos;/&windows;</emphasis></para>
- <para>This is a forum for technical discussions related to
- running programs written for other operating systems on &os;.
- </para>
+ <para>This is a forum for technical discussions related
+ to running programs written for other operating systems
+ on &os;.</para>
</listitem>
</varlistentry>
@@ -1186,13 +1235,15 @@
<term>&a.eol.name;</term>
<listitem>
- <para><emphasis>Peer support of FreeBSD-related software that is
- no longer supported by the FreeBSD project.</emphasis></para>
-
- <para>This list is for those interested in providing or making use
- of peer support of FreeBSD-related software for which the
- FreeBSD project no longer provides official support (e.g., in
- the form of security advisories and patches).</para>
+ <para><emphasis>Peer support of FreeBSD-related software
+ that is no longer supported by the FreeBSD
+ project.</emphasis></para>
+
+ <para>This list is for those interested in providing or
+ making use of peer support of FreeBSD-related software
+ for which the FreeBSD project no longer provides
+ official support (e.g., in the form of security
+ advisories and patches).</para>
</listitem>
</varlistentry>
@@ -1200,7 +1251,8 @@
<term>&a.firewire.name;</term>
<listitem>
- <para><emphasis>&firewire; (iLink, IEEE 1394)</emphasis></para>
+ <para><emphasis>&firewire; (iLink, IEEE
+ 1394)</emphasis></para>
<para>This is a mailing list for discussion of the design
and implementation of a &firewire; (aka IEEE 1394 aka
@@ -1218,9 +1270,9 @@
<listitem>
<para><emphasis>File systems</emphasis></para>
- <para>Discussions concerning FreeBSD file systems. This is a
- technical mailing list for which strictly technical content is
- expected.</para>
+ <para>Discussions concerning FreeBSD file systems.
+ This is a technical mailing list for which strictly
+ technical content is expected.</para>
</listitem>
</varlistentry>
@@ -1230,8 +1282,9 @@
<listitem>
<para><emphasis>Gecko Rendering Engine</emphasis></para>
- <para>This is a forum about <application>Gecko</application>
- applications using &os;.</para>
+ <para>This is a forum about
+ <application>Gecko</application> applications using
+ &os;.</para>
<para>Discussion centers around Gecko Ports applications,
their installation, their development and their support
@@ -1245,9 +1298,9 @@
<listitem>
<para><emphasis>GEOM</emphasis></para>
- <para>Discussions specific to GEOM and related implementations.
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-all
mailing list