From db46fb6953e91dff6d96bada0943d6b61d45e7a9 Mon Sep 17 00:00:00 2001 From: Michael Lucas Date: Tue, 7 May 2002 12:34:27 +0000 Subject: [PATCH] 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. --- .../articles/contributing/article.sgml | 86 +++++++++++-------- 1 file changed, 49 insertions(+), 37 deletions(-) diff --git a/en_US.ISO8859-1/articles/contributing/article.sgml b/en_US.ISO8859-1/articles/contributing/article.sgml index 0dd5bfcc3f..a606f4d68e 100644 --- a/en_US.ISO8859-1/articles/contributing/article.sgml +++ b/en_US.ISO8859-1/articles/contributing/article.sgml @@ -68,39 +68,19 @@ FreeBSD Entities//EN"> %freebsd; What Is Needed The following list of tasks and sub-projects represents something of - an amalgam of the various core team TODO 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? + an amalgam of various TODO lists and + user requests. - - Ongoing Tasks - - 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 weekend hackers, or people without - programming skills. + + Ongoing Non-Programmer Tasks + 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. + - - If you run FreeBSD-current and have a good Internet - connection, there is a machine current.FreeBSD.org which builds a full - release once a day—every now and again, try to install - the latest release from it and report any failures in the - process. - - - - 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. - - 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. + + + + + Ongoing Programmer Tasks + 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 weekend hackers. + + + + If you run FreeBSD-current and have a good Internet + connection, there is a machine current.FreeBSD.org which builds a full + release once a day—every now and again, try to install + the latest release from it and report any failures in the + process. + + + + 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. + 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 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. + PR is a good one. Others might be much more complex, or might not + even have a fix included at all. - 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 + 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—they might already have a patch ready to be tested, or further ideas that you can discuss with them. @@ -198,7 +206,7 @@ FreeBSD Entities//EN"> %freebsd; How to Contribute Contributions to the system generally fall into one or more of the - following 6 categories: + following 5 categories: Bug Reports and General Commentary @@ -246,7 +254,11 @@ FreeBSD Entities//EN"> %freebsd; Changes to the Documentation documentation submissions - Changes to the documentation are overseen by the &a.doc;. Send + Changes to the documentation are overseen by the &a.doc;. + Please look at the FreeBSD + Documentation Project Primer for complete instructions. + Send submissions and changes (even small ones are welcome!) using send-pr as described in Bug Reports and General @@ -259,7 +271,7 @@ FreeBSD Entities//EN"> %freebsd; FreeBSD-current 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 FreeBSD-current which is made available in a variety of ways for the convenience of developers working actively on the system. See