Convert names, descriptions and e-mail addresses of FreeBSD committers
and mailing lists to SGML entities. Reviewed by: keramida Approved by: keramida, silence on -doc
This commit is contained in:
parent
767c635e20
commit
81f0937cee
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=12473
8 changed files with 62 additions and 55 deletions
en_US.ISO8859-1/articles
committers-guide
contributing
formatting-media
freebsd-questions
hubs
new-users
releng-packages
releng
|
@ -71,8 +71,8 @@
|
|||
|
||||
<row>
|
||||
<entry><emphasis>Mailing List</emphasis></entry>
|
||||
<entry><email>developers@FreeBSD.org</email>,
|
||||
<email>cvs-committers@FreeBSD.org</email></entry>
|
||||
<entry>&a.developers;,
|
||||
&a.committers;</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
|
@ -525,11 +525,11 @@
|
|||
</itemizedlist>
|
||||
|
||||
<para>You will almost certainly get a conflict because
|
||||
of the <literal>$Id: article.sgml,v 1.98 2002-03-08 19:52:25 obrien Exp $</literal> (or in FreeBSD's case,
|
||||
of the <literal>$Id: article.sgml,v 1.99 2002-03-15 08:10:46 roam Exp $</literal> (or in FreeBSD's case,
|
||||
<literal>$<!-- stop expansion -->FreeBSD<!-- stop expansion -->$</literal>) lines, so you will have to edit
|
||||
the file to resolve the conflict (remove the marker lines and
|
||||
the second <literal>$Id: article.sgml,v 1.98 2002-03-08 19:52:25 obrien Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.98 2002-03-08 19:52:25 obrien Exp $</literal> line intact).</para>
|
||||
the second <literal>$Id: article.sgml,v 1.99 2002-03-15 08:10:46 roam Exp $</literal> line, leaving the original
|
||||
<literal>$Id: article.sgml,v 1.99 2002-03-15 08:10:46 roam Exp $</literal> line intact).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
@ -795,7 +795,7 @@ checkout -P</programlisting>
|
|||
that it is actually merely the Newtonian manifestation of a
|
||||
sentient transdimensional entity. It is not humanly possible
|
||||
to know its every quirk inside out, so do not be afraid to ask
|
||||
the resident AI (<email>cvs@FreeBSD.org</email>) for help when
|
||||
the resident AI (&a.cvs;) for help when
|
||||
you screw up.</para>
|
||||
</listitem>
|
||||
|
||||
|
@ -863,7 +863,7 @@ checkout -P</programlisting>
|
|||
not have to write a comprehensive biography, just write a paragraph
|
||||
or two about who you are and what you plan to be working on as a
|
||||
committer in FreeBSD. Email this to
|
||||
<email>developers@FreeBSD.org</email> and you will be on your
|
||||
the &a.developers; and you will be on your
|
||||
way!</para>
|
||||
</listitem>
|
||||
|
||||
|
@ -874,8 +874,8 @@ checkout -P</programlisting>
|
|||
containing the e-mail address where you want mail addressed to
|
||||
<replaceable>yourusername</replaceable>@FreeBSD.org to be forwarded.
|
||||
This includes all of the commit messages as well as any other mail
|
||||
addressed to <email>cvs-committers@FreeBSD.org</email> and
|
||||
<email>developers@FreeBSD.org</email>. Really
|
||||
addressed to the &a.committers; and
|
||||
&a.developers;. Really
|
||||
large mailboxes which have taken up permanent residence on
|
||||
<hostid>hub</hostid> often get <quote>accidently</quote> truncated
|
||||
without warning, so forward it or read it and you will not lose
|
||||
|
@ -1095,7 +1095,7 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
stylesheets and related code under
|
||||
<filename>doc/share/sgml</filename>. If you have got questions
|
||||
about these you are encouraged to send them via the
|
||||
<email>doc@FreeBSD.org</email> mailing list. Committers
|
||||
&a.doc;. Committers
|
||||
interested in contributing to the documentation should familiarise
|
||||
themselves with the
|
||||
<ulink url="../../books/fdp-primer/index.html">Documentation Project Primer</ulink>.</para>
|
||||
|
@ -1248,7 +1248,7 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
Examples are Core
|
||||
voting, announcements, etc... developers@FreeBSD.org is
|
||||
<emphasis>not</emphasis> intended as a place for code reviews or a
|
||||
replacement for arch@FreeBSD.org or audit@FreeBSD.org. In fact
|
||||
replacement for the &a.arch; or the &a.audit;. In fact
|
||||
using it as such hurts the FreeBSD Project as it gives a sense of a
|
||||
closed list where general decisions affecting all of the FreeBSD
|
||||
using community are made with out being <quote>open</quote>.
|
||||
|
@ -1568,7 +1568,7 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
<para>This is pretty clear - you are not allowed to make
|
||||
direct modifications to the CVS repository, period. In
|
||||
case of difficulty, ask one of the repository meisters by
|
||||
sending mail to <email>cvs@FreeBSD.org</email> and simply
|
||||
sending mail to the &a.cvs; and simply
|
||||
wait for them to fix the problem and get back to you. Do
|
||||
not attempt to fix the problem yourself!</para>
|
||||
|
||||
|
@ -2038,8 +2038,8 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
|
||||
<answer>
|
||||
<para>The ports manager will send out warning messages to
|
||||
the <email>freebsd-ports@FreeBSD.org</email> and
|
||||
<email>cvs-committers@FreeBSD.org</email> mailing lists
|
||||
the &a.ports; and
|
||||
&a.committers;
|
||||
announcing the start of the impending release, usually
|
||||
two or three weeks in advance. The exact starting time
|
||||
will not be determined until a few days before the
|
||||
|
@ -2050,7 +2050,7 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
|
||||
<para>When the freeze starts, there will be another
|
||||
announcement to the
|
||||
<email>cvs-committers@FreeBSD.org</email> list, of
|
||||
&a.committers;, of
|
||||
course.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
@ -2063,8 +2063,8 @@ docs:Documentation Bug:nik:</programlisting>
|
|||
<answer>
|
||||
<para>A few hours after the release, the ports manager
|
||||
will send out a mail to the
|
||||
<email>freebsd-ports@FreeBSD.org</email> and
|
||||
<email>cvs-committers@FreeBSD.org</email> mailing lists
|
||||
&a.ports; and
|
||||
&a.committers;
|
||||
announcing the end of the ports freeze. Note that the
|
||||
release being cut does not automatically end the freeze.
|
||||
We have to make sure there will not be any last minute
|
||||
|
|
|
@ -482,8 +482,8 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
|
||||
<para>We can always use new mirror sites for FTP, WWW or
|
||||
<command>cvsup</command>. If you would like to be such a mirror,
|
||||
please contact the FreeBSD project administrators
|
||||
<email>hubs@FreeBSD.org</email> for more information.</para>
|
||||
please contact the
|
||||
&a.hubs; for more information.</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
|
|
@ -1,4 +1,6 @@
|
|||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
|
||||
%authors;
|
||||
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
|
||||
%man;
|
||||
]>
|
||||
|
@ -600,7 +602,7 @@ swapon: added /dev/da0b as swap space</screen>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Jordan Hubbard (<email>jkh@FreeBSD.org</email>) for
|
||||
<para>&a.jkh; for
|
||||
making sysinstall useful for this type of task.</para>
|
||||
</listitem>
|
||||
|
||||
|
@ -611,7 +613,7 @@ swapon: added /dev/da0b as swap space</screen>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Greg Lehey (<email>grog@FreeBSD.org</email>) for
|
||||
<para>&a.grog; for
|
||||
checking my work and pointing out inaccuracies, as well as
|
||||
miscellaneous support.</para>
|
||||
</listitem>
|
||||
|
|
|
@ -1,6 +1,8 @@
|
|||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
|
||||
%man;
|
||||
<!ENTITY % mailing-lists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
|
||||
%mailing-lists;
|
||||
]>
|
||||
|
||||
<article>
|
||||
|
@ -72,7 +74,7 @@
|
|||
<title id="subscribe">How to subscribe to FreeBSD-questions</title>
|
||||
|
||||
<para>FreeBSD-questions is a mailing list, so you need mail access. Send
|
||||
a mail message to <email>majordomo@FreeBSD.org</email> with the single
|
||||
a mail message to &a.majordomo; with the single
|
||||
line:</para>
|
||||
|
||||
<literallayout class="monospaced">subscribe FreeBSD-questions</literallayout>
|
||||
|
|
|
@ -3,6 +3,8 @@
|
|||
%man;
|
||||
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
|
||||
%authors;
|
||||
<!ENTITY % mailing-lists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
|
||||
%mailing-lists;
|
||||
<!ENTITY % not.published "IGNORE">
|
||||
]>
|
||||
|
||||
|
@ -214,7 +216,7 @@
|
|||
offering it via CVSup. Still it is possible to offer
|
||||
the CVS repository via AnonCVS, FTP, Rsync or HTTP, but
|
||||
people would not benefit from CVSup access.
|
||||
CVSup was developed by John Polstra <email>jdp@FreeBSD.org</email>.
|
||||
CVSup was developed by &a.jdp;.
|
||||
It is a bit tricky to install on non-FreeBSD platforms,
|
||||
since it is written in Modula-3 and therefore requires
|
||||
a Modula-3 environmen. John Polstra has built a
|
||||
|
@ -306,8 +308,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
|
|||
<programlisting>
|
||||
/dev/da0s1b /anoncvstmp mfs rw,-s=786432,-b=4096,-f=512,-i=560,-c=3,-m=0,nosuid,nodev 0 0
|
||||
</programlisting>
|
||||
This is (of course) tuned a lot, and was suggested by John Polstra
|
||||
<email>jdp@freebsd.org</email>.
|
||||
This is (of course) tuned a lot, and was suggested by &a.jdp;.
|
||||
</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
@ -718,7 +719,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
|
|||
mirror, this certainly helps you getting access.
|
||||
In any other case make sure your country really needs another mirror.
|
||||
If it already has three or more, ask
|
||||
<email>freebsd-hubs@FreeBSD.org</email> first.
|
||||
the &a.hubs; first.
|
||||
</para>
|
||||
<para>
|
||||
There are just two master sites, for the FTP fileset and
|
||||
|
@ -745,7 +746,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
|
|||
</para>
|
||||
<para>
|
||||
To get access to <hostid>ftp-master.FreeBSD.org</hostid>,
|
||||
you need to contact Peter Wemm <email>peter@freebsd.org</email>
|
||||
you need to contact &a.peter;.
|
||||
</para>
|
||||
</sect4>
|
||||
<sect4 id="mirror-where-master-cvsup">
|
||||
|
@ -760,7 +761,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
|
|||
</para>
|
||||
<para>
|
||||
To get access, you need to contact
|
||||
John Polstra <email>jdp@freebsd.org</email>.
|
||||
&a.jdp;.
|
||||
Make sure you read
|
||||
<ulink url="http://people.freebsd.org/~jdp/cvsup-access/">FreeBSD CVSup Access Policy</ulink>
|
||||
first!
|
||||
|
@ -830,7 +831,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
|
|||
</itemizedlist>
|
||||
|
||||
Furthermore, admins should be subscribed to
|
||||
<email>freebsd-hubs@freebsd.org</email>.
|
||||
the &a.hubs;.
|
||||
See <ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL">this link</ulink> for details, how to subscribe.
|
||||
</para>
|
||||
<important>
|
||||
|
@ -861,7 +862,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
|
|||
<para>
|
||||
Before applying, please consider (again) if
|
||||
another official mirror is really needed for
|
||||
your region. Ask on <email>freebsd-hubs@FreeBSD.org</email>,
|
||||
your region. Ask on the &a.hubs;,
|
||||
if in doubt.
|
||||
</para>
|
||||
<para>Ok, here is how to do it:</para>
|
||||
|
@ -874,7 +875,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
|
|||
</step>
|
||||
<step>
|
||||
<para>
|
||||
<ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL">Subscribe</ulink> to <email>freebsd-hubs@freebsd.org</email>.
|
||||
<ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL">Subscribe</ulink> to the &a.hubs;.
|
||||
</para>
|
||||
</step>
|
||||
<step>
|
||||
|
@ -891,14 +892,14 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
|
|||
If there is no subdomain delegated, yet, for your
|
||||
country, you probably need to contact
|
||||
<email>hostmaster@freebsd.org</email>,
|
||||
however, you can try <email>freebsd-hubs@freebsd.org</email>
|
||||
however, you can try the &a.hubs;
|
||||
first.
|
||||
</para>
|
||||
</step>
|
||||
<step>
|
||||
<para>
|
||||
Then you can ask <email>freebsd-doc@freebsd.org</email>, or
|
||||
<email>freebsd-hubs@freebsd.org</email> to add your mirror site to
|
||||
Then you can ask the &a.doc;, or
|
||||
the &a.hubs; to add your mirror site to
|
||||
the mirror list in the <ulink url="http://www.freebsd.org/handbook">FreeBSD
|
||||
Handbook</ulink>. Make sure you tell them the email address,
|
||||
to list as the maintainer of the site.
|
||||
|
|
|
@ -4,6 +4,8 @@
|
|||
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
|
||||
%man;
|
||||
<!ENTITY % mailing-lists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
|
||||
%mailing-lists;
|
||||
]>
|
||||
|
||||
<article>
|
||||
|
@ -655,7 +657,7 @@
|
|||
<command>/sbin/dmesg</command> is the boot log record, and it is
|
||||
useful to understand it because it shows what FreeBSD found when
|
||||
it booted up. If you ask questions on
|
||||
<email>freebsd-questions@FreeBSD.org</email> or on a USENET
|
||||
the &a.questions; or on a USENET
|
||||
group—like <quote>FreeBSD is not finding my tape drive,
|
||||
what do I do?</quote>—people will want to know what
|
||||
<command>dmesg</command> has to say.</para>
|
||||
|
|
|
@ -5,6 +5,8 @@
|
|||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
|
||||
%man;
|
||||
<!ENTITY % teams PUBLIC "-//FreeBSD//ENTITIES DocBook Team Entities//EN">
|
||||
%teams;
|
||||
<!ENTITY % freebsd PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
|
||||
%freebsd;
|
||||
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
|
||||
|
@ -56,8 +58,8 @@
|
|||
|
||||
<para>The <ulink url="http://www.FreeBSD.org/ports">FreeBSD Ports
|
||||
collection</ulink> is a collection of over &os.numports;
|
||||
third-party software packages available for FreeBSD. The ports
|
||||
team (portmgr@FreeBSD.org) is responsible for maintaining a
|
||||
third-party software packages available for FreeBSD. The &a.portmgr;
|
||||
is responsible for maintaining a
|
||||
consistent ports tree that can be used to create the binary
|
||||
packages that accompany a given FreeBSD release.</para>
|
||||
|
||||
|
|
|
@ -4,6 +4,12 @@
|
|||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY branches.ascii SYSTEM "branches.ascii">
|
||||
<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
|
||||
%authors;
|
||||
<!ENTITY % teams PUBLIC "-//FreeBSD//ENTITIES DocBook Team Entities//EN">
|
||||
%teams;
|
||||
<!ENTITY % mailing-lists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
|
||||
%mailing-lists;
|
||||
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
|
||||
%man;
|
||||
<!ENTITY % freebsd PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
|
||||
|
@ -116,8 +122,8 @@
|
|||
interface provided at <ulink
|
||||
url="http://www.FreeBSD.org/send-pr.html"></ulink>
|
||||
In addition to the multitude of different technical mailing lists
|
||||
about FreeBSD, the FreeBSD quality-assurance mailing list
|
||||
(freebsd-qa@FreeBSD.org) provides a forum for discussing the finer
|
||||
about FreeBSD, the &a.qa;
|
||||
provides a forum for discussing the finer
|
||||
points of <quote>release-polishing</quote>.</para>
|
||||
|
||||
<para>To service our most conservative users, individual release
|
||||
|
@ -163,7 +169,7 @@
|
|||
<para>Thirty days before the anticipated release, the source
|
||||
repository enters a <quote>code slush</quote>. During this
|
||||
time, all commits to the -STABLE branch must be approved by the
|
||||
release engineers (re@FreeBSD.org). The kinds of changes that
|
||||
&a.re;. The kinds of changes that
|
||||
are allowed during this 15 day period include:</para>
|
||||
|
||||
<itemizedlist>
|
||||
|
@ -573,8 +579,8 @@
|
|||
|
||||
<para>The <ulink url="http://www.FreeBSD.org/ports">FreeBSD Ports
|
||||
collection</ulink> is a collection of over &os.numports;
|
||||
third-party software packages available for FreeBSD. The ports
|
||||
team (portmgr@FreeBSD.org) is responsible for maintaining a
|
||||
third-party software packages available for FreeBSD. The &a.portmgr;
|
||||
is responsible for maintaining a
|
||||
consistent ports tree that can be used to create the binary
|
||||
packages that accompany official FreeBSD releases.</para>
|
||||
|
||||
|
@ -745,14 +751,13 @@
|
|||
<para>The release engineering process for 4.4 formally began on
|
||||
August 1st, 2001. After that date all commits to the
|
||||
<literal>RELENG_4</literal> branch of FreeBSD had to be explicitly
|
||||
approved by <ulink
|
||||
url="mailto:re@FreeBSD.org">re@FreeBSD.org</ulink>. The first
|
||||
approved by the &a.re;. The first
|
||||
release candidate for the x86 architecture was released on August
|
||||
16, followed by 4 more release candidates leading up to the final
|
||||
release on September 18th. The security officer was very involved
|
||||
in the last week of the process as several security issues were
|
||||
found in the earlier release candidates. A total of over
|
||||
<emphasis>500</emphasis> emails were sent to re@FreeBSD.org in
|
||||
<emphasis>500</emphasis> emails were sent to the &a.re; in
|
||||
little over a month.</para>
|
||||
|
||||
<para>Our user community has made it very clear that the security
|
||||
|
@ -822,17 +827,10 @@
|
|||
responsibilities for FreeBSD 4.4 and also for all of his work
|
||||
throughout the years making FreeBSD what it is today. Of course
|
||||
the release wouldn't have been possible without all of the
|
||||
release-related work done by <ulink
|
||||
url="mailto:asami@FreeBSD.org">Satoshi Asami</ulink>, <ulink
|
||||
url="mailto:steve@FreeBSD.org">Steve Price</ulink>, <ulink
|
||||
url="mailto:bmah@FreeBSD.org">Bruce Mah</ulink>, <ulink
|
||||
url="mailto:nik@FreeBSD.org">Nik Clayton</ulink>, <ulink
|
||||
url="mailto:obrien@FreeBSD.org">David O'Brien</ulink>, <ulink
|
||||
url="mailto:kris@FreeBSD.org">Kris Kennaway</ulink>, <ulink
|
||||
url="mailto:jhb@FreeBSD.org">John Baldwin</ulink>, and the rest of
|
||||
release-related work done by &a.asami;, &a.steve;, &a.bmah;, &a.nik;,
|
||||
&a.obrien;, &a.kris;, &a.jhb; and the rest of
|
||||
the FreeBSD development community. I would also like to thank
|
||||
<ulink url="mailto:rgrimes@FreeBSD.org">Rod Grimes</ulink>, <ulink
|
||||
url="mailto:phk@FreeBSD.org">Poul-Henning Kamp</ulink>, and others
|
||||
&a.rgrimes;, &a.phk;, and others
|
||||
who worked on the release engineering tools in the very early days
|
||||
of FreeBSD. This article was influenced by release engineering
|
||||
documents from the CSRG[14], the NetBSD Project[11], and John
|
||||
|
|
Loading…
Reference in a new issue