Reorganization and partial rewrite of this article.

Suggestions for to-do activities are now broken out into "coder" and
"non-coder" tasks.

Remove implications that the Core team makes all TODO lists.
This commit is contained in:
Michael Lucas 2002-05-07 12:34:27 +00:00
parent 1fed1d514c
commit db46fb6953
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=12997

View file

@ -68,39 +68,19 @@ FreeBSD Entities//EN"> %freebsd;
<title>What Is Needed</title>
<para>The following list of tasks and sub-projects represents something of
an amalgam of the various core team <filename>TODO</filename> lists and
user requests we have collected over the last couple of months. Where
possible, tasks have been ranked by degree of urgency. If you are
interested in working on one of the tasks you see here, send mail to the
coordinator listed by clicking on their names. If no coordinator has
been appointed, maybe you would like to volunteer?</para>
an amalgam of various <filename>TODO</filename> lists and
user requests.</para>
<sect2>
<title>Ongoing Tasks</title>
<para>Most of the tasks listed in the next sections 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>, or people without
programming skills.</para>
<sect2 id="non-programmer-tasks">
<title>Ongoing Non-Programmer Tasks</title>
<para>Many people who are involved in FreeBSD are not
programmers. The Project includes documentation writers, Web
designers, and support people. All that these people need to
contribute is an investment of time and a willingness to
learn.</para>
<orderedlist>
<listitem>
<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 install
the latest release from it and report any failures in the
process.</para>
</listitem>
<listitem>
<para>Read the freebsd-bugs mailing list. 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>
</listitem>
<listitem>
<para>Read through the FAQ and Handbook periodically. If anything
is badly explained, out of date or even just completely wrong, let
@ -132,6 +112,32 @@ FreeBSD Entities//EN"> %freebsd;
sometimes you may even learn something new yourself! These forums
can also be a source of ideas for things to work on.</para>
</listitem>
</orderedlist>
</sect2>
<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 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
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 install
the latest release from it and report any failures in the
process.</para>
</listitem>
<listitem>
<para>Read the freebsd-bugs mailing list. 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>
</listitem>
<listitem>
<para>If you know of any bug fixes which have been successfully
@ -181,13 +187,15 @@ FreeBSD Entities//EN"> %freebsd;
url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi">FreeBSD PR
list</ulink> shows all the current active problem reports and
requests for enhancement that have been submitted by FreeBSD users.
The PR database includes both programmer and non-programmer tasks.
Look through the open PRs, and see if anything there takes your
interest. Some of these might be very simple tasks, that just need an
interest. Some of these might be very simple tasks that just need an
extra pair of eyes to look over them and confirm that the fix in the
PR is a good one. Others might be much more complex.</para>
PR is a good one. Others might be much more complex, or might not
even have a fix included at all.</para>
<para>Start with the PRs that have not been assigned to anyone else, but
if one them is assigned to someone else, but it looks like something
<para>Start with the PRs that have not been assigned to anyone else.
If a PR is assigned to someone else, but it looks like something
you can handle, email the person it is assigned to and ask if you can
work on it&mdash;they might already have a patch ready to be tested,
or further ideas that you can discuss with them.</para>
@ -198,7 +206,7 @@ FreeBSD Entities//EN"> %freebsd;
<title>How to Contribute</title>
<para>Contributions to the system generally fall into one or more of the
following 6 categories:</para>
following 5 categories:</para>
<sect2 id="contrib-general">
<title>Bug Reports and General Commentary</title>
@ -246,7 +254,11 @@ FreeBSD Entities//EN"> %freebsd;
<title>Changes to the Documentation</title>
<indexterm><primary>documentation submissions</primary></indexterm>
<para>Changes to the documentation are overseen by the &a.doc;. Send
<para>Changes to the documentation are overseen by the &a.doc;.
Please look at the <ulink
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
linkend="contrib-general">Bug Reports and General
@ -259,7 +271,7 @@ FreeBSD Entities//EN"> %freebsd;
<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 the core FreeBSD development. There is a special
the current state of FreeBSD development. There is a special
on-going release of FreeBSD 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="