Now that most or all of the Nordic nRF5 SDK is covered by the permissive 5-clause Nordic license (as of June 2017: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/introducing-nordics-new-software-licensing-schemes), do you have any objections to us putting the SDK in a public GitHub repo that we can use as a submodule in our own open-source project? This is for convenience, so we don't have to download the sdk during the build process or copy it into our main repo.
My understanding is that the redistribution clause would permit this. This license appears to the same as the license for https://github.com/NordicSemiconductor/nrfx. So the nrfx repo is an example of what i want to do (except that you control that repo).
This question came up in the past, but that was before the new licensing scheme.
Ideally, you'd have a master repo that was just an unpacked version of the nRF5 SDK. We could then fork that or use it directly. I see something similar already for the Mesh SDK: https://github.com/NordicSemiconductor/nRF5-SDK-for-Mesh, but I don't know if you're planning to do this soon. I've read here that you have an internal VCS and bug tracking system, so I'd certainly understand if your public repo was locked down and didn't permit issues or PR's.
Thanks very much.
