On 5/22/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
Quick summary of this thread 28 Votes for (23 binding), 4 against (3 binding). Seems to me that those objecting don't seem to have pursuaded people to change their vote. At what point do we decide on a result?
I think you just did :) Definitely a consensus in favour of the resolution. The negative opinions in the thread then started moving in the direction of other ideas. My preference is for a single-community Jakarta, I think the time has come to finish the job - however if that looks like it's never going to come then I think the best thing is for Commons to go TLP. Here's what I think could happen: If willing, ECS, ORO, Regexp moving into Commons. Probably move ECS into maintenance immediatley but that's a different story. Both dev and user mailing lists to merge in. I think JCS, BCEL and BSF should also all move into Commons if willing; with the intention of moving them to TLP if they grow. I think BSF is a good TLP on paper, but some more time 'incubating' will be valuable and that'll be better in the relatively small move to Jakarta-Commons. Dev lists should merge in, user lists could stay outside I think (assuming some level of activity currently). Taglibs is currently discussing a good chunk of internal clean-up. We'll retire most of the taglibs and focus on three. Much like BSF, I think the future for Taglibs could easily be folding into Commons or going TLP if it more activity. Again, fold dev into commons, keep user separate. The devs there already have high overlap with Commons. --- up til this point was the easy bit :) Http Components is much the same as Taglibs/BSF, but less overlap and less interested in returning to Commons. I think it would do well to follow the same course (merge dev list, different user list, keeping an eye on TLP in the future if growth). * Slide. There's some sign of activity here. Not enough yet. * Cactus. Tiny bit of activity, again not enough for a TLP. * JMeter. Lots of commits from Sebb, but not a big community. For all three of these the best solution I can think of is to move them to the Incubator. Keep the lists where they are, move the svn, move the websites. They need to be thinking TLP, they need to get community. -- If that, or something like it, sounds like a good consensus plan, then I'm definitely more in favour of that than Commons going to TLP. There are really only four steps: Step 0: Consensus. Step 1: Move 3 projects to the Incubator. Step 2: Move other projects into Commons. Step 3: Re-establish Jakarta PMC - we'd use pretty much the same resolution we just voted on here. So the question is; is the above direction worth discussing, or should we just go with the Commons TLP. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
