path: root/en_US.ISO8859-1/books/handbook/eresources/chapter.xml

<?xml version="1.0" encoding="iso-8859-1"?>
<!--
     The FreeBSD Documentation Project

     $FreeBSD$
-->
<appendix xmlns="http://docbook.org/ns/docbook"
  xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
  xml:id="eresources">

  <title>Resources on the Internet</title>

  <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 &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 &os; user
    community are outlined below.  Please send other resources not
    mentioned here to the &a.doc; so that they may also be
    included.</para>

  <sect1 xml:id="eresources-www">
    <title>Websites</title>

    <itemizedlist>
      <listitem>
	<para><link xlink:href="https://forums.FreeBSD.org/">The
	    &os; Forums</link> provide a web based discussion forum
	  for &os; questions and technical
	  discussion.</para>
      </listitem>

      <listitem>
	<para>The <link
	    xlink:href="http://www.youtube.com/bsdconferences">BSDConferences
	    YouTube Channel</link> 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 &os;.</para>
      </listitem>
    </itemizedlist>
  </sect1>

  <sect1 xml: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
      &os; audience.  There are a wide variety of lists on a number of
      different &os; topics.  Sending 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 list
      subscribers receive many hundreds of &os; related messages every
      day, and the charters and rules for use are meant 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>To test the ability to send email to &os; lists,
	  send a test message to &a.test.name;.</emphasis>  Please do
	not send test messages to any other list.</para>
    </note>

    <para>When in doubt about what list to post a question to, see
      <link xlink:href="&url.articles.freebsd-questions;">How to get
	best results from the FreeBSD-questions mailing
	list</link>.</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
      <link xlink:href="&url.articles.mailing-list-faq;">Mailing List
	Frequently Asked Questions</link> (FAQ) document.</para>

    <para>Archives are kept for all of the mailing lists and can be
      searched using the
      <link xlink:href="&url.base;/search/index.html">&os; World Wide
	Web server</link>.  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 &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 xml:id="eresources-summary">
      <title>List Summary</title>

      <para><emphasis>General lists:</emphasis> The following are
	general lists which anyone is free (and encouraged) to
	join:</para>

      <informaltable frame="none" pgwide="1">
	<tgroup cols="2">
	  <thead>
	    <row>
	      <entry>List</entry>
	      <entry>Purpose</entry>
	    </row>
	  </thead>

	  <tbody>
	    <row>
	      <entry>&a.advocacy.name;</entry>
	      <entry>&os; Evangelism</entry>
	    </row>

	    <row>
	      <entry>&a.announce.name;</entry>
	      <entry>Important events and Project milestones
		(moderated)</entry>
	    </row>

	    <row>
	      <entry>&a.arch.name;</entry>
	      <entry>Architecture and design discussions</entry>
	    </row>

	    <row>
	      <entry>&a.bugbusters.name;</entry>
	      <entry>Discussions pertaining to the maintenance of
		the &os; problem report database and related
		tools</entry>
	    </row>

	    <row>
	      <entry>&a.bugs.name;</entry>
	      <entry>Bug reports</entry>
	    </row>

	    <row>
	      <entry>&a.chat.name;</entry>
	      <entry>Non-technical items related to the &os;
		community</entry>
	    </row>

	    <row>
	      <entry>&a.chromium.name;</entry>
	      <entry>&os;-specific Chromium issues</entry>
	    </row>

	    <row>
	      <entry>&a.current.name;</entry>
	      <entry>Discussion concerning the use of
		&os.current;</entry>
	    </row>

	    <row>
	      <entry>&a.isp.name;</entry>
	      <entry>Issues for Internet Service Providers using
		&os;</entry>
	    </row>

	    <row>
	      <entry>&a.jobs.name;</entry>
	      <entry>&os; employment and consulting
		opportunities</entry>
	    </row>

	    <row>
	      <entry>&a.quarterly-calls.name;</entry>
	      <entry>Calls for quarterly status reports (moderated)</entry>
	    </row>

	    <row>
	      <entry>&a.questions.name;</entry>
	      <entry>User questions and technical support</entry>
	    </row>

	    <row>
	      <entry>&a.security-notifications.name;</entry>
	      <entry>Security notifications (moderated)</entry>
	    </row>

	    <row>
	      <entry>&a.stable.name;</entry>
	      <entry>Discussion concerning the use of
		&os.stable;</entry>
	    </row>

	    <row>
	      <entry>&a.test.name;</entry>
	      <entry>Where to send test messages instead of to
		one of the actual lists</entry>
	    </row>

	    <row>
	      <entry>&a.women.name;</entry>
	      <entry>FreeBSD advocacy for women</entry>
	    </row>
	  </tbody>
	</tgroup>
      </informaltable>

      <para><emphasis>Technical lists:</emphasis> The following lists
	are for technical discussion.  Read the charter for each list
	carefully before joining or sending mail to one as there are
	firm guidelines for their use and content.</para>

      <informaltable frame="none" pgwide="1">
	<tgroup cols="2">
	  <thead>
	    <row>
	      <entry>List</entry>
	      <entry>Purpose</entry>
	    </row>
	  </thead>

	  <tbody>
	    <row>
	      <entry>&a.acpi.name;</entry>
	      <entry>ACPI and power management development</entry>
	    </row>

	    <row>
	      <entry>&a.amd64.name;</entry>
	      <entry>Porting &os; to AMD64 systems (moderated)</entry>
	    </row>

	    <row>
	      <entry>&a.apache.name;</entry>
	      <entry>Discussion about
		<application>Apache</application> related
		ports</entry>
	    </row>

	    <row>
	      <entry>&a.arm.name;</entry>
	      <entry>Porting &os; to &arm; processors</entry>
	    </row>

	    <row>
	      <entry>&a.atm.name;</entry>
	      <entry>Using ATM networking with &os;</entry>
	    </row>

	    <row>
	      <entry>&a.bluetooth.name;</entry>
	      <entry>Using &bluetooth; technology in &os;</entry>
	    </row>

	    <row>
	      <entry>&a.cloud.name;</entry>
	      <entry>&os; on cloud platforms (EC2, GCE, Azure,
		etc.)</entry>
	    </row>

	    <row>
	      <entry>&a.cluster.name;</entry>
	      <entry>Using &os; in a clustered environment</entry>
	    </row>

	    <row>
	      <entry>&a.database.name;</entry>
	      <entry>Discussing database use and development under
		&os;</entry>
	    </row>

	    <row>
	      <entry>&a.desktop.name;</entry>
	      <entry>Using and improving &os; on the desktop</entry>
	    </row>

	    <row>
	      <entry>&a.dev-ci.name;</entry>
	      <entry>Build and test reports from the Continuous
		Integration servers</entry>
	    </row>

	    <row>
	      <entry>&a.dev-reviews.name;</entry>
	      <entry>Notifications of the FreeBSD review
		system</entry>
	    </row>

	    <row>
	      <entry>&a.doc.name;</entry>
	      <entry>Creating &os; related documents</entry>
	    </row>

	    <row>
	      <entry>&a.drivers.name;</entry>
	      <entry>Writing device drivers for &os;</entry>
	    </row>

	    <row>
	      <entry>&a.dtrace.name;</entry>
	      <entry>Using and working on DTrace in &os;</entry>
	    </row>

	    <row>
	      <entry>&a.eclipse.name;</entry>
	      <entry>&os; users of Eclipse IDE, tools, rich client
		applications and ports.</entry>
	    </row>

	    <row>
	      <entry>&a.elastic.name;</entry>
	      <entry>&os;-specific ElasticSearch discussions</entry>
	    </row>

	    <row>
	      <entry>&a.embedded.name;</entry>
	      <entry>Using &os; in embedded applications</entry>
	    </row>

	    <row>
	      <entry>&a.eol.name;</entry>
	      <entry>Peer support of &os;-related software that
		is no longer supported by the &os; 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.enlightenment.name;</entry>
	      <entry>Porting <application>Enlightenment</application>
		and <application>Enlightenment</application>
		applications</entry>
	    </row>

	    <row>
	      <entry>&a.erlang.name;</entry>
	      <entry>&os;-specific Erlang discussions</entry>
	    </row>

	    <row>
	      <entry>&a.firewire.name;</entry>
	      <entry>&os; &firewire; (iLink, IEEE 1394) technical
		discussion</entry>
	    </row>

	    <row>
	      <entry>&a.fortran.name;</entry>
	      <entry>Fortran on &os;</entry>
	    </row>

	    <row>
	      <entry>&a.fs.name;</entry>
	      <entry>File systems</entry>
	    </row>

	    <row>
	      <entry>&a.games.name;</entry>
	      <entry>Support for Games on &os;</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.git.name;</entry>
	      <entry>Discussion of git use in the &os; project</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.haskell.name;</entry>
	      <entry>&os;-specific Haskell issues and
		discussions</entry>
	    </row>

	    <row>
	      <entry>&a.hardware.name;</entry>
	      <entry>General discussion of hardware for running
		&os;</entry>
	    </row>

	    <row>
	      <entry>&a.i18n.name;</entry>
	      <entry>&os; Internationalization</entry>
	    </row>

	    <row>
	      <entry>&a.infiniband.name;</entry>
	      <entry>Infiniband on &os;</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
		&os;</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 &os;</entry>
	    </row>

	    <row>
	      <entry>&a.mips.name;</entry>
	      <entry>Porting &os; to &mips;</entry>
	    </row>

	    <row>
	      <entry>&a.mono.name;</entry>
	      <entry>Mono and C# applications on &os;</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.ocaml.name;</entry>
	      <entry>&os;-specific OCaml discussions</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.pkg.name;</entry>
	      <entry>Binary package management and package
		tools discussion</entry>
	    </row>

	    <row>
	      <entry>&a.pkg-fallout.name;</entry>
	      <entry>Fallout logs from package building</entry>
	    </row>

	    <row>
	      <entry>&a.pkgbase.name;</entry>
	      <entry>Packaging the &os; base 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 (moderated)</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 &os; to the &powerpc;</entry>
	    </row>

	    <row>
	      <entry>&a.proliant.name;</entry>
	      <entry>Technical discussion of &os; on HP ProLiant
		server platforms</entry>
	    </row>

	    <row>
	      <entry>&a.python.name;</entry>
	      <entry>&os;-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
		&os;</entry>
	    </row>

	    <row>
	      <entry>&a.riscv.name;</entry>
	      <entry>Porting &os; to &risc-v; systems</entry>
	    </row>

	    <row>
	      <entry>&a.ruby.name;</entry>
	      <entry>&os;-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 &os;</entry>
	    </row>

	    <row>
	      <entry>&a.snapshots.name;</entry>
	      <entry>&os; Development Snapshot Announcements</entry>
	    </row>

	    <row>
	      <entry>&a.sparc.name;</entry>
	      <entry>Porting &os; to &sparc; based systems</entry>
	    </row>

	    <row>
	      <entry>&a.standards.name;</entry>
	      <entry>&os;'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>&os;-specific Tcl/Tk discussions</entry>
	    </row>

	    <row>
	      <entry>&a.testing.name;</entry>
	      <entry>Testing on &os;</entry>
	    </row>

	    <row>
	      <entry>&a.tex.name;</entry>

	      <entry>Porting <application>TeX</application> and its
		applications to &os;</entry>
	    </row>

	    <row>
	      <entry>&a.threads.name;</entry>
	      <entry>Threading in &os;</entry>
	    </row>

	    <row>
	      <entry>&a.tilera.name;</entry>
	      <entry>Porting &os; to the Tilera family of
		CPUs</entry>
	    </row>

	    <row>
	      <entry>&a.tokenring.name;</entry>
	      <entry>Support Token Ring in &os;</entry>
	    </row>

	    <row>
	      <entry>&a.toolchain.name;</entry>
	      <entry>Maintenance of &os;'s integrated
		toolchain</entry>
	    </row>

	    <row>
	      <entry>&a.translators.name;</entry>
	      <entry>Translating &os; documents and programs</entry>
	    </row>

	    <row>
	      <entry>&a.transport.name;</entry>
	      <entry>Discussions of transport level network protocols
		in &os;</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 &os;</entry>
	    </row>

	    <row>
	      <entry>&a.xen.name;</entry>
	      <entry>Discussion of the &os; port to &xen; &mdash;
		implementation and usage</entry>
	    </row>

	    <row>
	      <entry>&a.xfce.name;</entry>
	      <entry><application>XFCE</application> for &os; &mdash;
		porting and maintaining</entry>
	    </row>

	    <row>
	      <entry>&a.zope.name;</entry>
	      <entry><application>Zope</application> for &os; &mdash;
		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 in order to
	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.wip-status.name;</entry>
	      <entry>&os; Work-In-Progress Status</entry>
	    </row>

	    <row>
	      <entry>&a.wireless.name;</entry>
	      <entry>Discussions of 802.11 stack, tools, device driver
		development</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,
	the digest options can be changed in the 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&nbsp;/ 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-10.name;</entry>
	      <entry><filename>/usr/src</filename></entry>
	      <entry>All changes to the <filename>stable/10</filename>
		branch of the src Subversion repository</entry>
	    </row>

	    <row>
	      <entry>&a.svn-src-stable-11.name;</entry>
	      <entry><filename>/usr/src</filename></entry>
	      <entry>All changes to the <filename>stable/11</filename>
		branch of the src Subversion repository</entry>
	    </row>

	    <row>
	      <entry>&a.svn-src-stable-12.name;</entry>
	      <entry><filename>/usr/src</filename></entry>
	      <entry>All changes to the <filename>stable/12</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 xml:id="eresources-subscribe">
      <title>How to Subscribe</title>

      <para>To subscribe to a list, click the list name at
	&a.mailman.lists.link;.  The page that is displayed should
	contain all of the necessary subscription instructions for
	that list.</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 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.</para>

      <para>It is important to keep discussion in the technical
	mailing lists on a technical track.  To only receive important
	announcements, instead join the &a.announce;, which is
	intended for infrequent traffic.</para>
    </sect2>

    <sect2 xml:id="eresources-charters">
      <title>List Charters</title>

      <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 removed from all &os; 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.  If the list is about
	    technical issues, the 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 &amp; -scsi</quote>),
	    there really is no reason to post to more than one list at
	    a time.  If a message is received with multiple mailing
	    lists on the <literal>Cc</literal> line, trim the
	    <literal>Cc</literal> line before replying.  <emphasis>The
	      person who replies is still responsible for
	      cross-posting, 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-&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>

      <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.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 &os; events.
	      This includes announcements about snapshots and other
	      releases.  It contains announcements of new &os;
	      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 &os;
	      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 &os;</emphasis></para>

	    <para>This is the forum where &os;'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 &os;.
	      Whenever possible, bugs should be submitted using the
	      <link
		xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">web
		interface</link> to it.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.chat.name;</term>

	  <listitem>
	    <para><emphasis>Non technical items related to the &os;
		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>&os;-specific Chromium
		issues</emphasis></para>

	    <para>This is a list for the discussion of Chromium
	      support for &os;.  This is a technical list to
	      discuss development and installation of Chromium.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.cloud.name;</term>

	  <listitem>
	    <para><emphasis>Running &os; on various cloud
		platforms</emphasis></para>

	    <para>This list discusses running &os; on Amazon EC2,
	      Google Compute Engine, Microsoft Azure, and other cloud
	      computing platforms.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.core.name;</term>

	  <listitem>
	    <para><emphasis>&os; 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
	      &os;-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.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
	      desktop.  It is primarily a place for desktop porters
	      and users to discuss issues and improve &os;'s desktop
	      support.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.dev-ci.name;</term>
	  <listitem>
	    <para><emphasis>Continuous Integration reports of build
		and test results</emphasis></para>

	    <para>All Continuous Integration reports of build and test
	      results</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.dev-reviews.name;</term>
	  <listitem>
	    <para><emphasis>Notifications of work in progress in
		FreeBSD's review tool</emphasis></para>

	    <para>Automated notifications of work in progress for
	      review in FreeBSD's review tools, including
	      patches.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.doc.name;</term>

	  <listitem>
	    <para><emphasis>Documentation Project</emphasis></para>

	    <para>This mailing list is for the discussion of issues
	      and projects related to the creation of documentation
	      for &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>

	<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 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>

	<varlistentry>
	  <term>&a.dtrace.name;</term>

	  <listitem>
	    <para><emphasis>Using and working on DTrace in
		&os;</emphasis></para>

	    <para>DTrace is an integrated component of &os; that
	      provides a framework for understanding the kernel as
	      well as user space programs at run time.  The mailing
	      list is an archived discussion for developers of the
	      code as well as those using it.</para>
	  </listitem>
	</varlistentry>

	<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
	      who would like to develop &os; specific applications
	      using the Eclipse framework.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.embedded.name;</term>

	  <listitem>
	    <para><emphasis>Using &os; in embedded
		applications</emphasis></para>

	    <para>This list discusses topics related to using &os; in
	      embedded systems.  This is a technical mailing list for
	      which strictly technical content is expected.  For the
	      purpose of this list, embedded systems are 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>

	<varlistentry>
	  <term>&a.emulation.name;</term>

	  <listitem>
	    <para><emphasis>Emulation of other systems such as
		Linux/&ms-dos;/&windows;</emphasis></para>

	    <para>This is a forum for technical discussions related
	      to running programs written for other operating systems
	      on &os;.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.enlightenment.name;</term>

	  <listitem>
	    <para><emphasis>Enlightenment</emphasis></para>

	    <para>Discussions concerning the
	      <application>Enlightenment</application> Desktop
	      Environment for &os; systems.  This is a technical
	      mailing list for which strictly technical content is
	      expected.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.eol.name;</term>

	  <listitem>
	    <para><emphasis>Peer support of &os;-related software
		that is no longer supported by the &os;
		Project.</emphasis></para>

	    <para>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.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.firewire.name;</term>

	  <listitem>
	    <para><emphasis>&firewire; (iLink, IEEE
		1394)</emphasis></para>

	    <para>This is a mailing list for discussion of the design
	      and implementation of a &firewire; (aka IEEE 1394 aka
	      iLink) subsystem for &os;.  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>

	<varlistentry>
	  <term>&a.fortran.name;</term>

	  <listitem>
	    <para><emphasis>Fortran on &os;</emphasis></para>

	    <para>This is the mailing list for discussion of Fortran
	      related ports on &os;: compilers, libraries, scientific
	      and engineering applications from laptops to HPC
	      clusters.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.fs.name;</term>

	  <listitem>
	    <para><emphasis>File systems</emphasis></para>

	    <para>Discussions concerning &os; filesystems.  This is a
	      technical mailing list for which strictly technical
	      content is expected.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.games.name;</term>

	  <listitem>
	    <para><emphasis>Games on &os;</emphasis></para>

	    <para>This is a technical list for discussions related to
	      bringing games to &os;.  It is for individuals actively
	      working on porting games 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.gecko.name;</term>

	  <listitem>
	    <para><emphasis>Gecko Rendering Engine</emphasis></para>

	    <para>This is a forum about
	      <application>Gecko</application> applications using
	      &os;.</para>

	    <para>Discussion centers around Gecko Ports applications,
	      their installation, their development and their support
	      within &os;.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.geom.name;</term>

	  <listitem>
	    <para><emphasis>GEOM</emphasis></para>

	    <para>Discussions specific to GEOM and related
	      implementations.  This is a technical mailing list for
	      which strictly technical content is expected.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.git.name;</term>

	  <listitem>
	    <para><emphasis>Use of git in the &os;
		project</emphasis></para>

	    <para>Discussions of how to use git in &os;
	      infrastructure including the github mirror and other
	      uses of git for project collaboration.  Discussion area
	      for people using git against the &os; github mirror.
	      People wanting to get started with the mirror or git
	      in general on &os; can ask here.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.gnome.name;</term>

	  <listitem>
	    <para><emphasis>GNOME</emphasis></para>

	    <para>Discussions concerning The
	      <application>GNOME</application> Desktop Environment
	      for &os; systems.  This is a technical mailing list
	      for which strictly technical content is expected.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.infiniband.name;</term>

	  <listitem>
	    <para><emphasis>Infiniband on &os;</emphasis></para>

	    <para>Technical mailing list discussing Infiniband, OFED,
	      and OpenSM on &os;.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.ipfw.name;</term>

	  <listitem>
	    <para><emphasis>IP Firewall</emphasis></para>

	    <para>This is the forum for technical discussions
	      concerning the redesign of the IP firewall code in
	      &os;.  This is a technical mailing list for which
	      strictly technical content is expected.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.isdn.name;</term>

	  <listitem>
	    <para><emphasis>ISDN Communications</emphasis></para>

	    <para>This is the mailing list for people discussing the
	      development of ISDN support for &os;.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.java.name;</term>

	  <listitem>
	    <para><emphasis>&java; Development</emphasis></para>

	    <para>This is the mailing list for people discussing the
	      development of significant &java; applications for &os;
	      and the porting and maintenance of &jdk;s.</para>
	  </listitem>
	</varlistentry>

	<varlistentry xml:id="eresources-charters-jobs">
	  <term>&a.jobs.name;</term>

	  <listitem>
	    <para><emphasis>Jobs offered and sought</emphasis></para>

	    <para>This is a forum for posting employment notices
	      specifically related to &os; and resumes from those
	      seeking &os;-related employment.  This is
	      <emphasis>not</emphasis> a mailing list for general
	      employment issues since adequate forums for that already
	      exist elsewhere.</para>

	    <para>Note that this list, like other <systemitem
		class="fqdomainname">FreeBSD.org</systemitem>
	      mailing lists, is distributed worldwide.  Be clear about
	      the geographic location and the extent to which
	      telecommuting or assistance with relocation is
	      available.</para>

	    <para>Email should use open formats only &mdash;
	      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
	      &microsoft; Word (<filename>.doc</filename>) will be
	      rejected by the mailing list server.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.kde.name;</term>

	  <listitem>
	    <para><emphasis>KDE</emphasis></para>

	    <para>Discussions concerning
	      <application>KDE</application> on &os; systems.
	      This is a technical mailing list for which strictly
	      technical content is expected.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.hackers.name;</term>

	  <listitem>
	    <para><emphasis>Technical discussions</emphasis></para>

	    <para>This is a forum for technical discussions related
	      to &os;.  This is the primary technical mailing list.
	      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.  This is a technical
	      mailing list for which strictly technical content is
	      expected.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.hardware.name;</term>

	  <listitem>
	    <para><emphasis>General discussion of &os;
		hardware</emphasis></para>

	    <para>General discussion about the types of hardware that
	      &os; runs on, various problems and suggestions
	      concerning what to buy or avoid.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.hubs.name;</term>

	  <listitem>
	    <para><emphasis>Mirror sites</emphasis></para>

	    <para>Announcements and discussion for people who run &os;
	      mirror sites.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.isp.name;</term>

	  <listitem>
	    <para><emphasis>Issues for Internet Service
		Providers</emphasis></para>

	    <para>This mailing list is for discussing topics relevant
	      to Internet Service Providers (ISPs) using &os;.  This
	      is a technical mailing list for which strictly technical
	      content is expected.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.mono.name;</term>

	  <listitem>
	    <para><emphasis>Mono and C# applications on
		&os;</emphasis></para>

	    <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>

	<varlistentry>
	  <term>&a.ocaml.name;</term>

	  <listitem>
	    <para><emphasis>&os;-specific OCaml
		discussions</emphasis></para>

	    <para>This is a list for discussions related to the OCaml
	      support on &os;.  This is a technical mailing list. It
	      is for individuals working on OCaml ports, 3rd party
	      libraries and frameworks.  Individuals interested in the
	      technical discussion are also welcome.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.office.name;</term>

	  <listitem>
	    <para><emphasis>Office applications on
		&os;</emphasis></para>

	    <para>Discussion centers around office applications, their
	      installation, their development and their support within
	      &os;.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.ops-announce.name;</term>

	  <listitem>
	    <para><emphasis>Project Infrastructure
		Announcements</emphasis></para>

	    <para>This is the mailing list for people interested in
	      changes and issues related to the FreeBSD.org Project
	      infrastructure.</para>

	    <para>This moderated list is strictly for announcements:
	      no replies, requests, discussions, or opinions.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.performance.name;</term>

	  <listitem>
	    <para><emphasis>Discussions about tuning or speeding up
		&os;</emphasis></para>

	    <para>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 includes talking about &os;
	      installations that are either 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 is a highly
	      technical list ideally suited for experienced &os;
	      users, hackers, or administrators interested in keeping
	      &os; 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>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.pf.name;</term>

	  <listitem>
	    <para><emphasis>Discussion and questions about the packet
		filter firewall system</emphasis></para>

	    <para>Discussion concerning the packet filter (pf)
	      firewall system in terms of &os;.  Technical discussion
	      and user questions are both welcome.  This list is also
	      a place to discuss the ALTQ QoS framework.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.pkg.name;</term>

	  <listitem>
	    <para><emphasis>Binary package management and package
		tools discussion</emphasis></para>

	    <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 third party packages.</para>

	    <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>

	<varlistentry>
	  <term>&a.pkg-fallout.name;</term>

	  <listitem>
	    <para><emphasis>Fallout logs from package
		building</emphasis></para>

	    <para>All packages building failures logs from the package
	      building clusters</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.pkgbase.name;</term>

	  <listitem>
	    <para><emphasis>Packaging the &os; base
		system.</emphasis></para>

	    <para>Discussions surrounding implementation and issues
	      regarding packaging the &os; base system.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.platforms.name;</term>

	  <listitem>
	    <para><emphasis>Porting to Non &intel;
		platforms</emphasis></para>

	    <para>Cross-platform &os; issues, general discussion and
	      proposals for non &intel; &os; ports.  This is a
	      technical mailing list for which strictly technical
	      content is expected.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.ports.name;</term>

	  <listitem>
	    <para><emphasis>Discussion of
		<quote>ports</quote></emphasis></para>

	    <para>Discussions concerning &os;'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>

	<varlistentry>
	  <term>&a.ports-announce.name;</term>

	  <listitem>
	    <para><emphasis>Important news and instructions about the
		&os;&nbsp;<quote>Ports
		  Collection</quote></emphasis></para>

	    <para>Important news for developers, porters, and users of
	      the <quote>Ports Collection</quote>
	      (<filename>/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>

	<varlistentry>
	  <term>&a.ports-bugs.name;</term>

	  <listitem>
	    <para><emphasis>Discussion of
		<quote>ports</quote> bugs</emphasis></para>

	    <para>Discussions concerning problem reports for &os;'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>

	<varlistentry>
	  <term>&a.proliant.name;</term>

	  <listitem>
	    <para><emphasis>Technical discussion of &os; on HP
		ProLiant server platforms</emphasis></para>

	    <para>This mailing list is to be used for the technical
	      discussion of the usage of &os; 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>

	<varlistentry>
	  <term>&a.python.name;</term>

	  <listitem>
	    <para><emphasis>Python on &os;</emphasis></para>

	    <para>This is a list for discussions related to improving
	      Python-support on &os;.  This is a technical mailing
	      list.  It is for individuals working on porting Python,
	      its third party modules and
	      <application>Zope</application> stuff to &os;.
	      Individuals interested in following the technical
	      discussion are also welcome.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.questions.name;</term>

	  <listitem>
	    <para><emphasis>User questions</emphasis></para>

	    <para>This is the mailing list for questions about &os;.
	      Do not send <quote>how to</quote> questions to the
	      technical lists unless the question is quite
	      technical.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.ruby.name;</term>

	  <listitem>
	    <para><emphasis>&os;-specific Ruby
		discussions</emphasis></para>

	    <para>This is a list for discussions related to the Ruby
	      support on &os;.  This is a technical mailing list.  It
	      is for individuals working on Ruby ports, third party
	      libraries and frameworks.</para>

	    <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 &os;.  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>&os; 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 &os; security problems and fixes.
	      This is not a discussion list.  The discussion list is
	      FreeBSD-security.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.snapshots.name;</term>

	  <listitem>
	    <para><emphasis>&os; Development Snapshot
		Announcements</emphasis></para>

	    <para>This list provides notifications 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;.
	      <quote>STABLE</quote> is the branch where development
	      continues after a RELEASE, including bug fixes and new
	      features.  The ABI is kept stable for binary
	      compatibility.  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 &amp; POSIX
		Conformance</emphasis></para>

	    <para>This is a forum for technical discussions related to
	      &os; Conformance to the C99 and the POSIX
	      standards.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.teaching.name;</term>

	  <listitem>
	    <para><emphasis>Teaching with &os;</emphasis></para>

	    <para>Non technical mailing list discussing teaching
	      with &os;.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.testing.name;</term>

	  <listitem>
	    <para><emphasis>Testing on &os;</emphasis></para>

	    <para>Technical mailing list discussing testing on &os;,
	      including ATF/Kyua, test build infrastructure, port
	      tests to &os; from other operating systems (NetBSD,
	      ...), etc.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.tex.name;</term>

	  <listitem>
	    <para><emphasis>Porting <application>TeX</application> and
		its applications to &os;</emphasis></para>

	    <para>This is a technical mailing list for discussions
	      related to TeX and its applications on &os;.  It is for
	      individuals actively working on porting TeX to FreeBSD,
	      to bring up problems or discuss alternative solutions.
	      Individuals interested in following the technical
	      discussion are also welcome.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.toolchain.name;</term>

	  <listitem>
	    <para><emphasis>Maintenance of &os;'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.transport.name;</term>

	  <listitem>
	    <para><emphasis>Discussions of transport level network
		protocols in &os;</emphasis></para>

	    <para>The transport mailing list exists for the discussion
	      of issues and designs around the transport level
	      protocols in the &os; network stack, including TCP,
	      SCTP and UDP.  Other networking topics, including
	      driver specific and network protocol issues should be
	      discussed on the &a.net;.</para>
	  </listitem>
	</varlistentry>

	<varlistentry>
	  <term>&a.translators.name;</term>

	  <listitem>
	    <para><emphasis>Translating &os; documents and
		programs</emphasis></para>

	    <para>A discussion list where translators of &os;
	      documents from English into other languages can talk
	      about translation methods and tools.  New members are
	      asked to introduce themselves and mention the languages
	      they are interested in translating.</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.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 by developers to
	      announce the creation and progress of &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 the 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 months as
	      part of the Status Reports
	      <footnote><para><uri
		    xlink:href="https://www.freebsd.org/news/status/">https://www.freebsd.org/news/status/</uri></para></footnote>.
	      Past reports are archived.</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;
		&mdash; 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>

    <sect2 xml:id="eresources-mailfiltering">
      <title>Filtering on the Mailing Lists</title>

      <para>The &os; mailing lists are filtered in multiple ways to
	avoid the distribution of spam, viruses, and other unwanted
	emails.  The filtering actions described in this section do
	not include all those used to protect the mailing
	lists.</para>

      <para>Only certain types of attachments are allowed on the
	mailing lists.  All attachments with a MIME content type not
	found in the list below will be stripped before an email is
	distributed on the mailing lists.</para>

      <itemizedlist>
	<listitem>
	  <para>application/octet-stream</para>
	</listitem>

	<listitem>
	  <para>application/pdf</para>
	</listitem>

	<listitem>
	  <para>application/pgp-signature</para>
	</listitem>

	<listitem>
	  <para>application/x-pkcs7-signature</para>
	</listitem>

	<listitem>
	  <para>message/rfc822</para>
	</listitem>

	<listitem>
	  <para>multipart/alternative</para>
	</listitem>

	<listitem>
	  <para>multipart/related</para>
	</listitem>

	<listitem>
	  <para>multipart/signed</para>
	</listitem>

	<listitem>
	  <para>text/html</para>
	</listitem>

	<listitem>
	  <para>text/plain</para>
	</listitem>

	<listitem>
	  <para>text/x-diff</para>
	</listitem>

	<listitem>
	  <para>text/x-patch</para>
	</listitem>
      </itemizedlist>

      <note>
	<para>Some of the mailing lists might allow attachments of
	  other MIME content types, but the above list should be
	  applicable for most of the mailing lists.</para>
      </note>

      <para>If an email contains both an HTML and a plain text
	version, the HTML version will be removed.  If an email
	contains only an HTML version, it will be converted to plain
	text.</para>
    </sect2>
  </sect1>

  <sect1 xml:id="eresources-news">
    <title>Usenet Newsgroups</title>

    <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>

      <itemizedlist>
	<listitem>
	  <para><link
	      xlink:href="news:comp.unix.bsd.freebsd.announce">comp.unix.bsd.freebsd.announce</link></para>
	</listitem>

	<listitem>
	  <para><link
	      xlink:href="news:comp.unix.bsd.freebsd.misc">comp.unix.bsd.freebsd.misc</link></para>
	</listitem>

	<listitem>
	  <para><link
	      xlink:href="news:de.comp.os.unix.bsd">de.comp.os.unix.bsd</link>
	    (German)</para>
	</listitem>

	<listitem>
	  <para><link
	      xlink:href="news:fr.comp.os.bsd">fr.comp.os.bsd</link>
	    (French)</para>
	</listitem>
      </itemizedlist>
    </sect2>

    <sect2>
      <title>Other &unix; Newsgroups of Interest</title>

      <itemizedlist>
	<listitem>
	  <para><link
	      xlink:href="news:comp.unix">comp.unix</link></para>
	</listitem>

	<listitem>
	  <para><link
	      xlink:href="news:comp.unix.questions">comp.unix.questions</link></para>
	</listitem>

	<listitem>
	  <para><link
	      xlink:href="news:comp.unix.admin">comp.unix.admin</link></para>
	</listitem>

	<listitem>
	  <para><link
	      xlink:href="news:comp.unix.programmer">comp.unix.programmer</link></para>
	</listitem>

	<listitem>
	  <para><link
	      xlink:href="news:comp.unix.shell">comp.unix.shell</link></para>
	</listitem>

	<listitem>
	  <para><link
	      xlink:href="news:comp.unix.misc">comp.unix.misc</link></para>
	</listitem>

	<listitem>
	  <para><link
	      xlink:href="news:comp.unix.bsd">comp.unix.bsd</link></para>
	</listitem>
      </itemizedlist>
    </sect2>

    <sect2>
      <title>X Window System</title>

      <itemizedlist>
	<listitem>
	  <para><link
	      xlink:href="news:comp.windows.x">comp.windows.x</link></para>
	</listitem>
      </itemizedlist>
    </sect2>
  </sect1>

  <sect1 xml:id="eresources-web">
    <title>Official Mirrors</title>

    &chap.eresources.www.index.inc;

    &chap.mirrors.lastmod.inc;

    &chap.eresources.www.inc;
  </sect1>
</appendix>