Talk to the Google folks, since I use Gmail :-).
They seem to be getting into fights with a lot of people these days. Doesn't seem that "do no evil" and "we're publicly traded now" mix very well for very long :)
I hope you're not missing my main point ... the process by which collaboration occurs is irrelevant if only words and not code is shared. That's why wish lists (in any form) are pretty useless unless they are backed up with action.
I didn't miss that point at all, and I couldn't agree more :)
But conversely, I hope your not missing my main point... Virtually everyone you talk to has their own wish list for Struts, but for various reasons they never do anything about them (well, aside from state them on the mailing lists of course). I think one of the reasons is not knowing if their ideas will be met with any interest, or if they might spend three weeks working on something only to have someone else "beat them to the punch". No one likes to feel like they have wasted effort, and I think a central communication hub might help alleviate this problem.
Mailing lists have served the Struts developers just fine in the almost five years that Struts has been in existence. That doesn't mean other technologies might not have been helpful, or worked better. It just means that Struts is what it is because people acted by creating something, rather than only talking about creating something (or, only talking about something they wish someone *else* would create for them :-).
Your main point again :) Still valid a pargraph later!
About the mailing lists though... I agree they have worked, and continue to, but why not explore some other alternatives that might raise effiency, espcially in light of an expanded community? I think they have worked in the past because the number of possible contributors hasn't been as great as it is now (not to mention the number of users, which has clearly grown over the years). I don't know that my idea would be any better of course, but I thought it was worth proposing at least :)
Craig
PS: The more formal way to request an enhancement, of course, is to use the issue tracking system: http://issues.apache.org/bugzilla
That's true, but like the Wiki I would make the argumnet that it really isn't what its designed for. I mean, the name itself, BUGzilla, says that its an issue tracking system. I know that everyone in the world seems to use it for enhancement requests too, but is it truly appropriate?
Even putting that question aside, I am curious (and this is a legitimate question that you may be able to answer)... do people view those submissions as direct requests of the Struts development team? I know anyone can contribute patches, but how do people really view the target of the requests they make there?
The point being that if most people think of it as requests to the Struts team, then its not serving the same purpose as what I propose, which is more coordination of the potential development community OUTSIDE the core Struts development team. The question remains though: what do you believe the perception is? That makes all the difference, as perception usually does :)
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
