Hi Dennis: Dennis Sosnoski wrote: > Whether officially led by WSO2 or not, certainly most of the direction > of the project has come from people associated with WSO2 and/or the Sri > Lanka university. Glen is, I believe, the current chair of the PMC, and > was also the release manager for the 1.5 release.
I agree re: most of the committership having historically been from WSO2, but also IBM. You may not be aware that I'm no longer associated with WSO2 as of January; these days I'm an independent consultant. > As to Axis2 status, you don't see a problem in pointing people at a > latest Axis2 release which only supports HTTP transport and does not > have any corresponding Rampart release? Some delay in getting these > other components out is understandable, since they are separate projects > (wisely so or not), but it's been a month and a half since Axis2 1.5 was > released and there's been no noticeable move toward releasing these > essential components. (Note - all the transports are usable with Axis2 1.5, there just hasn't been an official release. It's not as if Axis2 1.5 "only" supports HTTP.) Although of course this is a team effort, I'll step up to take this one since as release manager I should have at least been pushing harder to get the transports release happening in parallel. I did ping the Rampart guys, but everyone has been pretty busy (including me). I'm going to try and get 1.5.1 out the door ASAP, and will commit to at least the transports happening along with that. > I don't know all the details of how Apache works - is this something > which should be addressed by the PMC? This is a volunteer effort, as always. The PMC can certainly indicate problems and discuss them, but they can't force committers to actually do any work. One thing I think we might suggest to improve the situation is a "JIRA-thon", where we get committers to pledge that they'll fix a certain number of JIRA issues (10 might be a good start) over a certain period of time, say two weeks. It would be great if we could release 1.6 with a LOT of problems fixed. Part of the problem is that we're not communicating well enough as a team, and not keeping track of what really needs doing. I don't actually fully agree with Sanjiva's assertion that Axis2 is "essentially done", because 1) we REALLY shouldn't have hundreds and hundreds of JIRAs - sure, some are frivolous but many are real issues causing real problems (case in point the incorrect use of the HTTP connection manager I fixed recently), and 2) every time I dive in there I see some really poor code somewhere. Not that we're the only project to have less-than-perfect code, but I'm worried that thinking too much along the lines of "we're a mature project" might lead to complacency about fixing some of these problems. Thanks, --Glen
