www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Cottlehuber (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LEGAL-181) Does a binary build of Apache CouchDB still qualify under ... BIS
Date Tue, 08 Oct 2013 20:20:45 GMT
Dave Cottlehuber created LEGAL-181:
--------------------------------------

             Summary: Does a binary build of Apache CouchDB still qualify under ... BIS
                 Key: LEGAL-181
                 URL: https://issues.apache.org/jira/browse/LEGAL-181
             Project: Legal Discuss
          Issue Type: Question
            Reporter: Dave Cottlehuber


The CouchDB Project provides courtesy builds for Windows users. This includes the following
crypto-related functionality:

- Erlang/OTP with a statically compiled OpenSSL
- ibrowse, an Erlang-based http client with SSL support

NB Erlang/OTP is developed & distributed by Ericsson in Sweden.

We're already covered as aproject under ECCN 5D002, like Apache HTTPD's apache_2.2.x-win32-*-openssl-*
releases, however Erlang/OTP is missing from the Controlled Sources list. It should be https://github.com/erlang/otp/

This thread http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201208.mbox/%3C50227DC3.1000107@luminis.eu%3E
seems to be a similar issue but has no obvious conclusion.

1. Does the project need to do anything further about this, or are we actually compliant already?
2. I assume I could update the controlled source list in svn, or does this invalidate the
BIS/ECCN?




--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message