Add an additional section with a task for interested contributors;

"Work through the PR database".

Prompted by Doug <Doug@gorean.org>, who in an e-mail to an interested
contributor in -hackers wrote;

On Sun, Jul 18, 1999 at 12:01:43PM -0700, Doug wrote:
[...]
> Step three, (and I can't believe this isn't mentioned in the handbook) if
> there isn't anything on that page that looks interesting to you, take a
> look at http://www.freebsd.org/cgi/query-pr-summary.cgi and see if
> anything there strikes your fancy. Look first at unsassigned PR's, but
> if one of them that is assigned to someone looks like something you can
> handle and have time to work on, mail the person it's assigned to and
> ask them about it.
[...]

So now it is mentioned in the Handbook :-)
This commit is contained in:
Nik Clayton 1999-07-30 20:59:55 +00:00
parent 6c26cf33ae
commit 49c64cab8f
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=5280
4 changed files with 80 additions and 4 deletions

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: chapter.sgml,v 1.75 1999-07-28 20:23:17 nik Exp $
$Id: chapter.sgml,v 1.76 1999-07-30 20:59:55 nik Exp $
-->
<chapter id="contrib">
@ -408,6 +408,25 @@
</listitem>
</orderedlist>
</sect2>
<sect2>
<title>Work through the PR database</title>
<para>The <ulink
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.
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
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>
<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
you can handle, e-mail 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>
</sect2>
</sect1>
<sect1>