dum de dum de dum..... Just to be public so that it doesn't look like I'm sneaking around trying to manipulate things.
-- I'm starting to open the question of TLP on many of the Jakarta dev mailing lists. It's with a general plan where we would see another half a dozen subprojects move to TLP and then really leave Commons as the main entity inside Jakarta along with some commons-like components that are currently subprojects. I've been talking unofficially with lots of people at ApacheCon, so I've had a fair bit of feedback on various bits. The important part is that the loose plan above finds a way to coalesce the Jakarta community into a much tighter, more TLP e like project. I've talked with a couple of board members to feel out things would be. One question being, is it a problem if we're pushing a TLP with just a few committers. The answer I had was that Excalibur is the example TLP, it's rather dormant and it's not a problem. I was also advised to be a bit more active in pushing forward. I think this makes sense, a lot of our cross-community activity is gone because people with high activity tend to move to TLP, so we need a bit more drive to get things done. Thus the change of tack that I'll be trying to pull off without getting hung :) Please discuss, argue, wibble; but what I'm looking for are active ways forward instead of maintaining the status quo. I don't think the status quo is good for Jakarta as an entity, it puts strain on our oversight because the number of subprojects stretches the chair's and community in general's ability to keeps things covered. *denies the blindfold and stands against the wall waiting* Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
