Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Mime-Version: 1.0 (Apple Message framework v609)
In-Reply-To: <3FE3BA40.2020304@discursive.com>
References: <3FE3BA40.2020304@discursive.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <8092B176-329C-11D8-BE18-000A959FF68E@dotnot.org>
Content-Transfer-Encoding: 7bit
From: Scott Sanders <scott@dotnot.org>
Subject: Re: [codec] [proposal] Moving To Apache Commons
Date: Fri, 19 Dec 2003 19:27:56 -0800
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>


On Dec 19, 2003, at 6:56 PM, Tim O'Brien wrote:

> 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
>
+1

> 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.
-0.  Don't care.
>
> #3. All committers to Commons Codec are also granted access to Apache 
> Commons
>
Naturally.

Scott


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org