Date: Fri, 18 Jan 2013 07:21:20 -0800 (PST) From: Dru Lavigne <dru.lavigne@att.net> To: freebsd-doc@freebsd.org Subject: [patch] first pass at Appendix C Message-ID: <1358522480.41802.YahooMailClassic@web184902.mail.gq1.yahoo.com>
index | next in thread | raw e-mail
[-- Attachment #1 --]
This is a content patch which does the following:
- removes section C.4
- removes deprecated usenet groups as well as the X groups in C.2
- moves the list charter descriptions into C.1.1 and cleans up their wording
- removes the obsolete lists in C.2 (e.g. TokenRing)
This patch does not do the following which will be done in the second pass:
- add the missing lists; these need to have entities created first
Section C.2 will probably be more readable as 4 tables. If someone has the time to help me get started with table formatting, I will do that in the second pass.
The second pass may also shuffle about C.1 a bit to make it clearer on how to subscribe, etc.
Cheers,
Dru
[-- Attachment #2 --]
Index: eresources/chapter.xml
===================================================================
--- eresources/chapter.xml (revision 40677)
+++ eresources/chapter.xml (working copy)
@@ -8,16 +8,16 @@
<appendix id="eresources">
<title>Resources on the Internet</title>
- <para>The rapid pace of FreeBSD progress makes print media
+ <para>The rapid pace of &os; 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
+ to stay informed of the latest advances. Since &os; 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
+ <para>The most important points of contact with the &os; 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>
@@ -25,22 +25,22 @@
<sect1 id="eresources-mail">
<title>Mailing Lists</title>
- <para>The mailing lists are the most direct way of addressing
- questions or opening a technical discussion to a concentrated
- FreeBSD audience. There are a wide variety of lists on a number
- of different FreeBSD topics. Addressing your questions to the
- most appropriate mailing list will invariably assure a faster
- and more accurate response.</para>
+ <para>The &a.mailman.lists.link; are the most direct way of
+ addressing questions or opening a technical discussion to a
+ concentrated &os; audience. There are a wide variety of lists
+ on a number of different &os; topics. Addressing your questions
+ to the 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 available mailing lists and their descriptions are
+ listed below. <emphasis>Please read and adhere to the mailing
+ list's charter when subscribing and before sending mail to a
+ list</emphasis>. Most list subscribers receive many hundreds
+ of &os; related messages every day. 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
@@ -50,1917 +50,1126 @@
<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
+ results from the &os;-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
+ <para>Before posting to any list, please learn how to best use
+ the mailing lists and help to avoid frequently repeated
+ discussions by reading the <ulink
url="&url.articles.mailing-list-faq;"> Mailing List Frequently
- Asked Questions</ulink> (FAQ) document.</para>
+ 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>Archives are kept for all of the mailing lists and can be
+ searched using the <ulink
+ url="&url.base;/search/index.html">&os; World Wide Web
+ server</ulink>. The keyword searchable archive offers an
+ excellent way to find answers to frequently asked questions
+ and should be consulted before posting a question. Note that
+ this also means that messages sent to &os; 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>Digest lists:</emphasis> All &os; mailing lists
+ are available in a digest format. Once subscribed to a
+ list, you can change your digest options in your account options
+ section.</para>
- <para><emphasis>General lists:</emphasis> The following are
- general lists which anyone is free (and encouraged) to
- join:</para>
+ <sect2 id="eresources-summary">
+ <title>List Summary</title>
- <informaltable frame="none" pgwide="1">
- <tgroup cols="2">
- <thead>
- <row>
- <entry>List</entry>
- <entry>Purpose</entry>
- </row>
- </thead>
+ <para><emphasis>General lists:</emphasis> The following are
+ general lists which anyone is free (and encouraged) to
+ join:</para>
- <tbody>
- <row>
- <entry>&a.advocacy.name;</entry>
- <entry>FreeBSD Evangelism</entry>
- </row>
+ <informaltable frame="none" pgwide="1">
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>List</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
- <row>
- <entry>&a.announce.name;</entry>
- <entry>Important events and project milestones</entry>
- </row>
+ <tbody>
+ <row>
+ <entry>&a.advocacy.name;</entry>
+ <entry>Used to share ideas and plans to increase the
+ number of companies and individuals using &os;</entry>
+ </row>
- <row>
- <entry>&a.arch.name;</entry>
- <entry>Architecture and design discussions</entry>
- </row>
+ <row>
+ <entry>&a.announce.name;</entry>
+ <entry>This is the mailing list for people interested
+ in occasional announcements of significant &os;
+ events and project milestones, including
+ announcements about snapshots, releases, new &os;
+ capabilities, and calls for volunteers.</entry>
+ </row>
- <row>
- <entry>&a.bugbusters.name;</entry>
- <entry>Discussions pertaining to the maintenance of
- the FreeBSD problem report database and related
- tools</entry>
- </row>
+ <row>
+ <entry>&a.arch.name;</entry>
+ <entry>Technical list for architecture and design
+ discussions. Read the list charter for examples of
+ suitable and non-suitable topics.</entry>
+ </row>
- <row>
- <entry>&a.bugs.name;</entry>
- <entry>Bug reports</entry>
- </row>
+ <row>
+ <entry>&a.bugbusters.name;</entry>
+ <entry>Discussions pertaining to the maintenance of
+ the &os; problem report database and related
+ tools. This list is not for discussions about
+ specific bugs, patches or PRs.</entry>
+ </row>
- <row>
- <entry>&a.chat.name;</entry>
- <entry>Non-technical items related to the FreeBSD
- community</entry>
- </row>
+ <row>
+ <entry>&a.bugs.name;</entry>
+ <entry>This is the mailing list for reporting bugs in
+ &os;. Whenever possible, bugs should instead be
+ submitted using the &man.send-pr.1; command or <ulink
+ url="&url.base;/send-pr.html">WEB
+ interface</ulink>.</entry>
+ </row>
- <row>
- <entry>&a.chromium.name;</entry>
- <entry>FreeBSD-specific Chromium issues</entry>
- </row>
+ <row>
+ <entry>&a.chat.name;</entry>
+ <entry>This list contains the overflow from the other
+ lists about non-technical, social information
+ related to the &os; community.</entry>
+ </row>
- <row>
- <entry>&a.current.name;</entry>
- <entry>Discussion concerning the use of
- &os.current;</entry>
- </row>
+ <row>
+ <entry>&a.chromium.name;</entry>
+ <entry>This is a technical list for the discussion of
+ Chromium support for &os;, including development and
+ installation of Chromium.</entry>
+ </row>
- <row>
- <entry>&a.isp.name;</entry>
- <entry>Issues for Internet Service Providers using
- FreeBSD</entry>
- </row>
+ <row>
+ <entry>&a.current.name;</entry>
+ <entry>This is the mailing list for users of
+ &os.current;. It includes warnings about new features
+ in &os.current; that will affect the users, and
+ instructions on steps that must be taken to remain
+ &os.current;.</entry>
+ </row>
- <row>
- <entry>&a.jobs.name;</entry>
- <entry>FreeBSD employment and consulting
- opportunities</entry>
- </row>
+ <row>
+ <entry>&a.isp.name;</entry>
+ <entry>Technical mailing list for discussing topics
+ relevant to Internet Service Providers (ISPs) using
+ &os;.</entry>
+ </row>
- <row>
- <entry>&a.questions.name;</entry>
- <entry>User questions and technical support</entry>
- </row>
+ <row>
+ <entry>&a.jobs.name;</entry>
+ <entry>This is a forum for posting employment notices
+ and resumes specifically related to &os;. Post here
+ if you are seeking &os;-related employment or have
+ a job involving &os; to advertise. This is
+ <emphasis>not</emphasis> a mailing list for
+ discussing general employment issues. Since this
+ list is distributed worldwide, be clear about the
+ job location and the extent to which telecommuting
+ or relocation assistance is available. Postings
+ should use open formats only, preferably plain
+ text, but basic (<acronym>PDF</acronym>) and HTML
+ are acceptable to many readers. Closed formats such
+ as µsoft; Word (<filename>.doc</filename>) will
+ be rejected by the mailing list server.</entry>
+ </row>
- <row>
- <entry>&a.security-notifications.name;</entry>
- <entry>Security notifications</entry>
- </row>
+ <row>
+ <entry>&a.questions.name;</entry>
+ <entry>User questions and technical support
+ about &os;. Send questions to this list instead of
+ the technical lists unless you consider the question
+ to be very technical.</entry>
+ </row>
- <row>
- <entry>&a.stable.name;</entry>
- <entry>Discussion concerning the use of
- &os.stable;</entry>
- </row>
+ <row>
+ <entry>&a.security-notifications.name;</entry>
+ <entry>Notification-only list of &os; security problems
+ and fixes. For security discussions, use
+ &a.security-notifications.name;.</entry>
+ </row>
- <row>
- <entry>&a.test.name;</entry>
- <entry>Where to send your test messages instead of
- one of the actual lists</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
+ <row>
+ <entry>&a.stable.name;</entry>
+ <entry>Technical mailing list for users of
+ &os.stable;. It includes warnings about new features
+ in &os.stable; that affect users and instructions
+ on steps that must be taken to remain
+ &os.stable;.</entry>
+ </row>
- <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>
+ <row>
+ <entry>&a.test.name;</entry>
+ <entry>Where to send your test messages instead of
+ one of the actual lists.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
- <informaltable frame="none" pgwide="1">
- <tgroup cols="2">
- <thead>
- <row>
- <entry>List</entry>
- <entry>Purpose</entry>
- </row>
- </thead>
+ <para><emphasis>Technical lists:</emphasis> The following
+ lists are for technical discussion. Read the charter for
+ each list carefully before subscribing or sending
+ mail to one of these lists as there are firm guidelines for
+ their use and content.</para>
- <tbody>
- <row>
- <entry>&a.acpi.name;</entry>
- <entry>ACPI and power management development</entry>
- </row>
+ <informaltable frame="none" pgwide="1">
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>List</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
- <row>
- <entry>&a.afs.name;</entry>
- <entry>Porting AFS to FreeBSD</entry>
- </row>
+ <tbody>
+ <row>
+ <entry>&a.acpi.name;</entry>
+ <entry>This list is for discussing the Advanced
+ Configuration and Power Interface (ACPI) support in
+ &os;, including bug fixing and developing new
+ features. General power management discussions are
+ also welcome.</entry>
+ </row>
- <row>
- <entry>&a.aic7xxx.name;</entry>
- <entry>Developing drivers for the &adaptec;
- AIC 7xxx</entry>
- </row>
+ <row>
+ <entry>&a.afs.name;</entry>
+ <entry>This list is for discussion on porting the
+ Andrew File System (AFS) to &os;</entry>
+ </row>
- <row>
- <entry>&a.amd64.name;</entry>
- <entry>Porting FreeBSD to AMD64 systems</entry>
- </row>
+ <row>
+ <entry>&a.aic7xxx.name;</entry>
+ <entry>This list is dedicated to the discussion of the
+ Adaptec aic7xxx family of disk controllers and the
+ driver support for them in &os; and &linux;. This
+ includes the AHA-274X, AHA-284X, AHA-2940, AHA-3940,
+ and AHA-398X adapters.</entry>
+ </row>
- <row>
- <entry>&a.apache.name;</entry>
- <entry>Discussion about
- <application>Apache</application> related
- ports</entry>
- </row>
+ <row>
+ <entry>&a.amd64.name;</entry>
+ <entry>This is the technical mailing list for
+ individuals actively working on porting &os; to the
+ 64-bit platform from AMD, to bring up problems or
+ discuss alternative solutions. Individuals interested
+ in following the technical discussion are also
+ welcome.</entry>
+ </row>
- <row>
- <entry>&a.arm.name;</entry>
- <entry>Porting FreeBSD to &arm; processors</entry>
- </row>
+ <row>
+ <entry>&a.apache.name;</entry>
+ <entry>This mailing list provides a place to discuss
+ <application>Apache</application> related ports as
+ well as their configuration and tuning issues.</entry>
+ </row>
- <row>
- <entry>&a.atm.name;</entry>
- <entry>Using ATM networking with FreeBSD</entry>
- </row>
+ <row>
+ <entry>&a.arm.name;</entry>
+ <entry>This is the technical mailing list for
+ individuals actively working on porting FreeBSD to
+ &arm; processors. Individuals interested in following
+ the technical discussion are also welcome.</entry>
+ </row>
- <row>
- <entry>&a.bluetooth.name;</entry>
- <entry>Using &bluetooth; technology in FreeBSD</entry>
- </row>
+ <row>
+ <entry>&a.atm.name;</entry>
+ <entry>This is the technical mailing list for
+ individuals using ATM networking with &os;</entry>
+ </row>
- <row>
- <entry>&a.cluster.name;</entry>
- <entry>Using FreeBSD in a clustered environment</entry>
- </row>
+ <row>
+ <entry>&a.bluetooth.name;</entry>
+ <entry>Mailing list for using &bluetooth; technology
+ in &os;. Topics include design issues, implementation
+ details, patches, bug reports, status reports, feature
+ requests, and all matters related to
+ &bluetooth;.</entry>
+ </row>
- <row>
- <entry>&a.cvsweb.name;</entry>
- <entry>CVSweb maintenance</entry>
- </row>
+ <row>
+ <entry>&a.cluster.name;</entry>
+ <entry>This is a forum for technical discussions related
+ to using &os; in a clustered environment.</entry>
+ </row>
- <row>
- <entry>&a.database.name;</entry>
- <entry>Discussing database use and development under
- FreeBSD</entry>
- </row>
+ <row>
+ <entry>&a.cvsweb.name;</entry>
+ <entry>List for technical discussions about the use,
+ development and maintenance of &os; CVSweb.</entry>
+ </row>
- <row>
- <entry>&a.desktop.name;</entry>
- <entry>Using and improving &os; on the desktop</entry>
- </row>
+ <row>
+ <entry>&a.database.name;</entry>
+ <entry>List for iscussing database use and development
+ under &os;</entry>
+ </row>
- <row>
- <entry>&a.doc.name;</entry>
- <entry>Creating FreeBSD related documents</entry>
- </row>
-
- <row>
- <entry>&a.drivers.name;</entry>
- <entry>Writing device drivers for &os;</entry>
- </row>
-
- <row>
- <entry>&a.eclipse.name;</entry>
- <entry>FreeBSD users of Eclipse IDE, tools, rich client
- applications and ports.</entry>
- </row>
-
- <row>
- <entry>&a.embedded.name;</entry>
- <entry>Using FreeBSD in embedded applications</entry>
- </row>
-
- <row>
- <entry>&a.eol.name;</entry>
- <entry>Peer support of FreeBSD-related software that
- is no longer supported by the FreeBSD project.</entry>
- </row>
-
- <row>
- <entry>&a.emulation.name;</entry>
- <entry>Emulation of other systems such as
- Linux/&ms-dos;/&windows;</entry>
- </row>
-
- <row>
- <entry>&a.firewire.name;</entry>
- <entry>FreeBSD &firewire; (iLink, IEEE 1394) technical
- discussion</entry>
- </row>
-
- <row>
- <entry>&a.fs.name;</entry>
- <entry>File systems</entry>
- </row>
-
- <row>
- <entry>&a.gecko.name;</entry>
- <entry><application>Gecko Rendering
- Engine</application> issues</entry>
- </row>
-
- <row>
- <entry>&a.geom.name;</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>
- </row>
-
- <row>
- <entry>&a.hackers.name;</entry>
- <entry>General technical discussion</entry>
- </row>
-
- <row>
- <entry>&a.hardware.name;</entry>
- <entry>General discussion of hardware for running
- FreeBSD</entry>
- </row>
-
- <row>
- <entry>&a.i18n.name;</entry>
- <entry>FreeBSD Internationalization</entry>
- </row>
-
- <row>
- <entry>&a.ia32.name;</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>
- </row>
-
- <row>
- <entry>&a.infiniband.name;</entry>
- <entry>Infiniband on FreeBSD</entry>
- </row>
-
- <row>
- <entry>&a.ipfw.name;</entry>
- <entry>Technical discussion concerning the redesign
- of the IP firewall code</entry>
- </row>
-
- <row>
- <entry>&a.isdn.name;</entry>
- <entry>ISDN developers</entry>
- </row>
-
- <row>
- <entry>&a.jail.name;</entry>
- <entry>Discussion about the &man.jail.8;
- facility</entry>
- </row>
-
- <row>
- <entry>&a.java.name;</entry>
- <entry>&java; developers and people porting &jdk;s to
- FreeBSD</entry>
- </row>
-
- <row>
- <entry>&a.kde.name;</entry>
- <entry>Porting <application>KDE</application> and
- <application>KDE</application> applications</entry>
- </row>
-
- <row>
- <entry>&a.lfs.name;</entry>
- <entry>Porting LFS to FreeBSD</entry>
- </row>
-
- <row>
- <entry>&a.mips.name;</entry>
- <entry>Porting FreeBSD to &mips;</entry>
- </row>
-
- <row>
- <entry>&a.mobile.name;</entry>
- <entry>Discussions about mobile computing</entry>
- </row>
-
- <row>
- <entry>&a.mono.name;</entry>
- <entry>Mono and C# applications on FreeBSD</entry>
- </row>
-
- <row>
- <entry>&a.mozilla.name;</entry>
- <entry>Porting <application>Mozilla</application> to
- FreeBSD</entry>
- </row>
-
- <row>
- <entry>&a.multimedia.name;</entry>
- <entry>Multimedia applications</entry>
- </row>
-
- <row>
- <entry>&a.newbus.name;</entry>
- <entry>Technical discussions about bus
- architecture</entry>
- </row>
-
- <row>
- <entry>&a.net.name;</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>
- </row>
-
- <row>
- <entry>&a.office.name;</entry>
- <entry>Office applications on &os;</entry>
- </row>
-
- <row>
- <entry>&a.performance.name;</entry>
- <entry>Performance tuning questions for high
- performance/load installations</entry>
- </row>
-
- <row>
- <entry>&a.perl.name;</entry>
- <entry>Maintenance of a number of
- Perl-related ports</entry>
- </row>
-
- <row>
- <entry>&a.pf.name;</entry>
- <entry>Discussion and questions about the packet filter
- firewall system</entry>
- </row>
-
- <row>
- <entry>&a.platforms.name;</entry>
- <entry>Concerning ports to non &intel; architecture
- platforms</entry>
- </row>
-
- <row>
- <entry>&a.ports.name;</entry>
- <entry>Discussion of the Ports Collection</entry>
- </row>
-
- <row>
- <entry>&a.ports-announce.name;</entry>
- <entry>Important news and instructions about the Ports
- Collection</entry>
- </row>
-
- <row>
- <entry>&a.ports-bugs.name;</entry>
- <entry>Discussion of the ports bugs/PRs</entry>
- </row>
-
- <row>
- <entry>&a.ppc.name;</entry>
- <entry>Porting FreeBSD to the &powerpc;</entry>
- </row>
-
- <row>
- <entry>&a.proliant.name;</entry>
- <entry>Technical discussion of FreeBSD on HP ProLiant
- server platforms</entry>
- </row>
-
- <row>
- <entry>&a.python.name;</entry>
- <entry>FreeBSD-specific Python issues</entry>
- </row>
-
- <row>
- <entry>&a.rc.name;</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>
- </row>
-
- <row>
- <entry>&a.ruby.name;</entry>
- <entry>FreeBSD-specific Ruby discussions</entry>
- </row>
-
- <row>
- <entry>&a.scsi.name;</entry>
- <entry>The SCSI subsystem</entry>
- </row>
-
- <row>
- <entry>&a.security.name;</entry>
- <entry>Security issues affecting FreeBSD</entry>
- </row>
-
- <row>
- <entry>&a.small.name;</entry>
- <entry>Using FreeBSD in embedded applications
- (obsolete; use &a.embedded.name; instead)</entry>
- </row>
-
- <row>
- <entry>&a.snapshots.name;</entry>
- <entry>&os; Development Snapshot Announcements</entry>
- </row>
-
- <row>
- <entry>&a.sparc.name;</entry>
- <entry>Porting FreeBSD to &sparc; based systems</entry>
- </row>
-
- <row>
- <entry>&a.standards.name;</entry>
- <entry>FreeBSD's conformance to the C99 and the &posix;
- standards</entry>
- </row>
-
- <row>
- <entry>&a.sysinstall.name;</entry>
- <entry>&man.sysinstall.8; development</entry>
- </row>
-
- <row>
- <entry>&a.tcltk.name;</entry>
- <entry>FreeBSD-specific Tcl/Tk discussions</entry>
- </row>
-
- <row>
- <entry>&a.threads.name;</entry>
- <entry>Threading in FreeBSD</entry>
- </row>
-
- <row>
- <entry>&a.tilera.name;</entry>
- <entry>Porting FreeBSD to the Tilera family of
- CPUs</entry>
- </row>
-
- <row>
- <entry>&a.tokenring.name;</entry>
- <entry>Support Token Ring in FreeBSD</entry>
- </row>
-
- <row>
- <entry>&a.toolchain.name;</entry>
- <entry>Maintenance of &os;'s integrated
- toolchain</entry>
- </row>
-
- <row>
- <entry>&a.usb.name;</entry>
- <entry>Discussing &os; support for USB</entry>
- </row>
-
- <row>
- <entry>&a.virtualization.name;</entry>
- <entry>Discussion of various virtualization techniques
- supported by &os;</entry>
- </row>
-
- <row>
- <entry>&a.vuxml.name;</entry>
- <entry>Discussion on VuXML infrastructure</entry>
- </row>
-
- <row>
- <entry>&a.x11.name;</entry>
- <entry>Maintenance and support of X11 on FreeBSD</entry>
- </row>
-
- <row>
- <entry>&a.xen.name;</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>
- </row>
-
- <row>
- <entry>&a.zope.name;</entry>
- <entry><application>Zope</application> for &os; —
- porting and maintaining</entry>
- </row>
- </tbody>
- </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>
-
- <informaltable frame="none" pgwide="1">
- <tgroup cols="2">
- <thead>
- <row>
- <entry>List</entry>
- <entry>Purpose</entry>
- </row>
- </thead>
-
- <tbody>
- <row>
- <entry>&a.hubs.name;</entry>
- <entry>People running mirror sites (infrastructural
- support)</entry>
- </row>
-
- <row>
- <entry>&a.usergroups.name;</entry>
- <entry>User group coordination</entry>
- </row>
-
- <row>
- <entry>&a.vendors.name;</entry>
- <entry>Vendors pre-release coordination</entry>
- </row>
-
- <row>
- <entry>&a.wip-status.name;</entry>
- <entry>FreeBSD Work-In-Progress Status</entry>
- </row>
-
- <row>
- <entry>&a.wireless.name;</entry>
- <entry>Discussions of 802.11 stack, tools, device driver
- development</entry>
- </row>
-
- <row>
- <entry>&a.www.name;</entry>
- <entry>Maintainers of
- <ulink
- url="&url.base;/index.html">www.FreeBSD.org</ulink></entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para><emphasis>Digest lists:</emphasis> All of the above lists
- are available in a digest format. Once subscribed to a list,
- you can change your digest options in your account options
- 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>
-
- <informaltable frame="none" pgwide="1">
- <tgroup cols="3">
- <thead>
- <row>
- <entry>List</entry>
- <entry>Source area</entry>
- <entry>Area Description (source for)</entry>
- </row>
- </thead>
-
- <tbody>
- <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>
- </row>
-
- <row>
- <entry>&a.svn-doc-head.name;</entry>
- <entry><filename>/usr/doc</filename></entry>
- <entry>All changes to the <quote>head</quote> branch of
- the doc Subversion repository</entry>
- </row>
-
- <row>
- <entry>&a.svn-doc-projects.name;</entry>
- <entry><filename>/usr/doc/projects</filename></entry>
- <entry>All changes to the <filename>projects</filename>
- area of the doc Subversion repository</entry>
- </row>
-
- <row>
- <entry>&a.svn-doc-svnadmin.name;</entry>
- <entry><filename>/usr/doc</filename></entry>
- <entry>All changes to the administrative scripts, hooks,
- and other configuration data of the doc Subversion
- repository</entry>
- </row>
-
- <row>
- <entry>&a.svn-ports-all.name;</entry>
- <entry><filename>/usr/ports</filename></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>
- </row>
-
- <row>
- <entry>&a.svn-ports-svnadmin.name;</entry>
- <entry><filename>/usr/ports</filename></entry>
- <entry>All changes to the administrative scripts, hooks,
- and other configuration data of the ports Subversion
- repository</entry>
- </row>
-
- <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>
- 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
- branch)</entry>
- </row>
-
- <row>
- <entry>&a.svn-src-projects.name;</entry>
- <entry><filename>/usr/projects</filename></entry>
- <entry>All changes to the <filename>projects</filename>
- area of the src Subversion repository</entry>
- </row>
-
- <row>
- <entry>&a.svn-src-release.name;</entry>
- <entry><filename>/usr/src</filename></entry>
- <entry>All changes to the <filename>releases</filename>
- area of the src Subversion repository</entry>
- </row>
-
- <row>
- <entry>&a.svn-src-releng.name;</entry>
- <entry><filename>/usr/src</filename></entry>
- <entry>All changes to the <filename>releng</filename>
- branches of the src Subversion repository (the
- security / release engineering branches)</entry>
- </row>
-
- <row>
- <entry>&a.svn-src-stable.name;</entry>
- <entry><filename>/usr/src</filename></entry>
- <entry>All changes to the all stable branches of the src
- Subversion repository</entry>
- </row>
-
- <row>
- <entry>&a.svn-src-stable-6.name;</entry>
- <entry><filename>/usr/src</filename></entry>
- <entry>All changes to the <filename>stable/6</filename>
- branch of the src Subversion repository</entry>
- </row>
-
- <row>
- <entry>&a.svn-src-stable-7.name;</entry>
- <entry><filename>/usr/src</filename></entry>
- <entry>All changes to the <filename>stable/7</filename>
- branch of the src Subversion repository</entry>
- </row>
-
- <row>
- <entry>&a.svn-src-stable-8.name;</entry>
- <entry><filename>/usr/src</filename></entry>
- <entry>All changes to the <filename>stable/8</filename>
- branch of the src Subversion repository</entry>
- </row>
-
- <row>
- <entry>&a.svn-src-stable-9.name;</entry>
- <entry><filename>/usr/src</filename></entry>
- <entry>All changes to the <filename>stable/9</filename>
- branch of the src Subversion repository</entry>
- </row>
-
- <row>
- <entry>&a.svn-src-stable-other.name;</entry>
- <entry><filename>/usr/src</filename></entry>
- <entry>All changes to the
- older <filename>stable</filename> branches of the src
- Subversion repository</entry>
- </row>
-
- <row>
- <entry>&a.svn-src-svnadmin.name;</entry>
- <entry><filename>/usr/src</filename></entry>
- <entry>All changes to the administrative scripts, hooks,
- and other configuration data of the src Subversion
- repository</entry>
- </row>
-
- <row>
- <entry>&a.svn-src-user.name;</entry>
- <entry><filename>/usr/src</filename></entry>
- <entry>All changes to the
- experimental <filename>user</filename> area of the src
- Subversion repository</entry>
- </row>
-
- <row>
- <entry>&a.svn-src-vendor.name;</entry>
- <entry><filename>/usr/src</filename></entry>
- <entry>All changes to the vendor work area of the src
- Subversion repository</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
- </sect2>
-
- <sect2 id="eresources-subscribe">
- <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>
-
- <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>
-
- <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@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@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;
- 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>
- </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>
- </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>
- </listitem>
- </itemizedlist>
-
- <para><emphasis>Individual list charters:</emphasis></para>
-
- <variablelist>
-
- <varlistentry>
- <term>&a.acpi.name;</term>
-
- <listitem>
- <para><emphasis>ACPI and power management
- development</emphasis></para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.afs.name;</term>
-
- <listitem>
- <para><emphasis>Andrew File System</emphasis></para>
-
- <para>This list is for discussion on porting and using
- AFS from CMU/Transarc</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.announce.name;</term>
-
- <listitem>
- <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
- moderated mailing list.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.arch.name;</term>
-
- <listitem>
- <para><emphasis>Architecture and design
- discussions</emphasis></para>
-
- <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>
-
- <itemizedlist>
- <listitem>
- <para>How to re-vamp the build system to have several
- customized builds running at the same time.</para>
- </listitem>
-
- <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>
- </listitem>
-
- <listitem>
- <para>How to write a network driver.</para>
- </listitem>
- </itemizedlist>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.bluetooth.name;</term>
-
- <listitem>
- <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>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.bugbusters.name;</term>
-
- <listitem>
- <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>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.bugs.name;</term>
-
- <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
- url="&url.base;/send-pr.html">WEB
- interface</ulink> to it.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.chat.name;</term>
-
- <listitem>
- <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>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.chromium.name;</term>
-
- <listitem>
- <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>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.core.name;</term>
-
- <listitem>
- <para><emphasis>FreeBSD core team</emphasis></para>
-
- <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>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.current.name;</term>
-
- <listitem>
- <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>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.cvsweb.name;</term>
-
- <listitem>
- <para><emphasis>FreeBSD CVSweb Project</emphasis></para>
-
- <para>Technical discussions about use, development and
- maintenance of FreeBSD-CVSweb.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.desktop.name;</term>
-
- <listitem>
- <para><emphasis>Using and improving &os; on the
- desktop</emphasis></para>
-
- <para>This is a forum for discussion of &os; on the
+ <row>
+ <entry>&a.desktop.name;</entry>
+ <entry>This is a forum for discussion of &os; on the
desktop. It is primarily a place for desktop porters
and users to discuss issues and improve &os;'s desktop
- support.</para>
- </listitem>
- </varlistentry>
+ support.</entry>
+ </row>
- <varlistentry>
- <term>&a.doc.name;</term>
-
- <listitem>
- <para><emphasis>Documentation project</emphasis></para>
-
- <para>This mailing list is for the discussion of issues
+ <row>
+ <entry>&a.doc.name;</entry>
+ <entry>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
+ for &os;. The members of this mailing list are
+ collectively referred to as <quote>The &os;
Documentation Project</quote>. It is an open list;
- feel free to join and contribute!</para>
- </listitem>
- </varlistentry>
+ feel free to join and contribute!</entry>
+ </row>
- <varlistentry>
- <term>&a.drivers.name;</term>
-
- <listitem>
- <para><emphasis>Writing device drivers for
- &os;</emphasis></para>
-
- <para>This is a forum for technical discussions related
+ <row>
+ <entry>&a.drivers.name;</entry>
+ <entry>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>
+ kernel.</entry>
+ </row>
- <varlistentry>
- <term>&a.eclipse.name;</term>
-
- <listitem>
- <para><emphasis>&os; users of Eclipse IDE, tools, rich
- client applications and ports.</emphasis></para>
-
- <para>The intention of this list is to provide mutual
- support for everything to do with choosing, installing,
- using, developing and maintaining the Eclipse IDE,
- tools, rich client applications on the &os; platform and
- assisting with the porting of Eclipse IDE and plugins to
- the &os; environment.</para>
-
- <para>The intention is also to facilitate exchange of
- information between the Eclipse community and the &os;
- community to the mutual benefit of both.</para>
-
- <para>Although this list is focused primarily on the needs
- of Eclipse users it will also provide a forum for those
+ <row>
+ <entry>&a.eclipse.name;</entry>
+ <entry>&os; users of Eclipse IDE, tools, rich client
+ applications and ports. The intention of this list
+ is to provide mutual support for everything to do
+ with choosing, installing, using, developing and
+ maintaining the Eclipse IDE on the &os; platform and
+ assisting with the porting of Eclipse IDE and plugins
+ to &os;. The intention is also to facilitate exchange
+ of information between the Eclipse community and the
+ &os; community. It provides a forum for those
who would like to develop &os; specific applications
- using the Eclipse framework.</para>
- </listitem>
- </varlistentry>
+ using the Eclipse framework.</entry>
+ </row>
- <varlistentry>
- <term>&a.embedded.name;</term>
+ <row>
+ <entry>&a.embedded.name;</entry>
+ <entry>This list discusses technical topics related to
+ using &os; in embedded systems. For the purpose of
+ this list, embedded systems are defined as 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, phone handsets, network equipment such as routers,
+ switches and PBXs, remote measuring equipment, PDAs,
+ and Point Of Sale systems.</entry>
+ </row>
- <listitem>
- <para><emphasis>Using FreeBSD in embedded
- applications</emphasis></para>
+ <row>
+ <entry>&a.eol.name;</entry>
+ <entry>This list is for those interested in providing
+ or making use of peer support of &os;-related
+ software for which the &os; project no longer
+ provides official support in the form of security
+ advisories and patches.</entry>
+ </row>
- <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>
+ <row>
+ <entry>&a.emulation.name;</entry>
+ <entry>Technical list for discussion of emulation of
+ other systems such as &linux; and &windows; and for
+ running programs written for other operating systems
+ on &os;.</entry>
+ </row>
- <varlistentry>
- <term>&a.emulation.name;</term>
+ <row>
+ <entry>&a.firewire.name;</entry>
+ <entry>Mailing list for the technical discussion of
+ the design and implementation of the &firewire;
+ (iLink, IEEE 1394) subsystem on &os;. Relevant
+ topics include the standards, bus devices and
+ their protocols, adapter boards/cards/chips sets,
+ and the architecture and implementation of code for
+ their proper support.</entry>
+ </row>
- <listitem>
- <para><emphasis>Emulation of other systems such as
- Linux/&ms-dos;/&windows;</emphasis></para>
+ <row>
+ <entry>&a.fs.name;</entry>
+ <entry>Technical discussions concerning &os; file
+ systems.</entry>
+ </row>
- <para>This is a forum for technical discussions related
- to running programs written for other operating systems
- on &os;.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.gecko.name;</entry>
+ <entry>This is a forum about
+ <application>Gecko</application> Ports applications,
+ their installation, development and support
+ within &os;.</entry>
+ </row>
- <varlistentry>
- <term>&a.eol.name;</term>
+ <row>
+ <entry>&a.geom.name;</entry>
+ <entry>Technical discussions specific to GEOM and
+ related implementations.</entry>
+ </row>
- <listitem>
- <para><emphasis>Peer support of FreeBSD-related software
- that is no longer supported by the FreeBSD
- project.</emphasis></para>
+ <row>
+ <entry>&a.gnome.name;</entry>
+ <entry>Technical discussions regarding the porting of
+ <application>GNOME</application> and
+ <application>GNOME</application> applications
+ to &os;</entry>
+ </row>
- <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>
+ <row>
+ <entry>&a.hackers.name;</entry>
+ <entry>This is the primary technical mailing list for
+ technical discussions related to &os;. It is for
+ individuals actively working on &os;, to bring up
+ problems or discuss alternative solutions.
+ Individuals interested in following the technical
+ discussion are also welcome.</entry>
+ </row>
- <varlistentry>
- <term>&a.firewire.name;</term>
+ <row>
+ <entry>&a.hardware.name;</entry>
+ <entry>General discussion about the types of hardware
+ that &os; runs on, including various problems and
+ suggestions concerning what to buy or avoid.</entry>
+ </row>
- <listitem>
- <para><emphasis>&firewire; (iLink, IEEE
- 1394)</emphasis></para>
+ <row>
+ <entry>&a.i18n.name;</entry>
+ <entry>List for technical discussions related to &os;
+ internationalization.</entry>
+ </row>
- <para>This is a mailing list for discussion of the design
- and implementation of a &firewire; (aka IEEE 1394 aka
- iLink) subsystem for FreeBSD. Relevant topics
- specifically include the standards, bus devices and
- their protocols, adapter boards/cards/chips sets, and
- the architecture and implementation of code for their
- proper support.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.i386.name;</entry>
+ <entry>Technical list for discussion of i386-specific
+ issues. Individuals interested in following the
+ technical discussion are also welcome.</entry>
+ </row>
- <varlistentry>
- <term>&a.fs.name;</term>
+ <row>
+ <entry>&a.ia32.name;</entry>
+ <entry>Technical list for individuals actively working
+ on IA-32 (&intel; x86) platform issues for &os;, to
+ bring up problems or discuss alternative solutions.
+ Individuals interested in following the technical
+ discussion are also welcome.</entry>
+ </row>
- <listitem>
- <para><emphasis>File systems</emphasis></para>
+ <row>
+ <entry>&a.ia64.name;</entry>
+ <entry>This is a technical mailing list for individuals
+ actively working on porting &os; to the IA-64
+ platform from &intel; and to bring up problems or
+ discuss alternative solutions. Individuals interested
+ in following the technical discussion are also
+ welcome.</entry>
+ </row>
- <para>Discussions concerning FreeBSD file systems.
- This is a technical mailing list for which strictly
- technical content is expected.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.infiniband.name;</entry>
+ <entry>Technical mailing list discussing Infiniband,
+ OFED, and OpenSM on &os;.D</entry>
+ </row>
- <varlistentry>
- <term>&a.gecko.name;</term>
+ <row>
+ <entry>&a.ipfw.name;</entry>
+ <entry>Technical discussion concerning the design of
+ the IPFW firewall code in &os;</entry>
+ </row>
- <listitem>
- <para><emphasis>Gecko Rendering Engine</emphasis></para>
+ <row>
+ <entry>&a.isdn.name;</entry>
+ <entry>This is the mailing list for people discussing
+ the development of ISDN support for &os;</entry>
+ </row>
- <para>This is a forum about
- <application>Gecko</application> applications using
- &os;.</para>
+ <row>
+ <entry>&a.jail.name;</entry>
+ <entry>List for technical discussion about the
+ &man.jail.8; facility</entry>
+ </row>
- <para>Discussion centers around Gecko Ports applications,
- their installation, their development and their support
- within &os;.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.java.name;</entry>
+ <entry>This is the mailing list for people discussing
+ the development of significant &java; applications
+ for &os; and the porting and maintenance of
+ &jdk;s.</entry>
+ </row>
- <varlistentry>
- <term>&a.geom.name;</term>
+ <row>
+ <entry>&a.kde.name;</entry>
+ <entry>Technical discussions concerning porting
+ <application>KDE</application> and
+ <application>KDE</application> applications on
+ &os;.</entry>
+ </row>
- <listitem>
- <para><emphasis>GEOM</emphasis></para>
+ <row>
+ <entry>&a.lfs.name;</entry>
+ <entry>Discussion list for porting LFS to &os;.</entry>
+ </row>
- <para>Discussions specific to GEOM and related
- implementations. This is a technical mailing list for
- which strictly technical content is expected.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.mips.name;</entry>
+ <entry>Technical list for individuals actively working
+ on porting &os; to &mips;, to bring up problems or
+ discuss alternative solutions. Individuals interested
+ in following the technical discussion are also
+ welcome.</entry>
+ </row>
- <varlistentry>
- <term>&a.gnome.name;</term>
+ <row>
+ <entry>&a.mobile.name;</entry>
+ <entry>Discussions related to running &os; on
+ notebooks, laptops, and other mobile equipment.
+ Typical issues include APM, PC-CARD, wireless
+ communication, and related topics.</entry>
+ </row>
- <listitem>
- <para><emphasis>GNOME</emphasis></para>
+ <row>
+ <entry>&a.mono.name;</entry>
+ <entry>Technical mailing list for discussions related
+ to the Mono development framework on &os;. It is
+ for individuals actively working on porting Mono or
+ C# applications to &os;, to bring up problems or
+ discuss alternative solutions. Individuals interested
+ in following the technicaldiscussion are also
+ welcome.</entry>
+ </row>
- <para>Discussions concerning The
- <application>GNOME</application> Desktop Environment
- for FreeBSD systems. This is a technical mailing list
- for which strictly technical content is expected.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.mozilla.name;</entry>
+ <entry>Discussion for porting Mozilla applications
+ such as <application>firefox</application> to
+ &os;</entry>
+ </row>
- <varlistentry>
- <term>&a.infiniband.name;</term>
+ <row>
+ <entry>&a.multimedia.name;</entry>
+ <entry>Discussion on this list centers around multimedia
+ applications, their installation, their development
+ and their support within &os;.</entry>
+ </row>
- <listitem>
- <para><emphasis>Infiniband on &os;</emphasis></para>
+ <row>
+ <entry>&a.net.name;</entry>
+ <entry>Technical discussions of networking in general
+ and TCP/IP source code in particular.</entry>
+ </row>
- <para>Technical mailing list discussing Infiniband, OFED,
- and OpenSM on &os;.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.newbus.name;</entry>
+ <entry>The primary technical mailing list for the New
+ Bus architecture.</entry>
+ </row>
- <varlistentry>
- <term>&a.ipfw.name;</term>
+ <row>
+ <entry>&a.numerics.name;</entry>
+ <entry>List for in-depth technical discussions
+ relating to implementing missing libm functions, or
+ improving the precision of already implemented
+ functions. The list's purpose is to capture the
+ design decisions of the implementation and serve as an
+ archive for later code spelunkers to draw upon for
+ understanding.</entry>
+ </row>
- <listitem>
- <para><emphasis>IP Firewall</emphasis></para>
+ <row>
+ <entry>&a.office.name;</entry>
+ <entry>Discussion centers around office applications,
+ their installation, their development and their
+ support within &os;.</entry>
+ </row>
- <para>This is the forum for technical discussions
- concerning the redesign of the IP firewall code in
- FreeBSD. This is a technical mailing list for which
- strictly technical content is expected.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.performance.name;</entry>
+ <entry>This mailing list exists to provide a place for
+ hackers, administrators, and/or concerned parties to
+ discuss performance related topics pertaining to &os;.
+ Acceptable topics include &os; installations that are
+ under high load, are experiencing performance
+ problems, or are pushing the limits of &os;.
+ Concerned parties that are willing to work toward
+ improving the performance of &os; are highly
+ encouraged to subscribe to this list. This list is
+ a place to make contributions or inquire about
+ undocumented performance related topics.</entry>
+ </row>
- <varlistentry>
- <term>&a.ia64.name;</term>
+ <row>
+ <entry>&a.perl.name;</entry>
+ <entry>Technical list for those working on Perl ports.
+ Others who wish to contribute toward the maintenance
+ of these ports are welcome to participate.</entry>
+ </row>
- <listitem>
- <para><emphasis>Porting FreeBSD to IA64</emphasis></para>
+ <row>
+ <entry>&a.pf.name;</entry>
+ <entry>Discussion concerning the packet filter (pf)
+ firewall system on &os;. Technical discussion and
+ user questions are welcome. This list is also a place
+ to discuss the ALTQ QoS framework.</entry>
+ </row>
- <para>This is a technical mailing list for individuals
- actively working on porting FreeBSD to the IA-64
- platform from &intel;, to bring up problems or discuss
- alternative solutions. Individuals interested in
- following the technical discussion are also
- welcome.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.pkg.name;</entry>
+ <entry>Discussion of all aspects of managing &os;
+ systems by using binary packages to install software,
+ including binary package toolkits and formats, their
+ development and support within &os;, package
+ repository management, and 3rd party packages.
+ Discussion of ports which fail to generate packages
+ correctly are inappropriate for this list.</entry>
+ </row>
- <varlistentry>
- <term>&a.isdn.name;</term>
+ <row>
+ <entry>&a.platforms.name;</entry>
+ <entry>Technical discussion of ports to non &intel;
+ architecture platforms. Topics include cross-platform
+ &os; issues, general discussion, and proposals for
+ non-&intel; &os; ports.</entry>
+ </row>
- <listitem>
- <para><emphasis>ISDN Communications</emphasis></para>
+ <row>
+ <entry>&a.ports.name;</entry>
+ <entry>Technical discussion concerning the &os; Ports
+ Collection, ports infrastructure, and general ports
+ coordination efforts.</entry>
+ </row>
- <para>This is the mailing list for people discussing the
- development of ISDN support for FreeBSD.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.ports-announce.name;</entry>
+ <entry>Important news and instructions for developers,
+ porters, and users of the &os; Ports Collection,
+ including architecture/infrastructure changes, new
+ capabilities, critical upgrade instructions, and
+ release engineering information. This is a low-volume
+ mailing list, intended for announcements.</entry>
+ </row>
- <varlistentry>
- <term>&a.java.name;</term>
+ <row>
+ <entry>&a.ports-bugs.name;</entry>
+ <entry>Technical discussion concerning problem reports
+ for the &os; Ports Collection, proposed ports, or
+ modifications to ports.</entry>
+ </row>
- <listitem>
- <para><emphasis>&java; Development</emphasis></para>
+ <row>
+ <entry>&a.ppc.name;</entry>
+ <entry>Technical list for individuals actively working
+ on porting &os; to the &powerpc;, to bring up problems
+ or discuss alternative solutions. Individuals
+ interested in following the technical discussion are
+ also welcome.</entry>
+ </row>
- <para>This is the mailing list for people discussing the
- development of significant &java; applications for
- FreeBSD and the porting and maintenance of
- &jdk;s.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.proliant.name;</entry>
+ <entry>Technical discussion of &os; on HP ProLiant
+ server platforms, including the discussion of
+ ProLiant-specific drivers, management software,
+ configuration tools, and BIOS updates. This is
+ also the primary place to discuss the hpasmd,
+ hpasmcli, and hpacucli modules.</entry>
+ </row>
- <varlistentry id="eresources-charters-jobs">
- <term>&a.jobs.name;</term>
+ <row>
+ <entry>&a.python.name;</entry>
+ <entry>Technical discussions related to improving
+ Python-support on &os;. It is for individuals working
+ on porting Python and its 3rd party modules to &os;.
+ Individuals interested in following the technical
+ discussion are also welcome.</entry>
+ </row>
- <listitem>
- <para><emphasis>Jobs offered and sought</emphasis></para>
+ <row>
+ <entry>&a.rc.name;</entry>
+ <entry>Discussion related to the
+ <filename>rc.d</filename> system and its
+ development, including current implementations,
+ improvements to existing systems, and design of new
+ elements.</entry>
+ </row>
- <para>This is a forum for posting employment notices
- and resumes specifically related to &os;, e.g., if you
- are seeking &os;-related employment or have a job
- involving &os; to advertise then this is the right
- place. This is <emphasis>not</emphasis> a mailing list
- for general employment issues since adequate forums
- for that already exist elsewhere.</para>
+ <row>
+ <entry>&a.realtime.name;</entry>
+ <entry>This is the mailing list for people working on
+ development of realtime extensions to &os;</entry>
+ </row>
- <para>Note that this list, like other <hostid
- role="domainname">FreeBSD.org</hostid> mailing lists,
- is distributed worldwide. Thus, you need to be clear
- about location and the extent to which telecommuting or
- assistance with relocation is available.</para>
+ <row>
+ <entry>&a.ruby.name;</entry>
+ <entry>Technical discussions related to Ruby support
+ on &os;. This list is for individuals working on
+ Ruby ports, 3rd party libraries, and frameworks.
+ Individuals interested in the technical discussion
+ are also welcome.</entry>
+ </row>
- <para>Email should use open formats only —
- preferably plain text, but basic Portable Document
- Format (<acronym>PDF</acronym>), HTML, and a few others
- are acceptable to many readers. Closed formats such as
- µsoft; Word (<filename>.doc</filename>) will be
- rejected by the mailing list server.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.scsi.name;</entry>
+ <entry>Technical mailing list for people working on
+ the SCSI subsystem for &os;</entry>
+ </row>
- <varlistentry>
- <term>&a.kde.name;</term>
+ <row>
+ <entry>&a.security.name;</entry>
+ <entry>Technical list for the discussion of security
+ issues affecting &os;.</entry>
+ </row>
- <listitem>
- <para><emphasis>KDE</emphasis></para>
+ <row>
+ <entry>&a.snapshots.name;</entry>
+ <entry>This list will notify you about the availability
+ of new &os; development snapshots for the head/ and
+ stable/ branches.</entry>
+ </row>
- <para>Discussions concerning
- <application>KDE</application> on FreeBSD systems.
- This is a technical mailing list for which strictly
- technical content is expected.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.sparc.name;</entry>
+ <entry>This is the technical mailing list for
+ individuals actively working on porting &os; to
+ &sparc; based systems, to bring up problems or discuss
+ alternative solutions. Individuals interested in
+ following the technical discussion are also
+ welcome.</entry>
+ </row>
- <varlistentry>
- <term>&a.hackers.name;</term>
+ <row>
+ <entry>&a.standards.name;</entry>
+ <entry>Technical discussions related to &os; conformance
+ to the C99 and the POSIX standards.</entry>
+ </row>
- <listitem>
- <para><emphasis>Technical discussions</emphasis></para>
+ <row>
+ <entry>&a.sun4v.name;</entry>
+ <entry>This is a technical mailing list for individuals
+ actively working on porting &os; to the sun4v
+ platform, to bring up problems or discuss alternative
+ solutions. Individuals interested in following the
+ technical discussion are also welcome.</entry>
+ </row>
- <para>This is a forum for technical discussions related
- to FreeBSD. This is the primary technical mailing list.
- It is for individuals actively working on FreeBSD, to
- bring up problems or discuss alternative solutions.
- Individuals interested in following the technical
- discussion are also welcome. This is a technical
- mailing list for which strictly technical content is
- expected.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.sysinstall.name;</entry>
+ <entry>This is a technical mailing list for individuals
+ actively working on &man.sysinstall.8;
+ development.</entry>
+ </row>
- <varlistentry>
- <term>&a.hardware.name;</term>
+ <row>
+ <entry>&a.tcltk.name;</entry>
+ <entry>Mailing list for those working on &os; Tcl/Tk
+ ports. Others who wish to contribute toward the maintenance
+ of these ports are also welcome to participate.</entry>
+ </row>
- <listitem>
- <para><emphasis>General discussion of FreeBSD
- hardware</emphasis></para>
+ <row>
+ <entry>&a.threads.name;</entry>
+ <entry>List for discussing the design and implementation
+ of threading on &os;. Topics include libc_r,
+ KSE/libkse, libthr based threads, as well as threading
+ issues within system libraries and other areas of
+ the system.</entry>
+ </row>
- <para>General discussion about the types of hardware
- that FreeBSD runs on, various problems and suggestions
- concerning what to buy or avoid.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.tilera.name;</entry>
+ <entry>Technical list for porting &os; to the Tilera
+ family of CPUs.</entry>
+ </row>
- <varlistentry>
- <term>&a.hubs.name;</term>
+ <row>
+ <entry>&a.toolchain.name;</entry>
+ <entry>Technical mailing list for discussions related
+ to the maintenance of the toolchain shipped with &os;.
+ Topics include the state of Clang and GCC, assemblers,
+ linkers and debuggers.</entry>
+ </row>
- <listitem>
- <para><emphasis>Mirror sites</emphasis></para>
+ <row>
+ <entry>&a.usb.name;</entry>
+ <entry>Technical discussions related to &os; support
+ for USB.</entry>
+ </row>
- <para>Announcements and discussion for people who run
- FreeBSD mirror sites.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.virtualization.name;</entry>
+ <entry>Discussion of various virtualization techniques
+ supported by &os;. Topics include the implementation
+ of basic functionality, adding new features, asking
+ for help, and the discussion of use cases.</entry>
+ </row>
- <varlistentry>
- <term>&a.isp.name;</term>
+ <row>
+ <entry>&a.vuxml.name;</entry>
+ <entry>Technical discussion on the VuXML
+ infrastructure.</entry>
+ </row>
- <listitem>
- <para><emphasis>Issues for Internet Service
- Providers</emphasis></para>
+ <row>
+ <entry>&a.wireless.name;</entry>
+ <entry>Discussions of &os; 802.11 stack, tools, and
+ device driver development. Topics includes bugs, new
+ features, and maintenance.</entry>
+ </row>
- <para>This mailing list is for discussing topics relevant
- to Internet Service Providers (ISPs) using FreeBSD.
- This is a technical mailing list for which strictly
- technical content is expected.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.x11.name;</entry>
+ <entry>List for discussions related to
+ maintaining the &os; <application>Xorg</application>
+ Individuals interested in following the technical
+ discussion are also welcome.</entry>
+ </row>
- <varlistentry>
- <term>&a.mono.name;</term>
+ <row>
+ <entry>&a.xen.name;</entry>
+ <entry>A list that focuses on the &os; &xen; port.
+ It is intended as a forum for technical discussions
+ of the implementation and design as well as
+ administrative deployment issues.</entry>
+ </row>
- <listitem>
- <para><emphasis>Mono and C# applications on
- FreeBSD</emphasis></para>
+ <row>
+ <entry>&a.xfce.name;</entry>
+ <entry>Technical mailing list for individuals
+ actively working on porting
+ <application>XFCE</application> to &os;, to bring
+ up problems or discuss alternative solutions.
+ Individuals interested in following the technical
+ discussion are also welcome.</entry>
+ </row>
- <para>This is a list for discussions related to the Mono
- development framework on &os;. This is a technical
- mailing list. It is for individuals actively working
- on porting Mono or C# applications to &os;, to bring
- up problems or discuss alternative solutions.
- Individuals interested in following the technical
- discussion are also welcome.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.zope.name;</entry>
+ <entry>Technical mailing list for
+ <application>Zope</application> for individuals
+ actively working on porting
+ <application>Zope</application> to &os;, to bring
+ up problems or discuss alternative solutions.
+ Individuals interested in following the technical
+ discussion are also welcome.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
- <varlistentry>
- <term>&a.office.name;</term>
+ <para><emphasis>Limited lists:</emphasis> The following lists
+ are for more specialized audiences and are probably not of
+ interest to the general public. It is recommended that you
+ establish a presence in the technical lists before joining
+ one of these limited lists so that you will understand the
+ communications etiquette involved.</para>
- <listitem>
- <para><emphasis>Office applications on
- &os;</emphasis></para>
+ <informaltable frame="none" pgwide="1">
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>List</entry>
+ <entry>Purpose</entry>
+ </row>
+ </thead>
- <para>Discussion centers around office applications,
- their installation, their development and their support
- within &os;.</para>
- </listitem>
- </varlistentry>
+ <tbody>
+ <row>
+ <entry>&a.hubs.name;</entry>
+ <entry>Announcements and infrastructural support
+ discussion for people who run &os; mirror
+ sites.</entry>
+ </row>
- <varlistentry>
- <term>&a.performance.name;</term>
+ <row>
+ <entry>&a.usergroups.name;</entry>
+ <entry>Discussion list for coordinators of local area
+ Users Groups and a designated individual from the
+ Core Team. Topics should be limited to meeting
+ synopsis and coordination of projects that span User
+ Groups.</entry>
+ </row>
- <listitem>
- <para><emphasis>Discussions about tuning or speedingup
- FreeBSD</emphasis></para>
+ <row>
+ <entry>&a.wip-status.name;</entry>
+ <entry>Moderated mailing list for developers to announce
+ their &os; Work In Progress (WIP) projects. Messages
+ are moderated. It is suggested to send the message
+ to a more topical &os; list and only "BCC:" this list.
+ This way your WIP can also be discussed on the topical
+ list, as no discussion is allowed on this list. An
+ editorial digest of the messages to this list might
+ be posted to the &os; website every few months as
+ part of the &os; Status Reports.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
- <para>This mailing list exists to provide a place for
- hackers, administrators, and/or concerned parties to
- discuss performance related topics pertaining to
- FreeBSD. Acceptable topics includes talking about
- FreeBSD installations that are either under high load,
- are experiencing performance problems, or are pushing
- the limits of FreeBSD. Concerned parties that are
- willing to work toward improving the performance of
- FreeBSD are highly encouraged to subscribe to this list.
- This is a highly technical list ideally suited for
- experienced FreeBSD users, hackers, or administrators
- interested in keeping FreeBSD fast, robust, and
- scalable. This list is not a question-and-answer list
- that replaces reading through documentation, but it is a
- place to make contributions or inquire about unanswered
- performance related topics.</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>
- </listitem>
- </varlistentry>
+ <informaltable frame="none" pgwide="1">
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>List</entry>
+ <entry>Source area</entry>
+ <entry>Area Description (source for)</entry>
+ </row>
+ </thead>
- <varlistentry>
- <term>&a.pf.name;</term>
+ <tbody>
+ <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>
+ </row>
- <listitem>
- <para><emphasis>Discussion and questions about the packet
- filter firewall system</emphasis></para>
+ <row>
+ <entry>&a.svn-doc-head.name;</entry>
+ <entry><filename>/usr/doc</filename></entry>
+ <entry>All changes to the <quote>head</quote> branch of
+ the doc Subversion repository</entry>
+ </row>
- <para>Discussion concerning the packet filter (pf)
- firewall system in terms of FreeBSD. Technical
- discussion and user questions are both welcome. This
- list is also a place to discuss the ALTQ QoS
- framework.</para>
+ <row>
+ <entry>&a.svn-doc-projects.name;</entry>
+ <entry><filename>/usr/doc/projects</filename></entry>
+ <entry>All changes to the <filename>projects</filename>
+ area of the doc Subversion repository</entry>
+ </row>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.svn-doc-svnadmin.name;</entry>
+ <entry><filename>/usr/doc</filename></entry>
+ <entry>All changes to the administrative scripts, hooks,
+ and other configuration data of the doc Subversion
+ repository</entry>
+ </row>
- <varlistentry>
- <term>&a.pkg.name;</term>
+ <row>
+ <entry>&a.svn-ports-all.name;</entry>
+ <entry><filename>/usr/ports</filename></entry>
+ <entry>All changes to the ports Subversion
+ repository</entry>
+ </row>
- <listitem>
- <para><emphasis>Binary package management and package
- tools discussion</emphasis></para>
+ <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>
+ </row>
- <para>Discussion of all aspects of managing &os; systems
- by using binary packages to install software, including
- binary package toolkits and formats, their development
- and support within &os;, package repository management,
- and 3rd party packages.</para>
+ <row>
+ <entry>&a.svn-ports-svnadmin.name;</entry>
+ <entry><filename>/usr/ports</filename></entry>
+ <entry>All changes to the administrative scripts, hooks,
+ and other configuration data of the ports Subversion
+ repository</entry>
+ </row>
- <para>Note that discussion of ports which fail to generate
- packages correctly should generally be considered as
- ports problems, and so inappropriate for this
- list.</para>
- </listitem>
- </varlistentry>
+ <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>
+ and <filename>projects</filename>)</entry>
+ </row>
- <varlistentry>
- <term>&a.platforms.name;</term>
+ <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
+ branch)</entry>
+ </row>
- <listitem>
- <para><emphasis>Porting to Non &intel;
- platforms</emphasis></para>
+ <row>
+ <entry>&a.svn-src-projects.name;</entry>
+ <entry><filename>/usr/projects</filename></entry>
+ <entry>All changes to the <filename>projects</filename>
+ area of the src Subversion repository</entry>
+ </row>
- <para>Cross-platform FreeBSD issues, general discussion
- and proposals for non &intel; FreeBSD ports. This is
- a technical mailing list for which strictly technical
- content is expected.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.svn-src-release.name;</entry>
+ <entry><filename>/usr/src</filename></entry>
+ <entry>All changes to the <filename>releases</filename>
+ area of the src Subversion repository</entry>
+ </row>
- <varlistentry>
- <term>&a.ports.name;</term>
+ <row>
+ <entry>&a.svn-src-releng.name;</entry>
+ <entry><filename>/usr/src</filename></entry>
+ <entry>All changes to the <filename>releng</filename>
+ branches of the src Subversion repository (the
+ security / release engineering branches)</entry>
+ </row>
- <listitem>
- <para><emphasis>Discussion of
- <quote>ports</quote></emphasis></para>
+ <row>
+ <entry>&a.svn-src-stable.name;</entry>
+ <entry><filename>/usr/src</filename></entry>
+ <entry>All changes to the all stable branches of the src
+ Subversion repository</entry>
+ </row>
- <para>Discussions concerning FreeBSD's <quote>ports
- collection</quote> (<filename>/usr/ports</filename>),
- ports infrastructure, and general ports coordination
- efforts. This is a technical mailing list for which
- strictly technical content is expected.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.svn-src-stable-6.name;</entry>
+ <entry><filename>/usr/src</filename></entry>
+ <entry>All changes to the <filename>stable/6</filename>
+ branch of the src Subversion repository</entry>
+ </row>
- <varlistentry>
- <term>&a.ports-announce.name;</term>
+ <row>
+ <entry>&a.svn-src-stable-7.name;</entry>
+ <entry><filename>/usr/src</filename></entry>
+ <entry>All changes to the <filename>stable/7</filename>
+ branch of the src Subversion repository</entry>
+ </row>
- <listitem>
- <para><emphasis>Important news and instructions about the
- &os; <quote>Ports
- Collection</quote></emphasis></para>
+ <row>
+ <entry>&a.svn-src-stable-8.name;</entry>
+ <entry><filename>/usr/src</filename></entry>
+ <entry>All changes to the <filename>stable/8</filename>
+ branch of the src Subversion repository</entry>
+ </row>
- <para>Important news for developers, porters, and users
- of the <quote>Ports Collection</quote> (<filename
- role="directory">/usr/ports</filename>), including
- architecture/infrastructure changes, new capabilities,
- critical upgrade instructions, and release engineering
- information. This is a low-volume mailing list,
- intended for announcements.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.svn-src-stable-9.name;</entry>
+ <entry><filename>/usr/src</filename></entry>
+ <entry>All changes to the <filename>stable/9</filename>
+ branch of the src Subversion repository</entry>
+ </row>
- <varlistentry>
- <term>&a.ports-bugs.name;</term>
+ <row>
+ <entry>&a.svn-src-stable-other.name;</entry>
+ <entry><filename>/usr/src</filename></entry>
+ <entry>All changes to the
+ older <filename>stable</filename> branches of the src
+ Subversion repository</entry>
+ </row>
- <listitem>
- <para><emphasis>Discussion of
- <quote>ports</quote> bugs</emphasis></para>
+ <row>
+ <entry>&a.svn-src-svnadmin.name;</entry>
+ <entry><filename>/usr/src</filename></entry>
+ <entry>All changes to the administrative scripts, hooks,
+ and other configuration data of the src Subversion
+ repository</entry>
+ </row>
- <para>Discussions concerning problem reports for FreeBSD's
- <quote>ports collection</quote>
- (<filename>/usr/ports</filename>), proposed ports, or
- modifications to ports. This is a technical mailing
- list for which strictly technical content is
- expected.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry>&a.svn-src-user.name;</entry>
+ <entry><filename>/usr/src</filename></entry>
+ <entry>All changes to the
+ experimental <filename>user</filename> area of the src
+ Subversion repository</entry>
+ </row>
- <varlistentry>
- <term>&a.proliant.name;</term>
+ <row>
+ <entry>&a.svn-src-vendor.name;</entry>
+ <entry><filename>/usr/src</filename></entry>
+ <entry>All changes to the vendor work area of the src
+ Subversion repository</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+</sect2>
- <listitem>
- <para><emphasis>Technical discussion of FreeBSD on HP
- ProLiant server platforms</emphasis></para>
+<sect2 id="eresources-subscribe">
+ <title>How to Subscribe</title>
- <para>This mailing list is to be used for the technical
- discussion of the usage of FreeBSD on HP ProLiant
- servers, including the discussion of ProLiant-specific
- drivers, management software, configuration tools, and
- BIOS updates. As such, this is the primary place to
- discuss the hpasmd, hpasmcli, and hpacucli
- modules.</para>
- </listitem>
- </varlistentry>
+ <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>
- <varlistentry>
- <term>&a.python.name;</term>
+ <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>
- <listitem>
- <para><emphasis>Python on FreeBSD</emphasis></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@FreeBSD.org</email>
+ to unsubscribe yourself.</para>
- <para>This is a list for discussions related to improving
- Python-support on FreeBSD. This is a technical mailing
- list. It is for individuals working on porting Python,
- its 3rd party modules and
- <application>Zope</application> stuff to FreeBSD.
- Individuals interested in following the technical
- discussion are also welcome.</para>
- </listitem>
- </varlistentry>
+ <para>Keep discussion in the technical mailing lists on a technical
+ track. If you are only interested in important announcements,
+ join the &a.announce;, which is intended for infrequent
+ traffic.</para>
+</sect2>
- <varlistentry>
- <term>&a.questions.name;</term>
+<sect2 id="eresources-charters">
+ <title>List Charters</title>
- <listitem>
- <para><emphasis>User questions</emphasis></para>
+ <para><emphasis>All</emphasis> &os; 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 &os; Postmaster
+ <email>postmaster@FreeBSD.org</email>, after which, on a
+ third offense, the poster will be removed from all &os;
+ mailing lists and filtered from further posting to them. We
+ regret that such rules and measures are necessary, but today's
+ Internet is a pretty harsh environment, and many fail to
+ appreciate just how fragile some of its mechanisms are.</para>
- <para>This is the mailing list for questions about
- FreeBSD. You should not send <quote>how to</quote>
- questions to the technical lists unless you consider
- the question to be pretty technical.</para>
- </listitem>
- </varlistentry>
+ <para>Rules of the road:</para>
- <varlistentry>
- <term>&a.ruby.name;</term>
+ <itemizedlist>
+ <listitem>
+ <para>The topic of any posting should adhere to the basic
+ charter of the list it is posted to. If the list
+ is about technical issues, your posting should contain
+ technical discussion. Irrelevant chatter detracts from
+ the value of the mailing list 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><emphasis>FreeBSD-specific Ruby
- discussions</emphasis></para>
+ <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.
+ If a message is sent to you in such a way that
+ multiple mailing lists appear on the <literal>Cc</literal>
+ line, the <literal>Cc</literal> line should be
+ trimmed before replying. <emphasis>You are responsible
+ for your own cross-postings, no matter who the originator
+ might have been.</emphasis></para>
+ </listitem>
- <para>This is a list for discussions related to the Ruby
- support on FreeBSD. This is a technical mailing
- list. It is for individuals working on Ruby ports,
- 3rd party libraries and frameworks.</para>
+ <listitem>
+ <para>Personal attacks and profanity are not allowed. Gross
+ breaches of netiquette, like excerpting or reposting
+ private mail when permission to do so was not obtained, are
+ frowned upon and may result in a warning or ban.</para>
+ </listitem>
- <para>Individuals interested in the technical discussion
- are also welcome.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.scsi.name;</term>
-
- <listitem>
- <para><emphasis>SCSI subsystem</emphasis></para>
-
- <para>This is the mailing list for people working on
- the SCSI subsystem for FreeBSD. This is a technical
- mailing list for which strictly technical content is
- expected.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.security.name;</term>
-
- <listitem>
- <para><emphasis>Security issues</emphasis></para>
-
- <para>FreeBSD computer security issues (DES, Kerberos,
- known security holes and fixes, etc). This is a
- technical mailing list for which strictly technical
- discussion is expected. Note that this is not a
- question-and-answer list, but that contributions (BOTH
- question AND answer) to the FAQ are welcome.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.security-notifications.name;</term>
-
- <listitem>
- <para><emphasis>Security Notifications</emphasis></para>
-
- <para>Notifications of FreeBSD security problems and
- fixes. This is not a discussion list. The discussion
- list is FreeBSD-security.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.small.name;</term>
-
- <listitem>
- <para><emphasis>Using FreeBSD in embedded
- applications</emphasis></para>
-
- <para>This list discusses topics related to unusually
- small and embedded FreeBSD installations. This is a
- technical mailing list for which strictly technical
- content is expected.</para>
-
- <note>
- <para>This list has been obsoleted by
- &a.embedded.name;.</para>
- </note>
-
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.snapshots.name;</term>
-
- <listitem>
- <para><emphasis>&os; Development Snapshot
- Announcements</emphasis></para>
-
- <para>This list will notify you about the availability
- of new &os; development snapshots for the head/ and
- stable/ branches.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.stable.name;</term>
-
- <listitem>
- <para><emphasis>Discussions about the use of
- &os.stable;</emphasis></para>
-
- <para>This is the mailing list for users of &os.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 <quote>STABLE</quote> should subscribe to this
- list. This is a technical mailing list for which
- strictly technical content is expected.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.standards.name;</term>
-
- <listitem>
- <para><emphasis>C99 & POSIX
- Conformance</emphasis></para>
-
- <para>This is a forum for technical discussions related
- to FreeBSD Conformance to the C99 and the POSIX
- standards.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.toolchain.name;</term>
-
- <listitem>
- <para><emphasis>Maintenance of FreeBSD's integrated
- toolchain</emphasis></para>
-
- <para>This is the mailing list for discussions related
- to the maintenance of the toolchain shipped with &os;.
- This could include the state of Clang and GCC, but also
- pieces of software such as assemblers, linkers and
- debuggers.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.usb.name;</term>
-
- <listitem>
- <para><emphasis>Discussing &os; support for
- USB</emphasis></para>
-
- <para>This is a mailing list for technical discussions
- related to &os; support for USB.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.usergroups.name;</term>
-
- <listitem>
- <para><emphasis>User Group Coordination
- List</emphasis></para>
-
- <para>This is the mailing list for the coordinators from
- each of the local area Users Groups to discuss matters
- with each other and a designated individual from the
- Core Team. This mail list should be limited to meeting
- synopsis and coordination of projects that span User
- Groups.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.vendors.name;</term>
-
- <listitem>
- <para><emphasis>Vendors</emphasis></para>
-
- <para>Coordination discussions between The FreeBSD
- Project and Vendors of software and hardware for
- FreeBSD.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.virtualization.name;</term>
-
- <listitem>
- <para><emphasis>Discussion of various virtualization
- techniques supported by &os;</emphasis></para>
-
- <para>A list to discuss the various virtualization
- techniques supported by &os;. On one hand the focus
- will be on the implementation of the basic functionality
- as well as adding new features. On the other hand users
- will have a forum to ask for help in case of problems or
- to discuss their use cases.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.wip-status.name;</term>
-
- <listitem>
- <para><emphasis>&os; Work-In-Progress
- Status</emphasis></para>
-
- <para>This mailing list can be used to announce creation
- and progress of your &os; related work. Messages
- will be moderated. It is suggested to send the message
- "To:" a more topical &os; list and only "BCC:"
- this list. This way your WIP can also be discussed on
- the topical list, as no discussion is allowed on this
- list.</para>
-
- <para>Look inside the archives for examples of suitable
- messages.</para>
-
- <para>An editorial digest of the messages to this list
- might be posted to the &os; website every few month
- as part of the Status Reports
- <footnote><para><ulink
- url="http://www.freebsd.org/news/status/"></ulink></para></footnote>.
- You can find more examples and past reports there,
- too.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.wireless.name;</term>
-
- <listitem>
- <para><emphasis>Discussions of 802.11 stack, tools device
- driver development</emphasis></para>
-
- <para>The FreeBSD-wireless list focuses on 802.11 stack
- (sys/net80211), device driver and tools development.
- This includes bugs, new features and maintenance.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.xen.name;</term>
-
- <listitem>
- <para><emphasis>Discussion of the &os; port to &xen;
- — implementation and usage</emphasis></para>
-
- <para>A list that focuses on the &os; &xen; port. The
- anticipated traffic level is small enough that it is
- intended as a forum for both technical discussions of
- the implementation and design details as well as
- administrative deployment issues.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.xfce.name;</term>
-
- <listitem>
- <para><emphasis>XFCE</emphasis></para>
-
- <para>This is a forum for discussions related to bring
- the <application>XFCE</application> environment to &os;.
- This is a technical mailing list. It is for individuals
- actively working on porting
- <application>XFCE</application> to &os;, to bring up
- problems or discuss alternative solutions. Individuals
- interested in following the technical discussion are
- also welcome.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.zope.name;</term>
-
- <listitem>
- <para><emphasis>Zope</emphasis></para>
-
- <para>This is a forum for discussions related to bring
- the <application>Zope</application> environment to &os;.
- This is a technical mailing list. It is for individuals
- actively working on porting
- <application>Zope</application> to &os;, to bring up
- problems or discuss alternative solutions. Individuals
- interested in following the technical discussion are
- also welcome.</para>
- </listitem>
- </varlistentry>
- </variablelist>
- </sect2>
+ <listitem>
+ <para>Advertising of non-&os; 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>
+</sect2>
<sect2 id="eresources-mailfiltering">
<title>Filtering on the Mailing Lists</title>
@@ -2041,9 +1250,9 @@
<sect1 id="eresources-news">
<title>Usenet Newsgroups</title>
- <para>In addition to two FreeBSD specific newsgroups, there are
- many others in which FreeBSD is discussed or are otherwise
- relevant to FreeBSD users.</para>
+ <para>In addition to two &os; specific newsgroups, there are
+ many others in which &os; is discussed or are otherwise
+ relevant to &os; users.</para>
<sect2>
<title>BSD Specific Newsgroups</title>
@@ -2070,12 +1279,6 @@
url="news:fr.comp.os.bsd">fr.comp.os.bsd</ulink>
(French)</para>
</listitem>
-
- <listitem>
- <para><ulink
- url="news:it.comp.os.freebsd">it.comp.os.freebsd</ulink>
- (Italian)</para>
- </listitem>
</itemizedlist>
</sect2>
@@ -2114,11 +1317,6 @@
<listitem>
<para><ulink
- url="news:comp.security.unix">comp.security.unix</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink
url="news:comp.sources.unix">comp.sources.unix</ulink></para>
</listitem>
@@ -2138,52 +1336,6 @@
</listitem>
</itemizedlist>
</sect2>
-
- <sect2>
- <title>X Window System</title>
-
- <itemizedlist>
- <listitem>
- <para><ulink
- url="news:comp.windows.x.i386unix">comp.windows.x.i386unix</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="news:comp.windows.x">comp.windows.x</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="news:comp.windows.x.apps">comp.windows.x.apps</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="news:comp.windows.x.announce">comp.windows.x.announce</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="news:comp.windows.x.intrinsics">comp.windows.x.intrinsics</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="news:comp.windows.x.motif">comp.windows.x.motif</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="news:comp.windows.x.pex">comp.windows.x.pex</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="news:comp.emulators.ms-windows.wine">comp.emulators.ms-windows.wine</ulink></para>
- </listitem>
- </itemizedlist>
- </sect2>
</sect1>
<sect1 id="eresources-web">
@@ -2194,14 +1346,14 @@
<itemizedlist>
<listitem><para><ulink url="http://forums.freebsd.org/">The
- FreeBSD Forums</ulink> provide a web based discussion
- forum for FreeBSD questions and technical
+ &os; Forums</ulink> provide a web based discussion
+ forum for &os; questions and technical
discussion.</para></listitem>
<listitem><para><ulink
- url="http://planet.freebsdish.org/">Planet FreeBSD</ulink>
+ url="http://planet.freebsdish.org/">Planet &os;</ulink>
offers an aggregation feed of dozens of blogs written by
- FreeBSD developers. Many developers use this to post quick
+ &os; developers. Many developers use this to post quick
notes about what they are working on, new patches, and other
works in progress.</para></listitem>
@@ -2210,7 +1362,7 @@
YouTube Channel</ulink> provides a collection of high
quality videos from BSD Conferences around the world. This
is a great way to watch key developers give presentations
- about new work in FreeBSD.</para></listitem>
+ about new work in &os;.</para></listitem>
</itemizedlist>
</sect2>
@@ -2220,36 +1372,4 @@
&chap.eresources.www.inc;
</sect2>
</sect1>
-
- <sect1 id="eresources-email">
- <title>Email Addresses</title>
-
- <para>The following user groups provide FreeBSD related email
- addresses for their members. The listed administrator reserves
- the right to revoke the address if it is abused in any
- way.</para>
-
- <informaltable frame="none" pgwide="1">
- <tgroup cols="4">
- <thead>
- <row>
- <entry>Domain</entry>
- <entry>Facilities</entry>
- <entry>User Group</entry>
- <entry>Administrator</entry>
- </row>
- </thead>
-
- <tbody>
- <row>
- <entry>ukug.uk.FreeBSD.org</entry>
- <entry>Forwarding only</entry>
- <entry><email>ukfreebsd@uk.FreeBSD.org</email></entry>
- <entry>Lee Johnston
- <email>lee@uk.FreeBSD.org</email></entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
- </sect1>
</appendix>
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1358522480.41802.YahooMailClassic>