Stephen Colebourne wrote:
I understand the fustrations of J-C that might cause this proposal. I do
fear the result of this change though. However, I believe that an individual
component has the right to decide its own fate within J-C. So all I can do
is indicate my -0 to the change at the moment as I don't think alternatives
have yet reached a conclusion.
To go to A-C means to have no supporting community other than codec
developers.
Will you ask for your own mailing list?
I don't see why not. I would prefer this for a few reasons. First, I
think that the shared mailing list is distracting from the focus needed
to produce quality software. Second, I think that the shared mailing
list leads to an unnecessarily bulky "community".
or be on the same list as Serf?
Are there enough of you?
Enough people profess interest in using this product, but only a few
committers (myself and Gary) actually go about the business of
contributing. Believe it or not, I think that components get lost in
the signal to noise ratio of the Jakarta Commons development mailing list.
Who will judge the readiness for releases (the A-C members?)?
The Apache Commons PMC. AFAIK, a PMC is the ultimate arbiter of release
readiness. I see no reason to change that.
Is there no affiliation with the rest of J-C as one community?
Why? to make people in J-C feel better about themselves? Seriously,
I fly contrary to this spirit of self-affirmation. Jakarta Commons is
not a successful or thriving community. I saw 2 CVS commit emails from
Friday, and a lot of posturing and self-affirmation.
Stephen
----- Original Message -----
From: "Tim O'Brien" <[EMAIL PROTECTED]>
Codec, a small - probably the smallest - piece of code in Jakarta-land.
Is well suited for inclusion in Apache Commons. I propose that Codec be
used as a guinea pig of sorts to test the waters of Apache Commons. It
is not language specific, and it is something that could be excised from
the Commons with limited fuss.
To this end, I propose that Jakarta Commons Codec be officially
transformed into Apache Commons Codec.
Simultaneous with the move from J-C to A-C -
#1. Commons Codec will be hosted on Subversion
Why? Subversion is ready and superior in almost every aspect. Moving
smaller projects such as this one to Subversion will allow us to iron
out any kinks, and will help nudge more projects in this direction.
#2. Commons Codec will use Jira for issue tracking.
#3. All committers to Commons Codec are also granted access to Apache
Commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
