Michael, I'd like to follow-up on just one point - reviewing of patches.
Anyone can monitor bugzilla and review patches when they come in. If several people send feedback, via bugzilla or via the mailing lists, it might speed up the process of getting those patches into CVS. If there's a patch that you would find useful, try it out and report back. If several people are reporting back about the same patch and they all say it solves the problem, then we know that a) this is an issue that affects many people b) the patch is probably good. In that case, the chances of a committer spending time looking at the problem is greatly increased because they know it's a worthwhile cause and that a probable solution exists. So there is at least one way for more people to contribute AND reduce the backlog of requests. Steve > -----Original Message----- > From: Michael McGrady [mailto:[EMAIL PROTECTED] > Sent: July 4, 2004 11:46 AM > To: Struts Developers List > Subject: Re: thoughts on encouraging user development > > > This was one of the more helpful posts in this regard in a long > time. Thanks Ted. > > From the point of view of someone who regularly adds code to > the struts > framework on my own site but whom never really offers that > code to the > community, EXCEPT VIA THE struts WIKI (for reasons explained > here before), > it might be helpful if someone with perspective on the struts > "project" > indicated in clear terms what would be helpful. I can tell > you that I > personally don't have a clue, even though I am daily in > contact with all > the idea emanating out of struts. I think I have a sufficient > understanding of struts to write the platform from scratch. > But, I don't > have the time to burrow through the administrative details to > get involved > seriously in the community. This is especially so if > contributions are > going to just sit without review for an indeterminate period. > I think > everyone likes to think that there work is going to at least > have a chance > at making a difference. > > This is not written in despair. I can tell that struts is doing just > fine. Great in fact. Love it. Just some thoughts if anyone > cares about > this perspective. > > Michael > > At 11:10 AM 7/4/2004, you wrote: > >One of the best posts I've read on contributing to open > source is one that > >Craig made some time ago to the Tomcat list. > > > >* http://jakarta.apache.org/site/contributing.html > > > >In this post, Craig describes how committers evolve from > users. As people > >use use Struts, and find ways to improve it, they can > contribute their > >improvements back to the community. There are several ways to make > >contibutions. Many people setup their own site, other join > the SourceForge > >Struts site (http://struts.sf.net/), and some make > contributions to the > >main distribution. > > > >Because we consider contributing an extension of using, the "How to > >contribute" material is part of the Using page. > > > >* http://apache.struts.org/using.html > > > >If anyone gets the sense that we aren't pushing hard for > contributions, it > >might be because we are already backlogged. There are 262 > outstanding > >enhancement tickets, 29 with patches. So many that I > despair at ever > >reviewing them all. I'm sure that many are duplicates, > overlapping, or > >obsolete, but what Apache hours I have available need to be spent > >elsewhere right now. :( > > > >-Ted. > > > > > >--------------------------------------------------------------------- > >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]
