Mailing-List: contact jcp-open-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: jcp-open@apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 adc@toolazydogs.com does not designate 72.14.220.156 as permitted sender)
Message-Id: <828D2E1A-80CE-4161-9BBF-B1BF4B74BE66@toolazydogs.com>
From: "Alan D. Cabrera" <adc@toolazydogs.com>
To: jcp-open@apache.org
In-Reply-To: <4B55CE80.2060801@ungoverned.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: OSGi CT access
Date: Tue, 19 Jan 2010 10:01:00 -0800
References: <351CAD18-C7CF-4AE7-A933-0D69148C760E@gmail.com>
 <4B55CE80.2060801@ungoverned.org>


On Jan 19, 2010, at 7:23 AM, Richard S. Hall wrote:

> On 1/19/10 10:11, Kevan Miller wrote:
>> I'd like to confirm the process for gaining access to the OSGi CT.
>>
>> An ASF committer can:
>>
>> * submit an NDA -- http://www.apache.org/jcp/ApacheNDA.pdf
>> * send a request on jcp-open, presumably with an simple explanation  
>> of why they would like access to the CT (e.g. I'm working on the  
>> Apache Aries project and would like access to the OSGi CT).
>>
>> Is that about right?
>>
>
> For me, this seems reasonable. I was looking to Geir to see if he  
> agreed, since he has more experience with this than me.

For CT work, would we need a separate mailing list?


Regards,
Alan