old-www/LDP/LG/issue44/severinghaus.html

89 lines
3.5 KiB
HTML

<!--startcut ==========================================================-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<title>TitleOfArticle LG #44</title>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#0000AF"
ALINK="#FF0000">
<!--endcut ============================================================-->
<H4>
"Linux Gazette...<I>making Linux just a little more fun!</I>"
</H4>
<P> <HR> <P>
<!--===================================================================-->
<center>
<H1><font color="maroon">
Other ways to join and contribute to the Open Source community</font></H1>
<H4>By <a href="mailto:eriksev@linuxdev.net">Erik Severinghaus</a></H4>
</center>
<P> <HR> <P>
Though Linux, is/was/always-will-be a hackers OS, there are lots of guys that
couldn't hack the kernel to save their life. There are however lots of other
badly needed areas which could use support.
<H1>Documentation</H1>
This is one of the most important, and ignored, areas of Linux. Lets face it,
coders don't ususally like to write documentation. Find a project you really
like (start w/ a small app or something) and see if you can write an easy way
to do the basic stuff, and then document the more advanced features. Have a
tough time figuring out how to do something? Chances are lots of other guys
are having the same problem. Write a HOWTO or Mini-HOWTO and submit it to the
<A HREF="http://metalab.unc.edu/linux">LDP</A>. There are tons of other
things that need documentation, and developers will love ya for it :).
<H1>Bug Testers</H1>
This is another thing that will make you a developers best friend. Take the
programs, push 'em to the limits, and make 'em break. If you can do something
to crash it, send a polite email to the author with your system specs, what
version of software, exactly what you did, and exactly what happened when it
crashed. Even better, do an strace if it seg faults and send the author the
results.
<H1>Packaging</H1>
Finding rpms and debs of the latest programs is tough to do. Reading some man
pages to learn the ins and outs of rpm and dpkg, and rolling generic .tgzs
into unofficial (or even better: official) packages is of great help to
everyone.
<H1>Advocacy</H1>
This can be very useful <I>if done correctly</I>. Dispelling the endless FUD
is always a Good Thing, but only if done in a polite and constructive manner
(completely free of profanity). Please, before you do this, read the
<A HREF="http://metalab.unc.edu/linux/HOWTO/mini/Advocacy.html">advocacy
HOWTO.</A>
<H1>Conclusion</H1>
These are just a few of the ways to help out and contribute to the Linux and
Open Source communities. Remember, finding something you enjoy doing will help
you do better work, and not get burned out.
<!--===================================================================-->
<P> <hr> <P>
<center><H5>Copyright &copy; 1999, Erik Severinghaus <BR>
Published in Issue 44 of <i>Linux Gazette</i>, August 1999</H5></center>
<!--===================================================================-->
<!--startcut ==========================================================-->
<P> <hr> <P>
<A HREF="./index.html"><IMG ALIGN=BOTTOM SRC="../gx/indexnew.gif"
ALT="[ TABLE OF CONTENTS ]"></A>
<A HREF="../index.html"><IMG ALIGN=BOTTOM SRC="../gx/homenew.gif"
ALT="[ FRONT PAGE ]"></A>
<A HREF="pollman/dns.html"><IMG SRC="../gx/back2.gif"
ALT=" Back "></A>
<A HREF="silva.html"><IMG SRC="../gx/fwd.gif" ALT=" Next "></A>
<P> <hr> <P>
</BODY>
</HTML>
<!--endcut ============================================================-->