Re: Export Control for Geode
No worries, thanks so much for the help! I’ll update the README(s) as needed. Anthony > On Mar 13, 2017, at 11:08 AM, Mark Bretlwrote: > > HI Anthony, > > Sorry for the delay, I have completed steps #1 and #2. > > --Mark > > On Mon, Mar 6, 2017 at 10:42 AM, Anthony Baker wrote: > >> Thanks Mark! Let me know if you have any questions. >> >> Anthony >> >>> On Mar 6, 2017, at 10:32 AM, Mark Bretl wrote: >>> >>> Looks good. Unless there are any other comments/issues, I will start this >>> tomorrow. >>> >>> --Mark >>> >>> On Thu, Mar 2, 2017 at 10:29 PM, Anthony Baker >> wrote: >>> After reviewing [1], I think we need to record and report our use of cryptographic libraries that fall under US export control. This means: 1) Updating the eccnmatrix.xml [2] in svn and publishing the change [3]. 2) Sending an email [4]. 3) Updating README.md [5]. Mark, #1 and #2 need to be done by the PMC Chair. Can you review this and let me know what you think? I can tackle #3 after. Thanks, Anthony [1] http://www.apache.org/dev/crypto.html [2] https://gist.github.com/metatype/96da9d928f20d5ae638cc16dd4ee9a85 [3] https://cms.apache.org/www/publish [4] https://gist.github.com/metatype/24b4462af6319cbf568b63ad3a56464e [5] https://gist.githubusercontent.com/metatype/ b50b49a4c2a7a99793029b3ea0cde8c3/raw/40aca011a65c12d6fbec73fce60f57 f43323d36f/README.md >> >>
Re: Export Control for Geode
HI Anthony, Sorry for the delay, I have completed steps #1 and #2. --Mark On Mon, Mar 6, 2017 at 10:42 AM, Anthony Bakerwrote: > Thanks Mark! Let me know if you have any questions. > > Anthony > > > On Mar 6, 2017, at 10:32 AM, Mark Bretl wrote: > > > > Looks good. Unless there are any other comments/issues, I will start this > > tomorrow. > > > > --Mark > > > > On Thu, Mar 2, 2017 at 10:29 PM, Anthony Baker > wrote: > > > >> After reviewing [1], I think we need to record and report our use of > >> cryptographic libraries that fall under US export control. > >> > >> This means: > >> > >> 1) Updating the eccnmatrix.xml [2] in svn and publishing the change [3]. > >> 2) Sending an email [4]. > >> 3) Updating README.md [5]. > >> > >> Mark, #1 and #2 need to be done by the PMC Chair. Can you review this > >> and let me know what you think? I can tackle #3 after. > >> > >> Thanks, > >> Anthony > >> > >> [1] http://www.apache.org/dev/crypto.html > >> [2] https://gist.github.com/metatype/96da9d928f20d5ae638cc16dd4ee9a85 > >> [3] https://cms.apache.org/www/publish > >> [4] https://gist.github.com/metatype/24b4462af6319cbf568b63ad3a56464e > >> [5] https://gist.githubusercontent.com/metatype/ > >> b50b49a4c2a7a99793029b3ea0cde8c3/raw/40aca011a65c12d6fbec73fce60f57 > >> f43323d36f/README.md > >> > >
Re: Export Control for Geode
Thanks Mark! Let me know if you have any questions. Anthony > On Mar 6, 2017, at 10:32 AM, Mark Bretlwrote: > > Looks good. Unless there are any other comments/issues, I will start this > tomorrow. > > --Mark > > On Thu, Mar 2, 2017 at 10:29 PM, Anthony Baker wrote: > >> After reviewing [1], I think we need to record and report our use of >> cryptographic libraries that fall under US export control. >> >> This means: >> >> 1) Updating the eccnmatrix.xml [2] in svn and publishing the change [3]. >> 2) Sending an email [4]. >> 3) Updating README.md [5]. >> >> Mark, #1 and #2 need to be done by the PMC Chair. Can you review this >> and let me know what you think? I can tackle #3 after. >> >> Thanks, >> Anthony >> >> [1] http://www.apache.org/dev/crypto.html >> [2] https://gist.github.com/metatype/96da9d928f20d5ae638cc16dd4ee9a85 >> [3] https://cms.apache.org/www/publish >> [4] https://gist.github.com/metatype/24b4462af6319cbf568b63ad3a56464e >> [5] https://gist.githubusercontent.com/metatype/ >> b50b49a4c2a7a99793029b3ea0cde8c3/raw/40aca011a65c12d6fbec73fce60f57 >> f43323d36f/README.md >>
Re: Export Control for Geode
Looks good. Unless there are any other comments/issues, I will start this tomorrow. --Mark On Thu, Mar 2, 2017 at 10:29 PM, Anthony Bakerwrote: > After reviewing [1], I think we need to record and report our use of > cryptographic libraries that fall under US export control. > > This means: > > 1) Updating the eccnmatrix.xml [2] in svn and publishing the change [3]. > 2) Sending an email [4]. > 3) Updating README.md [5]. > > Mark, #1 and #2 need to be done by the PMC Chair. Can you review this > and let me know what you think? I can tackle #3 after. > > Thanks, > Anthony > > [1] http://www.apache.org/dev/crypto.html > [2] https://gist.github.com/metatype/96da9d928f20d5ae638cc16dd4ee9a85 > [3] https://cms.apache.org/www/publish > [4] https://gist.github.com/metatype/24b4462af6319cbf568b63ad3a56464e > [5] https://gist.githubusercontent.com/metatype/ > b50b49a4c2a7a99793029b3ea0cde8c3/raw/40aca011a65c12d6fbec73fce60f57 > f43323d36f/README.md >
Export Control for Geode
After reviewing [1], I think we need to record and report our use of cryptographic libraries that fall under US export control. This means: 1) Updating the eccnmatrix.xml [2] in svn and publishing the change [3]. 2) Sending an email [4]. 3) Updating README.md [5]. Mark, #1 and #2 need to be done by the PMC Chair. Can you review this and let me know what you think? I can tackle #3 after. Thanks, Anthony [1] http://www.apache.org/dev/crypto.html [2] https://gist.github.com/metatype/96da9d928f20d5ae638cc16dd4ee9a85 [3] https://cms.apache.org/www/publish [4] https://gist.github.com/metatype/24b4462af6319cbf568b63ad3a56464e [5] https://gist.githubusercontent.com/metatype/b50b49a4c2a7a99793029b3ea0cde8c3/raw/40aca011a65c12d6fbec73fce60f57f43323d36f/README.md