Reading this the morning after, ;) I realize I wasn't clear that I intended to rebuke not the trolls, for in a Meritocracy they hold no standing, but existing committers and contributors. I'm afraid we have gotten lax in our commitment to digging into the code and moving the project forward. The Struts Action 1 situation in particular is disturbing considering how much attention and discussion it gets.

One of our big problems in the past is bugzilla tickets would be filed, patches added, and they'd be ignored for months, even years. I'm hoping this new JIRA instance and ticket work that is going on will help address that so that patches will be identified and applied sooner, and it will be easier for a prospective contributor to see what needs to be done and jump in. I think we've done a bad job of that in the past, and I'd like to change it.

So again, there is much to do and please do join the efforts. If there is something we can do to help make the project direction clearer, or highlight areas that need work, please let us know. These are the types of non-code discussions I feel are appropriate for this list as their end result is more commits and technical involvement.

Don

Don Brown wrote:
How Struts adds committers isn't "fair" - code quality, community involvement, trust, and yes, personal taste are all factors. The PMC members are the gate keepers, and being human, they show favoritism, bias, and sometimes poor judgment. You may not like it, but that's the way it is. Great. Can we move on now?

Struts isn't some damn social club, where we sit around and gossip about the neighbors. Struts is about building great web frameworks, however, I feel we have strayed from this path and lost our focus. If we, committers and contributors alike, spent half the time committing code and contributing patches as we do bickering, complaining, and "offering our opinions", we'd be on Struts 4 by now! Let's stop this nonsense, and get back to work!

Do you have too much free time on your hands? Great, there is much to be done:

- Struts Action 1: We finally got the build working and have built a test build. I haven't heard a single comment from anyone who has downloaded it and given it a shot. If you want a stable Struts Action 1 release and more to come, get off your butt and help out!

- Struts Action 2: With most of the IP code out of the way, we've started some great discussions on features to include in the next release. While this is important, we also need to get some sort of release out by JavaOne. We need people polishing up the code, updating wiki docs, testing examples, writing migration guides, and fixing bugs.

- Tiles: For such a popular framework, it is a shame how few people contribute (only one active maintainer (!)). Greg is working on a standalone version of Tiles that would support Struts, Spring MVC, or anyone else. If you use Tiles, jump in and help Greg with the refactoring. We definitely will be looking for committers when this moves to Jakarta.

- Struts Shale (yes it is an equal Struts project, get over it): There still hasn't been a GA release of Shale that I know of. We need people writing docs, fixing bugs, and providing key feedback to help polish this product.

My personal thanks David Evens for helping out with JIRA, Wendy Smoak her hard work for the Maven 2 migration, Ted Husted for the Mailreader migration tutorial and training materials, Toby Jee for keeping up with bug fixes and working on the ww migration, Patrick Lightbody for the SAF 2 Maven 2 work, Phil Zoio for writing Strecks....these are people who stepped up to the plate and put their code where their mouth is. Let's grow this list!

Don

---------------------------------------------------------------------
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