Go to http://www.jboss.org/forums and then open up the TODO forum. Plenty TODO!
I am working on the log.debug() messages, but have not started with the Unifed Deployer stuff. Perhaps you could take a look at it. Scott Sanders > -----Original Message----- > From: Rhett Aultman [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 02, 2002 7:49 AM > To: [EMAIL PROTECTED] > Subject: [JBoss-dev] I'd really like to help, but... > > > At the risk of sounding like an absolute newbie (and inviting > all sorts of nasty responses), I wanted to ask the people in > here if maybe they could help get me pointed in the right > direction. My employer is considering the use of JBoss as > our EJB container, and I felt that this would be the ideal > time to start my education in J2EE infrastructure that I was > going to put off until graduate school. I also have wanted > to be able to contribute meaningfully to an open source > project for a while now, and JBoss is definitely one with > sufficient momentum that I can be a contributor without fear > of having to become the sole supporter/developer/maintainer. > > I'm no slouch with my Java programming (or, at least, I don't > think I am), and I've even written container systems for some > of my own development projects, so I think I may have the > kind of mind that would be useful as a JBoss coder. I've > also set up development environments on my Win2K and Sun > machines at home that I refresh with the nightly snapshots. > I'm pretty familiar with JBoss, I've read the docs, and I'm > digging through the API documentation as needed. I'm > starting to feel like I'm actually ready to contribute in some way. > > The thing is...I don't know exactly where I might be needed. > I know that to get RW access to the CVS tree I have to first > submit three patches that get accepted. Where can I go > hunting for bugs to patch, though? Almost all of the bugs I > saw on the JBoss Sourceforge page have patches in the > "patches" section already or have been assigned to an active > project member. Is there somewhere else that some fresh meat > would be needed? I have noticed that there are failures and > errors when the test suite is run. Are people needed to try > and bring the RabbitHole alpha up to snuff with its test > suite, or is test suite compliance the sole responsibility of > the core development team? > > Like I said, I'm eager to join in, and I think I may have > skills to contribute, but I just am unsure as to where I > actually can help. Could one of the more seasoned project > members maybe give me some ideas? Alternately, if you're > pretty much full up on developers or just don't need another > rookie, I'd be happy to hear it. At least I'd know I'm > barking up the wrong tree. > > I eagerly await any advice/comments/flames. > > -- > J. Rhett Aultman > Business Technology Solutions > FCCI Insurance Group > > > _______________________________________________ > Jboss-development mailing list [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
