openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <>
Subject RE: Request dev help: Info for required crypto export declaration
Date Thu, 01 Sep 2011 18:38:59 GMT
Please just do it this way:


ASF is very clear on what is required for *its* releases and this page appears to be comprehensive.

(I finally found where I saw this before.  It has also been discussed here or on the ooo-private
list before.  I remembered it as being simpler than it is.)

 - Dennis

-----Original Message-----
From: [] On Behalf Of Rob Weir
Sent: Thursday, September 01, 2011 09:15
Subject: Re: Request dev help: Info for required crypto export declaration

On Thu, Sep 1, 2011 at 11:51 AM, Danese Cooper <> wrote:
> On Wed, Aug 31, 2011 at 9:30 AM, Rob Weir <> wrote:
>> On Wed, Aug 31, 2011 at 12:29 PM, Dennis E. Hamilton
>> <> wrote:
>> <snip>
>> >> 1) Was something similar every done for  Most software
>> >> companies are aware of this US export regulation and do this
>> >> declaration as a matter of routine.  But not all open source projects
>> >> are as diligent as ASF is.  So it is possible that OOo never did this
>> >> before.  But if they did, we could reuse much of their paperwork.
>> >
>> > AFAIR Sun did that some time ago, but I'm not 100% sure.
> Yes, Sun did this (probably for every official "release").

If so, this might have been kept on the corporate side, not on the
community website.

For example, searching Google for " ECCN" shows
several requests for this information [1] [2] [3] over the years, but
no useful responses.

Looks like LO discussed it briefly [4], but dismissed it under the
misapprehension that since they are not in the US, the regulation is
irrelevant.   We'll obviously want to do better here.  It may not make
a much of a difference to the individual downloaded of AOOo, but this
paperwork is essential for anyone who might want to bundle AOOo with
laptops, for example.  The location of the project is not the solitary
relevant fact.  The location of the users and re-distributors is the
key thing.





I'll check what we did for IBM Lotus Symphony.


> Danese

View raw message