Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of cctrieloff@redhat.com
 designates 66.187.233.31 as permitted sender)
Message-ID: <4720BB9C.4040204@redhat.com>
Date: Thu, 25 Oct 2007 11:51:56 -0400
From: Carl Trieloff <cctrieloff@redhat.com>
Reply-To: cctrieloff@redhat.com
Organization: Red Hat
User-Agent: Thunderbird 1.5.0.7 (X11/20060913)
MIME-Version: 1.0
To: general@incubator.apache.org, legal-discuss@apache.org
Subject: Re: 'Handling Crypto..'  - River project
References: <D2881BF3-110E-48E0-9059-326F9E88D7F3@sun.com>
 <471F7F2D.7000905@rowe-clan.net>
In-Reply-To: <471F7F2D.7000905@rowe-clan.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


Top-posting as it is related but different question. I would like to 
contribute to the
apache legal questions/ answers / discussing. What is the process for 
joining
apache legal?

(I am not a lawyer)
Carl.

William A. Rowe, Jr. wrote:
> Keep in mind, "Sun" stuff wasn't necessarily handled under generally 
> available
> open source TSU (exception) classifications, but as commercial 
> "product".  This
> is, in part, why distributors may have issues using our exceptions and 
> our
> classifications (their export legal advisors know better).
>
> For these questions, always kick them across to legal-discuss@a.o 
> please :)
>
> Bill
>
> Jim Hurley wrote:
>> We're (River incubator project) trying to comply with:
>>     "Handling Cryptography within an ASF Release"
>>     <http://www.apache.org/dev/crypto.html>
>>
>> This process talks only about software that has been
>> self classified as 5D002 (has strong crypto classification).
>> Parts of the Sun Jini Technology Starter Kit (the base contribution
>> for the River project) were classified as 5D992.b.1, which is
>> a different classification.  From the ASF perspective, should
>> we treat this (5D992) classification as effectively "no crypto"?
>>
>> Need some guidance and insight to help us understand
>> what we need to do to comply.
>>
>> thanks -Jim
>> jhurley@apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>


---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org