husted 02/01/23 12:35:43
Modified: docs/site getinvolved.html
Added: docs/site contributing.html
Log:
Put Craig's piece about contributing into a file, so we don't have to link into a
mail archive.
Revision Changes Path
1.36 +23 -9 jakarta-site2/docs/site/getinvolved.html
Index: getinvolved.html
===================================================================
RCS file: /home/cvs/jakarta-site2/docs/site/getinvolved.html,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- getinvolved.html 19 Jan 2002 13:15:35 -0000 1.35
+++ getinvolved.html 23 Jan 2002 20:35:43 -0000 1.36
@@ -151,32 +151,46 @@
There are a variety of ways to participate. Regardless of how you
choose to participate, we suggest you join some or all of our <a
href="./mail.html">mailing lists</a>.
</p>
- <p><strong>Use the Products and
Give Us Feedback</strong><br />
+ <p>
+<strong>Use the Products and Give Us Feedback</strong><br />
Using the products, reporting bugs, making feature requests, et cetera, is by
far the most important role. It's your feedback that allows the
technology to evolve.
</p>
- <ul><li><a href="./mail.html">Join
Mailing Lists</a></li><li><a href="./binindex.html">Download Binary
Builds</a></li><li><a href="./bugs.html">Report bugs/Request additional
features</a></li></ul>
- <p><strong>Contribute Code or
Documentation Patches</strong><br />
+ <ul>
+<li><a href="./mail.html">Join Mailing Lists</a></li>
+<li><a href="./binindex.html">Download Binary Builds</a></li>
+<li><a href="./bugs.html">Report bugs/Request additional features</a></li>
+</ul>
+ <p>
+<strong>Contribute Code or Documentation Patches</strong><br />
In this role, you participate in the actual development of the code.
If this is the type of role you'd like to play, here are some steps
(in addition to the ones above) to get you started:
</p>
- <ul><li><a
href="./guidelines.html">Read Guidelines</a></li><li><a href="./library.html">Review
Reference Library</a></li><li><a href="./sourceindex.html">Download the Source
Code</a></li><li><a href="./cvsindex.html">Access CVS Repository</a></li></ul>
+ <ul>
+<li><a href="./guidelines.html">Read Guidelines</a></li>
+<li><a href="./library.html">Review Reference Library</a></li>
+<li><a href="./sourceindex.html">Download the Source Code</a></li>
+<li><a href="./cvsindex.html">Access CVS Repository</a></li>
+</ul>
<p>
Here is one developer's advice how to get involved. It specifically
talks about Tomcat, but the general idea can applied to any of the
-Jakarta projects.
+Jakarta subprojects.
</p>
- <ul><li><a
href="http://w4.metronet.com/~wjm/tomcat/2000/Nov/msg00073.html";>Getting
-Involved</a> -- Craig R. McClanahan</li></ul>
+ <ul>
+<li><a href="contributing.html">Contributing</a> -- Craig R. McClanahan</li>
+</ul>
<p>
Here is another comment that was sent to the Turbine Mailing List about the
opensource process and the contrast between how an opensource product
and a proprietary product improve through the user community.
</p>
- <ul><li><a
href="./understandingopensource.html">Understanding
-Opensource</a> -- Cameron Riley</li></ul>
+ <ul>
+<li><a href="./understandingopensource.html">Understanding
+Opensource</a> -- Cameron Riley</li>
+</ul>
</blockquote>
</p>
</td></tr>
1.1 jakarta-site2/docs/site/contributing.html
Index: contributing.html
===================================================================
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<!-- Content Stylesheet for Site -->
<!-- start the processing -->
<!-- ====================================================================== -->
<!-- Main Page Section -->
<!-- ====================================================================== -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<meta name="author" value="Craig
R. McClanahan">
<meta name="email" value="[EMAIL PROTECTED]">
<title>The Jakarta Site - Contributing</title>
</head>
<body bgcolor="#ffffff" text="#000000" link="#525D76">
<table border="0" width="100%" cellspacing="0">
<!-- TOP IMAGE -->
<tr>
<td colspan="2">
<a href="http://jakarta.apache.org";><img
src="http://jakarta.apache.org/images/jakarta-logo.gif"; align="left" border="0"/></a>
</td>
</tr>
</table>
<table border="0" width="100%" cellspacing="4">
<tr><td colspan="2">
<hr noshade="" size="1"/>
</td></tr>
<tr>
<!-- LEFT SIDE NAVIGATION -->
<td width="20%" valign="top" nowrap="true">
<p><strong>Essentials</strong></p>
<ul>
<li> <a href="../index.html">Front Page</a>
</li>
<li> <a href="http://jakarta.apache.org/site/news.html";>News
& Status</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/mission.html";>Mission</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/guidelines.html";>Guidelines Notes</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/faqs.html";>FAQs</a>
</li>
<li> <a href="../gump">Gump</a>
</li>
<li> <a href="http://search.apache.org/";>Search Apache
Sites</a>
</li>
</ul>
<p><strong>Download</strong></p>
<ul>
<li> <a
href="http://jakarta.apache.org/site/binindex.html";>Binaries</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/sourceindex.html";>Source Code</a>
</li>
</ul>
<p><strong>Get Involved</strong></p>
<ul>
<li> <a
href="http://jakarta.apache.org/site/getinvolved.html";>Overview</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/cvsindex.html";>CVS Repositories</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/mail.html";>Mailing Lists</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/library.html";>Reference Library</a>
</li>
<li> <a href="http://jakarta.apache.org/site/bugs.html";>Bug
Database</a>
</li>
</ul>
<p><strong>SubProjects</strong></p>
<ul>
<li> <a href="../alexandria/index.html">Alexandria</a>
</li>
<li> <a href="../ant/index.html">Ant</a>
</li>
<li> <a href="../avalon/index.html">Avalon</a>
</li>
<li> <a href="../bcel/index.html">BCEL</a>
</li>
<li> <a href="../cactus/index.html">Cactus</a>
</li>
<li> <a href="../commons/index.html">Commons</a>
</li>
<li> <a href="../ecs/index.html">ECS</a>
</li>
<li> <a href="../james/index.html">James</a>
</li>
<li> <a href="../jetspeed/index.html">Jetspeed</a>
</li>
<li> <a href="../jmeter/index.html">JMeter</a>
</li>
<li> <a href="../log4j/index.html">Log4J</a>
</li>
<li> <a href="../lucene/index.html">Lucene</a>
</li>
<li> <a href="../oro/index.html">ORO</a>
</li>
<li> <a href="../regexp/index.html">Regexp</a>
</li>
<li> <a href="../slide/index.html">Slide</a>
</li>
<li> <a href="../struts/index.html">Struts</a>
</li>
<li> <a href="../taglibs/index.html">Taglibs</a>
</li>
<li> <a href="../tomcat/index.html">Tomcat</a>
</li>
<li> <a href="../turbine/index.html">Turbine</a>
</li>
<li> <a href="../velocity/index.html">Velocity</a>
</li>
<li> <a href="../watchdog/index.html">Watchdog</a>
</li>
</ul>
<p><strong>Misc</strong></p>
<ul>
<li> <a
href="http://jakarta.apache.org/site/whoweare.html";>Who We Are</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/acknowledgements.html";>Acknowledgements</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/roles.html";>Management</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/jakarta-site2.html";>About This Site</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/contact.html";>Contact</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/legal.html";>Legal</a>
</li>
</ul>
</td>
<td width="80%" align="left" valign="top">
<table
border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="Contributing"><strong>Contributing</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p><i>This was originally posted on the Tomcat
DEV list,
but applies equally well to any Jakarta subproject.</i></p>
<pre>
Michael Percy wrote:
> I believe there would be (or at least SHOULD be! :) many
> more contributors to these projects (Tomcat), but maybe
> some of us are intimidated by the level of apparent
> expertise required for this stuff. (Then again, I know
> we have some damn good people on these lists.) I am
> curious, is this the case? Have you all been writing
> java apps for years and are steeped in C++ and OOP for
> the last decade? Do you have the servlet spec pasted on
> your wall?
</pre>
<p>
Michael,
</p>
<p>
In my particular case the servlet spec is pasted on the inside of my eyeballs
:-) But I'm kind of a wierd case in that respect, because I'm on the JSR-053
expert group that worked on the new specs (servlet 2.3 / JSP 1.2).
</p>
<p>
Personally, I've been a software developer/designer/architect in some fashion or
another for more years (and in more languages) than I care to admit. But I got
involved in the Apache JServ project (predecessor to Tomcat) a few years ago
when I needed a cheap server solution for an Internet-based application that I
needed to build. Like everyone, I was grumbling about how long it took for
JServ to get to final release (over a year from 0.9 to 1.0), until my son -- who
likes PHP but I love him anyway :-) -- said "Dad, you know Java, get in there
and help them finish it!". So I did.
</p>
<p>
I wouldn't worry to much about expertise (although clearly Java is a must, and
familiarty with the specifications that Tomcat implements -- servlet, JSP, HTTP,
etc. -- is vital on this particular project). The ways that people get involved
in open source are pretty varied, but a common course might go something like
this:
</p>
<ul>
<li>
You see something that you think should be
added, or that doesn't seem to work quite right
</li>
<li>
You investigate the existing code, becoming more
familiar with it along the way
</li>
<li>
You might ask a "what would you think if we did this?"
type question on the developer list
</li>
<li>
You contribute to the discussion of these ideas
(yours and others) - partly to gain knowledge but also
partly to become known to the community
</li>
<li>
At some point, you propose a patch, or a new chunk
of code that gets accepted into the code base (the
detailed rules for Tomcat are on the Jakarta web site)
</li>
<li>
Iterate the above a few times, perhaps looking at bigger
and bigger chunks of code as you gain more understanding
</li>
<li>
At some point, when it is evident that you're not a bozo :-),
you can get nominated for committer status and voted on
by the developer community, and then be able to post the
changes directly yourself.
</li>
</ul>
<pre>
> How can I, a perl hacker and aspiring java coder get
> involved? (How do you guys know what to do?) At what
> point would I be considered to be "good enough" to
> really contribute some code? Server-side java simply
> rocks, and if I could help make it a more viable
> option for everyone (including myself and my company)
> then I would love to do it.
</pre>
<p>
It all starts by becoming familiar enough with the current code base to start
understanding it. In most open source projects there is never enough
architectural documentation, so this often involves asking "how does this work"
type questions on the developer list. Don't feel bad about that -- NONE of us
knew anything about Tomcat internals before we started working on it :-)
</p>
<pre>
> Hope this isn't a totally inane question, but it has
> been on my mind for a couple weeks. Just wondering...
</pre>
<p>
Not at all inane -- I hope the above thoughts help.
</p>
<pre>
> Thanks,
> Mike
</pre>
<p>
Craig
</p>
<p>
03 Nov 2000
</p>
</blockquote>
</p>
</td></tr>
<tr><td><br/></td></tr>
</table>
</td>
</tr>
<!-- FOOTER -->
<tr><td colspan="2">
<hr noshade="" size="1"/>
</td></tr>
<tr><td colspan="2">
<div align="center"><font color="#525D76" size="-1"><em>
Copyright © 1999-2002, Apache Software Foundation
</em></font></div>
</td></tr>
</table>
</body>
</html>
<!-- end the processing -->
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
![http://jakarta.apache.org/images/jakarta-logo.gif"](http://jakarta.apache.org/images/jakarta-logo.gif"){kind=link}