Hi Justin, The point we are discussing is how to integrate external/third-party projects on NuttX apps repository. The licensing it only one of many issues we have.
Some months ago I suggested that NuttX could focus only in the kernel and we could create an external distribution using some build system like buildroot, yocto, etc. But as some people pointed, maybe a great strength of NuttX is to have everything integrated. So, I tend to agree with that. Maybe a better approach should be an option where the user select which licenses he/she accepts to use: BSD, MIT, LGPL, GPL, etc, and some disclaimer based on licenses he selected (i.e.: "You selected (L)GPL, then your final firmware cannot be used for commercial application if you don't release the source code"). Then now comes the issue you are talking about: we cannot include all types of software licenses inside the Apache repository. So an alternative is to have a nuttx-apps-external that will have all kind of projects that are not part of native NuttX Applications, but that are very useful for users. Other option is to follow the current path we already do: just put the Makefile with the instructions to download, configure and build the external project. But this solution is very prone to errors: sometimes the original file to be downloaded was moved to other place or removed, then we need to spend time fixing it. Using the nuttx-apps-external repository we will not have these issues because there we will have a copy of each external project. BR, Alan On 5/24/20, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > I’m concerned that you are discussion doing work outside of the Apache > repositories. Why is the main issue here? > > Greg mentions that the apache report are not properly controlled and > verified but I’m not 100% sure what he means by that. The PMC has control of > them and only verified committers have access. If this is just to avoid > licensing issues then I suggest that is also not the best way to deal with > that and let’s discuss what those issue are and see if there are other ways > of resolving them. > > Thanks, > Justin
