there's only a few more words i'd like to add to what the others have said.

i'd recommend starting by submitting documentation patches to the projects you're most interested in. not only are documentation patches very valuable but they are also an excellent way to learn the details of each component.

don't get discouraged if it takes a little time to get replies - we're all volunteers and quite often work on several different projects.

good luck!

- robert

On Thursday, August 7, 2003, at 09:35 AM, Eric Pugh wrote:

Jeff...

The approach you might take is to go through some of the commons projects
and look at the list of "todo" that some
maintain(http://jakarta.apache.org/commons/sandbox/configuration/tasks.html)
.  Then, submit patches that fix those problems.

You might also want to use a tool like clover and look at which commons
projects are light on testcases. Then provide tests to those projects.
Comprehensive testing, while a pain to do after the fact, is very important
to the long term success of any project.


Just to throw out something to look at, the Configuration project in the
sandbox has a couple things it would like. Something to start with that
wouldn't take too much time is a JDBCConfiguration that provided a
Configuration object backed by a database table. If you could provide
something like that (plus testcases!) I promise to look at the patches for
you.


As far as getting your own projects into Commons, to be granted karma you
have to be around a while so people get to know you and are confortably with
your approach to coding.


Sincerely,
Eric Pugh

-----Original Message-----
From: Jeff Epstein [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 5:44 AM
To: [EMAIL PROTECTED]
Subject: Three month contribution to Commons?


Hello there.


I am an MSIS student (Masters of Science, Information System) at Drexel
University, with five years professional experience under my belt
(mostly server-side Java and Oracle).

I have the opportunity to take a three month independent study (about
twenty hours a week, September through December), and, if you'll have
me, I would love to spend that time contributing something significant
to the Jakarta Commons project.

Is there something specific that you need, that I could start-and-finish
within this time?

As far as the Commons sub-projects that I'm familiar with, I'm
particularly interested in CLI and Lang (but am quite open to others).
I've been working on my own Lang-like project for six years now, XBN
Java.  I don't deny how much I have to learn--I'm not even sure anyone
else uses it--but XBN Java is one of my proudest accomplishments.  *I*
use it for everything I do.

I am reading the "how to contribute" articles spiced about the Jakarta
site, figuring out what I can.  Is there perhaps any specific advice on
how I might best pursue this with Commons?  I understand this would be
in an unofficial capacity, but I need to propose something concrete to
Drexel within the next three weeks.

(A thought:  Are there avenues towards getting one's own existing
modules/packages proposed and potentially/eventually implemented into
the Commons?)

Thanks very much.  Feel free to check out my resume or downloadable code
at my homepage, linked below.

:' )


===== :' )

Jeffy
[EMAIL PROTECTED]
http://www.jeffyjeffy.com

..

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to