[
https://issues.apache.org/jira/browse/MYNEWT-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sterling Hughes resolved MYNEWT-122.
------------------------------------
Resolution: Fixed
Updated on the site, resolving.
> Update www.apache.org/licenses/exports/ with Apache Mynewt crypto info
> ----------------------------------------------------------------------
>
> Key: MYNEWT-122
> URL: https://issues.apache.org/jira/browse/MYNEWT-122
> Project: Mynewt
> Issue Type: Sub-task
> Components: Image Mgmt
> Reporter: Aditi Hilbert
> Assignee: Justin Mclean
> Fix For: v0_8_0_rel
>
>
> Justin, can you help us here since you are a PMC chair? We need to add the
> link to the crypto code in our project on the following page:
> http://www.apache.org/licenses/exports/
> The info is:
> Apache Mynewt Incubator Project
> Product Name: Apache Mynewt
> Version: development
> ECCN: 5D002
> Controlled Source: ASF
> Link:
> https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-larva.git;a=tree;f=libs/mbedtls;hb=refs/heads/develop
> Once this is done, I can send the email notification to the US Govt.
> thanks!
> -------------------
> To satisfy the BIS requirements to make source code available for inspection,
> while minimizing the number of notification emails needed to be sent, the ASF
> maintains a single web page at http://www.apache.org/licenses/exports/ with
> links to the applicable source code for each version of each ASF product
> classified as ECCN 5D002.
> To make updates to this ASF-wide Exports page as simple and consistent as
> possible, the source XML page contains a list of XML trees under eccnmatrix
> that can be edited by anyone with site-dev karma (which includes all of the
> PMC chairs). Note that the exports web page is generated from the XML.
> Any edits to the exports page should be tested using both the site build
> process (view the index.html before committing any changes) and by running
> the bisnotice.xsl transform on the product added/changed (see below). You can
> probably figure out what the content of the XML fields should be by following
> the example of other projects and reading the page. If you have any further
> questions about the content, or if you are not sure that a BIS notice is
> required, please check the FAQs first and then bring any remaining questions
> to the legal-discuss mailing list. Note that the product data should only be
> version-specific if the classification changes (e.g., Apache HTTP Server
> version 1.3 vs 2.0) or if the link to the controlled source code needs to
> change, such as if the encryption library included in the product for
> different releases came from different manufacturers. In addition, note that
> it is possible to include both controlled and non-controlled (ECCN "n/a")
> products in the list, but a BIS notice is only necessary for the products
> that have at least one version classified as 5D002.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
