On 5/26/07, Ted Husted <[EMAIL PROTECTED]> wrote:
On 5/25/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> 4) Goto code.google. Ack :(
I wouldn't discount GoogleCode (or Java.net or SourceForge or
CodeHaus). Right now, there's a GoogleCode site that I use everyday,
and it's been utterly reliable. There's features I miss, but the UI is
so convenient, I don't mind. We are not Borg, and not every software
product need live under the ASF umbella.
Ack in terms of driving a community away because it is unable to meet
our arbitrary criteria.
> Jakarta2 - A flattened commons-like umbrella which in terms of change
> means a flattened dev@ list and svn changes. What I don't know is
> whether people are going to be demanding that the subsites look the
> same; ie) need to mavenize each project and adjust the site. The
> easiest way to deal with things will be to move the other subprojects
> into Commons and reestablish the Project.
This is probably just an unfortunate turn of phrase, but we can't just
"move" anyone anywhere.
Yes we can, we just choose not to. Our PMC has a history of delegating
the decision making to the subprojects, rather than making it for
them; it's not a requirement.
Still - I'm definitely presuming that that will continue. Subprojects
need to be on board. The problem is when a subproject chooses option
5; do nothing. Is that a decision we're happy with.
The Incubator PMC is not going to accept any code without volunteers to go
with it.
Things get really easy in that situation - we retire it just like
Alexandria. We've not got any code without community currently.
Likewise, we can't do anything
about the subproject websites without volunteers to do that work too.
We can volunteer. (I'll happily go in and change things :) ).
But, as a PMC, we could ask infra@ to create a shared mailing lists to
replace the others, and make karma adjustments.
Here's my take-away from Henri's post. The Jakata PMC, as it stands
today, could set a deadline for the remaining subprojects to make
other hosting arrangements (TLP, Commons, Google). Otherwise, on a
date certain, we would create single Jakarta Dev and User lists for
all the remaining subprojects to share, and open karma to all the
subprojects to all the Jakarta committers, in the style of the
Commons.
In other words, create a TLP, join the Commons, or become a commons.
One other alternative would be for the active committers to those
remaining subprojects to draft their own resolution proposal for
creating a new Jakarta PMC, and boot the rest of us out. :) Though, if
anyone wanted to make that happen, I'd suggest making it happen for
the June board meeting, to coincide with the Commons proposal.
Chiefly, we need to decide if we're sending the Commons proposal. The
board learnt from the Shale/Struts proposal not to accept anything if
the current PMC are not happy with the situation.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
