aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/articles/contributing/article.sgml
diff options
context:
space:
mode:
authorMarc Fonvieille <blackend@FreeBSD.org>2002-08-03 18:59:36 +0000
committerMarc Fonvieille <blackend@FreeBSD.org>2002-08-03 18:59:36 +0000
commita3a6aa326d89bfb70aab3a2c787f99f6e6243968 (patch)
tree876cdf35fca48f3c6dfc1cd40878393562f8a40c /en_US.ISO8859-1/articles/contributing/article.sgml
parent07b2f1f6c66df12b10fced8e877116b3e810782b (diff)
downloaddoc-a3a6aa326d89bfb70aab3a2c787f99f6e6243968.tar.gz
doc-a3a6aa326d89bfb70aab3a2c787f99f6e6243968.zip
Mailing lists entities addition.
Some punctuation and style corrections. Use of manual pages entities. Fix an old remain when that article was part of the Handbook and talked about "FreeBSD Inc.", it's "FreeBSD Foundation" now.
Notes
Notes: svn path=/head/; revision=13775
Diffstat (limited to 'en_US.ISO8859-1/articles/contributing/article.sgml')
-rw-r--r--en_US.ISO8859-1/articles/contributing/article.sgml40
1 files changed, 20 insertions, 20 deletions
diff --git a/en_US.ISO8859-1/articles/contributing/article.sgml b/en_US.ISO8859-1/articles/contributing/article.sgml
index c3bce09c75..aa97af62a4 100644
--- a/en_US.ISO8859-1/articles/contributing/article.sgml
+++ b/en_US.ISO8859-1/articles/contributing/article.sgml
@@ -107,7 +107,7 @@ FreeBSD Entities//EN"> %freebsd;
</listitem>
<listitem>
- <para>Read the freebsd-questions mailing list and &ng.misc;
+ <para>Read the &a.questions; and &ng.misc;
occasionally (or even regularly). It can be very
satisfying to share your expertise and help people solve
their problems; sometimes you may even learn something new
@@ -119,14 +119,14 @@ FreeBSD Entities//EN"> %freebsd;
<sect2 id="ongoing-programmer-tasks">
<title>Ongoing Programmer Tasks</title>
- <para>Most of the tasks listed here require a considerable
- investment of time, an in-depth knowledge of the FreeBSD
+ <para>Most of the tasks listed here require either a considerable
+ investment of time, or an in-depth knowledge of the FreeBSD
kernel, or both. However, there are also many useful tasks
which are suitable for <quote>weekend hackers</quote>.</para>
<orderedlist>
<listitem>
- <para>If you run FreeBSD-current and have a good Internet
+ <para>If you run FreeBSD-CURRENT and have a good Internet
connection, there is a machine <hostid
role="fqdn">current.FreeBSD.org</hostid> which builds a
full release once a day&mdash;every now and again, try to
@@ -135,7 +135,7 @@ FreeBSD Entities//EN"> %freebsd;
</listitem>
<listitem>
- <para>Read the freebsd-bugs mailing list. There might be a
+ <para>Read the &a.bugs;. There might be a
problem you can comment constructively on or with patches
you can test. Or you could even try to fix one of the
problems yourself.</para>
@@ -143,8 +143,8 @@ FreeBSD Entities//EN"> %freebsd;
<listitem>
<para>If you know of any bug fixes which have been
- successfully applied to -current but have not been merged
- into -stable after a decent interval (normally a couple of
+ successfully applied to -CURRENT but have not been merged
+ into -STABLE after a decent interval (normally a couple of
weeks), send the committer a polite reminder.</para>
</listitem>
@@ -172,8 +172,8 @@ FreeBSD Entities//EN"> %freebsd;
<listitem>
<para>If you have contributed any ports, send your patches
- back to the original author (this will make your life
- easier when they bring out the next version)</para>
+ back to the original authors (this will make your life
+ easier when they bring out the next version).</para>
</listitem>
<listitem>
@@ -235,7 +235,7 @@ FreeBSD Entities//EN"> %freebsd;
technical interest should be mailed to the &a.hackers;.
Likewise, people with an interest in such things (and a
tolerance for a <emphasis>high</emphasis> volume of mail!) may
- subscribe to the hackers mailing list by sending mail to
+ subscribe to the &a.hackers; by sending mail to
&a.majordomo;. See <ulink
url="../../books/handbook/eresources.html#ERESOURCES-MAIL">The
FreeBSD Handbook</ulink> for more information about this and
@@ -284,7 +284,7 @@ FreeBSD Entities//EN"> %freebsd;
url="../../books/fdp-primer/index.html">FreeBSD Documentation
Project Primer</ulink> for complete instructions. Send
submissions and changes (even small ones are welcome!) using
- <command>send-pr</command> as described in <link
+ &man.send-pr.1; as described in <link
linkend="contrib-general">Bug Reports and General
Commentary</link>.</para>
</sect2>
@@ -292,18 +292,18 @@ FreeBSD Entities//EN"> %freebsd;
<sect2>
<title>Changes to Existing Source Code</title>
- <indexterm><primary>FreeBSD-current</primary></indexterm>
+ <indexterm><primary>FreeBSD-CURRENT</primary></indexterm>
<para>An addition or change to the existing source code is a
somewhat trickier affair and depends a lot on how far out of
date you are with the current state of FreeBSD
development. There is a special on-going release of FreeBSD
- known as <quote>FreeBSD-current</quote> which is made
+ known as <quote>FreeBSD-CURRENT</quote> which is made
available in a variety of ways for the convenience of
developers working actively on the system. See <ulink url="
../../books/handbook/current-stable.html">The FreeBSD
Handbook</ulink> for more information about getting and using
- FreeBSD-current.</para>
+ FreeBSD-CURRENT.</para>
<para>Working from older sources unfortunately means that your
changes may sometimes be too obsolete or too divergent for
@@ -376,12 +376,12 @@ FreeBSD Entities//EN"> %freebsd;
distribution or you are simply not ready to release it without
a tighter review first, then you should send it to &a.core;
directly rather than submitting it with &man.send-pr.1;. The
- core mailing list reaches a much smaller group of people who
+ &a.core; reaches a much smaller group of people who
do much of the day-to-day work on FreeBSD. Note that this
group is also <emphasis>very busy</emphasis> and so you should
only send mail to them where it is truly necessary.</para>
- <para>Please refer to &man.intro.9; and &man.style.9; style for
+ <para>Please refer to &man.intro.9; and &man.style.9; for
some information on coding style. We would appreciate it if
you were at least aware of this information before submitting
code.</para>
@@ -443,7 +443,7 @@ FreeBSD Entities//EN"> %freebsd;
work, include the following text at the very beginning of
every source code file you wish to protect, replacing the text
between the <literal>%%</literal> with the appropriate
- information.</para>
+ information:</para>
<programlisting>Copyright (c) %%proper_years_here%%
%%your_name_here%%, %%your_state%% %%your_zip%%.
@@ -530,9 +530,9 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<itemizedlist>
<listitem>
<para>General purpose hardware such as disk drives, memory
- or complete systems should be sent to the FreeBSD,
- Inc. address listed in the <emphasis>donating
- funds</emphasis> section.</para>
+ or complete systems should be sent to the FreeBSD
+ Foundation address listed in the <link linkend="donations">donating
+ funds</link> section.</para>
</listitem>
<listitem>