> -----Original Message-----
> From: Gregory Nutt <spudan...@gmail.com>
> Sent: Saturday, May 23, 2020 2:04 PM
> To: dev@nuttx.apache.org
> Subject: Re: mbedtls
>
>
> > i guess a user often want to use apache-nuttx-external AND his own version.
> > while you can always workaround it with symbolic links, i wonder if it
> > could be more straightforward to use multiple "external" repos.
>
> People have talked about this on and off for some time in various way. There
> really needs to be a better decoupling between the
> RTOS and the applications that run on top of it. I would think that
> incubator-nuttx-apps should be only an application framework with
> highly integrated apps (like NSH) and that ALL other applications reside
> elsewhere.
>
Yes, apps is suitable for the code write from scratch for NuttX or the project
stop the active development. But since Apache Foundation has more strict
license requirement which mean that the owner of 3rd party code need sign SGA:
https://www.apache.org/licenses/contributor-agreements.html#grants
So if you want to put the source code into apps git, you need:
1.The library is Apache license
2.The library isn't in the active development
3.The owner sign Software Grant Agreement
4.Pass nxstyle check
> Taking this to the next step, this could involve some external repositories
> containing a variety of applications, original NuttX
> applications and 3rd party applications, along with some configuration tool
> to setup a NuttX userland. People, particularly Alan, has
> often advocated this as a "NuttX distro". However, I think the term distro
> alienates people. Let's just say repositories outside of
> Apache that integrate applications intothe incubator-nuttx-apps application
> framework.
>
> There is a good spot at github.com/nuttx, but that is not currently in-use.
> It is currently just a free-for-all and not suitable for any
Yes, github.com/nuttx is a good location to mitigate the above constraint.
> critical software development. But I think we could tighten up the security
> there, add some automated testing, and create some kind
> of project structure to protect and maintain the repositories.
>
> Ultimately, you are talking about another non-Apache project. That project
> would need some organization and support.
>
I propose that we reuse the same process(Apache Way) for github.com/nuttx(e.g.
review/merge, select new committer/PMC). The only difference is that
github.com/nuttx isn't an Apache project and is an optional component.
>
