Taking a step backwards. What are the current problems besetting Commons? I'm probably getting ahead on myself on trying to organize solutions without consensus on problems.
We have an inactivity issue, and reflecting that inactivity to the users. To solve the latter we've added the dormant concept to the Sandbox, and need to do something similar to the main projects. Jakarta as a whole has these problems and I'm looking to Commons for the solutions. On the former, we've given ourselves a mental wake up to get people involved, patching and committing. We've got an experimental m2 build in the sandbox, and a couple of components which don't have an m1 build. How independent do we want components to be. I'm thinking less independent because I want to maximise the ease with which people can move between components (to deal with inactivity), but the community might want to go the other way and be far more bazaar like. We have releases going out without our awareness. The commons-cli issue to the maven repository a while back; Jakarta had a similar one with velocity-dvsl. That's a general Apache problem that I'm suggesting solutions to on repository@ and letting what I'm saying here be affected by that (which probably makes me seem more illogical than usual) - this is one of the reasons why I'm in favour of a general Apache solution to group-ids. We have a sprawling site that could be much better - though this is entirely my opinion. We have a very noisy set of mailing lists. Need to ask how the Jive forum is going for Struts (I think I heard that was in place?). Watching how the Maven-dev move to separate lists for commits, jira, dev, ci goes. We have a need to organize our CI. Apparantly the hold up there is twofold: 1) issues over a general build server, or whether it should be individual pmcs 2) the zones machine is busy cpu wise and Infra don't want us to have a Commons zone that builds a lot just yet. The PMC Chair is casting random solutions to Jakarta's oversight and community issues and suggesting Commons can absorb Jakarta (apart from the bits that leave) as a solution. Lack of release management. I'm getting over my PGP whining and am going to dig in and start volunteering to do some releases again. We've recently raised issues in managing the sandbox promotion/failure cycle. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
