Craig R. McClanahan wrote:
Sorry for the late response on this ... it seems like weekends are the
only time I get to play with open source code any more :-(.

I hear that, brother! =:0) The catch-as-catch-can thing isn't working for me anymore either, so I think I'll take my own advice


http://jakarta.apache.org/struts/faqs/helping.html#corp

and block out a regular time for open source development and call it part of the work week. I really want to Bugzilla sorted-out and fill in some of the remaining gaps in the documentation.

Since we have a wiki now, I thought it might be helpful to setup a short term plans page. I took the liberty (surprise!) of adding some notes people have made on the list or in Bugzilla recently.

http://nagoya.apache.org/wiki/apachewiki.cgi?action=edit&id=StrutsShortTermPlans

Also, I setup a Job Jar page on the Wiki

http://nagoya.apache.org/wiki/apachewiki.cgi?StrutsJobJar

I'd like to add this item as well:

* <b>A maintainer for the conventional Struts taglibs package is needed.</b> If you are motivated, self-starting developer who is actively using these tags, groks the Apache Way, and can spare the time, please take a look at the outstanding reports for the taglibs components, and start submitting patches for our consideration.

But thought I should see if we have consensus on this first.

At one time, we were not pursuing the conventional tags because we did not want to steer people away from JSTL. But now that we have an actively-supported JSTL tag library, it may be time to fish around for someone to actively maintain this package on behalf of the segment of our Community who need, or choose, to use these tags.

Usually, I would suggest we let nature take its course and see if a taglib developer appears spontaneously. But, I think we may have given the community the impression that we are antagonistic towards these tags, and it may be prudent to take affirmative action to correct that impression.

-Ted.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to