Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for change notification.
The following page has been changed by HenriYandell: http://wiki.apache.org/jakarta/JakartaBoardReport-September2005 The comment on the change is: Report written. Will send tomorrow morning on the off-chance that things come up ------------------------------------------------------------------------------ === Status === - Issues for Hen to write up: + Various issues of note occurred this month: + * POI legal issue (in bugzilla) - A POI contributor had submitted a Bugzilla entry that was based on documentation on a website that should not have legally been there. The attached files were removed by the admin and a suitable comment inserted. This legally issue is effectively closed as it's a big grey legal tightrope and all that's left to see is if the pain has put the contributor off of contributing again. - * HttpClient renaming query - * POI legal issue (bugzilla entry) - * BeanUtils legal issue (code) - * Silk subproject - Taglibs will attempt to have a grand clear out and move to Silk - * Standard to be promoted - Managing inactivity is a critical issue: + * BeanUtils legal issue (in code) - Sam Ruby raised a concern over code in Commons BeanUtils described in the code as "Package private support methods (copied from java.beans.Introspector)", ie) were we legally covered. [http://issues.apache.org/bugzilla/show_bug.cgi?id=36445]. Based on the bug entry, Niall Pemberton rewrote the code in question (he was not party to the conversation on pmc@ though), which may or may not be enough. One of the problems with this issue is that it's not been possible to identify the source of the code, it appears to have turned up between the code leaving Struts and entering Commons for the first time. So unsure if this is covered by Sun's CCLA. The issue is still open. + * HttpClient renaming query - Commons HttpClient is seeking to move from Commons to a full Jakarta subproject. They're had their own mailing lists for a long time and this is something we should have done a long time ago. The name 'Jakarta Http' was raised and disapproval quickly voiced by other projects with whom it would cause confusion. Expect more on this in the next report. - * Taglibs teetering dangerously close to inactivity - * BCEL activity increased, next step is to build the developer community - * Failure to improve BSF PMC oversight this quarter (chair's fault), critical for the next quarter. - * Velocity inactivity debate. - * Commons/ApacheCon EU brought forth the 'commons-dormant' concept to get lots of sandbox'd projects that are utterly inactive out of the way of the active ones. - The increased focus on the Incubator and how to bring code to the ASF along with the inactivity issue are shining a spotlight on the Jakarta sandboxes as something to work on in the next quarter. + * Silk subproject - 'Apache Jakarta Silk' was chosen as the name for a new subproject to contain Web components. Various parts of Commons and Taglibs will form the initial codebase. The name was passed to the PRC who raised questions on potential clashes with other products/companies. This issue is still open. + + * Commons Sandbox - It's become increasingly obvious that the Commons Sandbox governance needs some attention. Discussions at the ApacheCon EU brought forth the idea of a 'commons/dormant' status, and many of the sandbox components have been moved to that. Various legal issues are becoming more well known, such as the need to sign software grants, and the recently added commons-proxy is in the process of that, and a new commons-csv component will be doing the same thing. + + ==== Inactivity ==== + + Managing inactivity is becoming a critical issue. The promotion of the larger, more noticeably vibrant subcommunities from the Jakarta umbrella has made it a lot more obvious where there are gaping holes of inactivity. The community is reacting to deal with that, sometimes naturally, sometimes with a nudge and on some occasions it looks like we'll probably just need a state of dormancy for codebases. Here's a quick list that affects 50% of the subprojects: + + * Taglibs. This is teetering dangerously close to inactivity. Three active committers, but they're largely focused on one or two of the components. The solution is going to be to move the active concerns to the Silk subproject and archive all of the inactive components. This community's coma is largely induced by the release of JSTL a few years back, a new standard that replicated much of the work that was there. + + * BCEL activity increased a lot, commits are largely from one person though there are other Apache committers replying on the lists. + + * Failure to improve BSF PMC oversight this quarter (chair's fault), a critical issue for the next quarter. + + * ORO, Regexp, ECS are all completely inactive. Watchdog and Alexandria are finished. === Releases === --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
