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

Convert names, descriptions and e-mail addresses of FreeBSD committers

Browse source 
and mailing lists to SGML entities.

Reviewed by:	keramida
Approved by:	keramida, silence on -doc
This commit is contained in:
Peter Pentchev 2002-03-15 08:10:48 +00:00
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
Download patch file Download diff file Expand all files Collapse all files

34
en_US.ISO8859-1/articles/committers-guide/article.sgml
View file

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