Craig,
     Thanks alot for the reply.  This is exactly the type of information 
I was looking for.  I am familiar with CVS, so no problems there.

Thanks again,
Bill

Craig R. McClanahan wrote:

> 
> On Thu, 23 Aug 2001, Bill Clinton wrote:
> 
> 
>> Date: Thu, 23 Aug 2001 15:58:37 -0400
>> From: Bill Clinton <[EMAIL PROTECTED]>
>> Reply-To: [EMAIL PROTECTED]
>> To: struts-dev <[EMAIL PROTECTED]>
>> Subject: Help Wanted?
>> 
>> Hello,
>>      I have been using struts for a little while now, and I really like
>> it.  I have had to delve into the source code occasionally and I think I
>> have a fairly good idea of the struts concepts.
>> 
>>      I would like to partipate in the project.  I am wondering if you
>> guys have some sort of list of smaller tasks that need to be done for
>> people like myself, who want to get involved but don't want to come in
>> and try to rewrite the whole thing.  I guess I am looking for a way to
>> "pay my dues" and prove myself as someone who can contribute while still
>> doing something useful for the project.
>> 
>> Thanks for any info,
>> Bill
>> 
>> 
> 
> 
> Hi Bill, and welcome to Struts ...
> 
> There is a TODO list included in the documentation app, which is somewhat
> out of date, but still an interesting base for new development.  Another
> way for people to get involved would be to look at the outstanding bug
> reports, investigate and fix them, and propose patches.  You can find the
> list at:
> 
>   http://nagoya.apache.org/bugzilla/
> 
> under product category "Struts".
> 
> One important thing to review when looking at bug reports is whether the
> bug occurs in the Struts 1.0 final release, or in the current nightly
> builds.  The source code has (of course) evolved since 1.0, so you need to
> make sure you're patching against the correct version.
> 
> With CVS, it's pretty easy to keep both source trees checked out in
> separate directories.  If you're not familiar with CVS, check the Jakarta
> web site for the tools you need (http://jakarta.apache.org) and at sites
> like <www.cvshome.org> for general CVS documentation.
> 
> Craig

Reply via email to