Welcome! Patches are good. There's a task link on the maven site which serves as our 'to-do' list of sorts. The Overview->Reference->Musings link is sort of a 'big picture' type list. Stuff we don't want to forget that drives direction. The IRC channel is another place to knock around development questions.
================================================================= Jeffrey D. Brekke Quad/Graphics [EMAIL PROTECTED] http://www.qg.com > -----Original Message----- > From: Nathan Coast [mailto:[EMAIL PROTECTED]] > Sent: Friday, May 03, 2002 7:39 AM > To: [EMAIL PROTECTED] > Subject: getting involved > > > Hi all, > > I'm keen to get involved in maven dev. Have read all the > guidelines and they > suggest a good place to start is bug fixing or testing. > Should I find > unassigned issues in scarab and submit them via [Patch] to > this mail list? Are > there any particular issues that are higher priority than > others? Should I > assign issues to myself or is this something that only > committers should do? > > Maven's domain has been a pet project of mine for a while > now. I've been trying > to increase developer productivity by creating a project > framework. To enable > developers to focus on coding rather than worrying about all > of the fun things > like source control, documentation, coding standards, issue > tracking, auto > builds, status reporting, yadda yadda yadda. (sounds very > similar to some of the > maven intro docs) I can't believe I haven't stumbled accross > maven before now. > There's certainly plenty cool stuff in maven. I'm also too > lazy to find a job > at the moment and this seems more interesting than talking to agents. > > cheers Nathan >
