All those projects have to be kept in sync with the upstream which may create some extra work I am a bit concerned for the maintenance effort
Best regards Alin On Thu, Jun 27, 2024 at 6:41 PM Nathan Hartman <hartman.nat...@gmail.com> wrote: > On Thu, Jun 27, 2024 at 11:40 AM Gregory Nutt <spudan...@gmail.com> wrote: > > > On 6/27/2024 9:30 AM, Tomek CEDRO wrote: > > > Hey there Alan :-) > > > > > > +1 here :-) > > > > > > I would put that to apache/nuttx-deps repo so maintenance is easier > > > and more coherent with the rest of the project :-) > > > > > > Have a good day folks :-) > > > Tomek > > > > Many of have licenses that are incompatible with Apache 2 and so could > > not be under apache/ > > > > In principle I agree we need a backup in case upstream projects disappear. > > Projects *have* disappeared in the past. For example, kconfig-frontends > disappeared for a while due to the author moving apartments. Thankfully it > returned but it (and other important tools) may disappear again, and may > disappear forever. > > Regarding licensing: > > I don't know whether there are any Foundation policies about hosting such > a... backup? mirror? What is it called? How can it be done in a way that > agrees with policies, if there are any? > > Cheers > Nathan >
