gustavonihei commented on pull request #566:
URL: 
https://github.com/apache/incubator-nuttx-apps/pull/566#issuecomment-898611028


   @btashton Just to see if we're aligned on the remaining tasks for this 
paperwork. There are 4 steps that the Apache guide requires to be done:
   
   **[Check the Export Control Classification Number 
(ECCN)](https://infra.apache.org/crypto.html#classify)**
   **[DONE]** Basically there is no work on this. MbedTLS is already used by 
several Apache projects, including MyNewt, so we can rely on the pre-executed 
assessment.
   
   **[Update the Exports Page with Source 
Links](https://infra.apache.org/crypto.html#sources)**
   **[Pending]** I believe we need the support from @justinmclean for 
fulfilling this item. We just need an entry for `APACHE NUTTX (INCUBATING) 
PROJECT` on [this page](https://www.apache.org/licenses/exports/) like this:
   ### APACHE NUTTX (INCUBATING) PROJECT
   - Apache NuttX
     - development / 5D002 / [ARM 
MbedTLS](https://www.trustedfirmware.org/projects/mbed-tls/)
   
   **[Notify the U.S. Government of the 
release](https://infra.apache.org/crypto.html#notify)**
   **[Pending]** Maybe the most complicated of all the tasks, but not that 
complicated at all. We need to fill the email template containing a brief 
description about MbedTLS or use the script from the Apache SVN for generating 
it. We may help on this one, Espressif has already gone through this process 
for enabling the integration of MbedTLS on ESP-IDF. Let us know if you need any 
support.
   
   **[Inform users by including a crypto notice in the distribution's README 
file](https://infra.apache.org/crypto.html#inform)**
   **[DONE]** We may simply copy the note from [Apache 
MyNewt](https://github.com/apache/mynewt-core#export-restrictions). See 
https://github.com/btashton/incubator-nuttx-apps/pull/1


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to