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

Add a non-guru section to "Contributing to FreeBSD"

Browse source 
Idea approved by:	jkh
This commit is contained in:
James Raynard 1997-12-20 22:35:08 +00:00
parent 8df42c0252
commit 59659782b0
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=2280
1 changed files with 61 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

62
handbook/submitters.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: submitters.sgml,v 1.135 1997-12-17 11:37:01 asami Exp $ -->
<!-- $Id: submitters.sgml,v 1.136 1997-12-20 22:35:08 jraynard Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Contributing to FreeBSD<label id="contrib"></heading>
@ -226,6 +226,66 @@ to "make regress" if that is all it is good for).
</enum>
<sect1><heading>Smaller tasks</heading>
<p>
Most of the tasks listed in the previous 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 &quot;weekend hackers&quot;, or people without programming
skills.
<enum>
<item>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 and install the latest release
from it and report any failures in the process.
<item>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.
<item>Read through the FAQ and Handbook periodically. If anything is
badly explained, out of date or even just completely wrong, let us
know. Even better, send us a fix (SGML is not difficult to learn, but
there is no objection to ASCII submissions).
<item>Help translate FreeBSD documentation into your native language (if
not already available) - just send an email to &a.doc asking if anyone is
working on it. Note that you are not committing yourself to translating
every single FreeBSD document by doing this - in fact, the documentation
most in need of translation is the installation instructions.
<item>Read the freebsd-questions mailing list and the newsgroup
comp.unix.bsd.freebsd.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 yourself! These
forums can also be a source of ideas for things to work on.
<item>If you know of any bugfixes which have been 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.
<item>Move contributed software to src/contrib in the source tree.
<item>Make sure code in src/contrib is up to date.
<item>Look for year 2000 bugs (and fix any you find!)
<item>Build the source tree (or just part of it) with extra warnings
enabled and clean up the warnings.
<item>Fix warnings for ports which do deprecated things like using
gets() or including malloc.h.
<item>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)
<item>Suggest further tasks for this list!
</enum>
<sect><heading>How to Contribute</heading>
<p>Contributions to the system generally fall into one or more of