> There are known CAN sources that have GPL code and have been documented in the LICENSE File > All this code is protected under the include GPL code config option and disabled by default > Is this approach approved or we should completely remove the GPL code from NuttX?
The code in question is dual licenced : > SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause) Doesn't that mean we can choose which license suits us (in this case, BSD-3)? śr., 6 wrz 2023 o 13:15 alin.jerpe...@sony.com <alin.jerpe...@sony.com> napisał(a): > Hi Shane, > > Thanks for the clarification > > There are known CAN sources that have GPL code and have been documented in > the LICENSE File > > All this code is protected under the include GPL code config option and > disabled by default > > Is this approach approved or we should completely remove the GPL code from > NuttX? > > Thanks > Alin > > > From: Shane Curcuru <a...@shanecurcuru.org> > Sent: den 6 september 2023 13:07 > To: dev@nuttx.apache.org > Subject: RE: CTU CAN FD driver multi-licence for Nuttx > > On 2023/08/09 00: 20: 42 Andrew Dennison wrote: > Hi Nuttx Dev, > > We are > negotiating with the authors of the linux device driver for the CTU > CAN > FD IP core to it re-licenced from GPL to so the driver can then be > ported > to > ZjQcmQRYFpfptBannerStart > Caution : This email originated from outside of Sony. > Do not click links or open any attachments unless you recognize the sender > and know the content is safe. Please report phishing if unsure. > ZjQcmQRYFpfptBannerEnd > > On 2023/08/09 00:20:42 Andrew Dennison wrote: > > > Hi Nuttx Dev, > > > > > > We are negotiating with the authors of the linux device driver for the > CTU > > > CAN FD IP core to it re-licenced from GPL to so the driver can then be > > > ported to Nuttx. > > > > Just a reminder: Apache policy prohibits GPL code, or GPL-derived code, > > from being included in any ASF project: > > > > https://apache.org/legal/resolved#category-x< > https://apache.org/legal/resolved#category-x> > > > > If there is *any* question about the license of incoming code, then you > > should ask the Legal Affairs Committee for advice, after reviewing the > > ASF policy on source headers: > > > > https://apache.org/legal/src-headers.html< > https://apache.org/legal/src-headers.html> > > > > Specific questions (i.e. about a specific body of code under license X > > that the project wants to incorporate) should be asked on Jira: > > > > https://issues.apache.org/jira/projects/LEGAL/issues< > https://issues.apache.org/jira/projects/LEGAL/issues> > > > > -- > > - Shane > > ASF Member > > The Apache Software Foundation > > > > > I've seen various licencing examples in the nuttx code base: but no high > > > level description that gives a definitive answer. For example there are > > > some cases where Authors are preserved and the code is BSD-2-Clause or > > > BSD-3-Clause (not Apache-2.0). > > > > > > We would appreciate some feedback on whether the proposal from Pavel > below > > > is acceptable or if any minor adjustments would help. > > > > > > Kind regards, > > > > > > Andrew Dennison > > > Chief Architect and Hardware Team Lead > > > MoTeC (A Bosch Company) > > > > > > On Tue, 8 Aug 2023 at 19:48, Pavel Pisa <p...@fel.cvut.cz<mailto: > p...@fel.cvut.cz>> wrote: > > > > > > > > > > > OK, consider driver code license and NuttX compatible. > > > > We need to discuss what will be actual variant and file > > > > headers text. I suggest > > > > > > > > // SPDX-License-Identifier: GPL-2.0+ OR BSD-2-Clause OR Apache-2.0 > > > > > > > > > /******************************************************************************* > > > > * > > > > * CTU CAN FD IP Core > > > > * > > > > * Copyright (C) 2015-2018 Ondrej Ille <ondrej.i...@gmail.com<mailto: > ondrej.i...@gmail.com>> FEE CTU > > > > * Copyright (C) 2018-2020 Ondrej Ille <ondrej.i...@gmail.com<mailto: > ondrej.i...@gmail.com>> self-funded > > > > * Copyright (C) 2018-2019 Martin Jerabek <martin.jerabe...@gmail.com > <mailto:martin.jerabe...@gmail.com>> > > > > FEE CTU > > > > * Copyright (C) 2018-2020 Pavel Pisa <p...@cmp.felk.cvut.cz<mailto: > p...@cmp.felk.cvut.cz>> FEE > > > > CTU/self-funded > > > > * > > > > * Project advisors: > > > > * Jiri Novak <jno...@fel.cvut.cz<mailto:jno...@fel.cvut.cz>> > > > > * Pavel Pisa <p...@cmp.felk.cvut.cz<mailto:p...@cmp.felk.cvut.cz > >> > > > > * > > > > * Department of Measurement (http://meas.fel.cvut.cz/< > http://meas.fel.cvut.cz/>) > > > > * Faculty of Electrical Engineering (http://www.fel.cvut.cz< > http://www.fel.cvut.cz>) > > > > * Czech Technical University (http://www.cvut.cz/< > http://www.cvut.cz/>) > > > > */ > > > > > > > > I am not sure if that is acceptable for NuttX mainline, but I do not > like > > > > process which stripped all information about real code authors when > > > > NuttX has been absorbed by Apache. The Copyright (C) statementscan be > > > > replaced > > > > by text "Authors list" if copyright of NuttX copy should be > transferred > > > > to Apache. But I would tend to keep list of authors who invested time, > > > > lot of it even from own spare one... > > > > > > > > > > > > > > > > > > -- > > > *MoTeC Pty Ltd* > > > > > > 121 Merrindale Drive > > > Croydon South 3136 > > > Victoria Australia > > > *T: *61 3 9761 5050 > > > *W: *http://www.motec.com.au<http://www.motec.com.au> < > https://www.motec.com.au/<https://www.motec.com.au/>> > > > > > > > > > -- > > > <http://www.facebook.com/motec.global< > http://www.facebook.com/motec.global>> > > > <http://www.youtube.com/user/MoTeCAustralia< > http://www.youtube.com/user/MoTeCAustralia>> > > > <https://www.instagram.com/motec_global/< > https://www.instagram.com/motec_global/>> > > > <https://www.linkedin.com/company/motec-global< > https://www.linkedin.com/company/motec-global>> > > > <https://twitter.com/motec_global<https://twitter.com/motec_global>> > > > > > > > > > -- > > > <https://www.motec.com.au<https://www.motec.com.au>> > > > > > > -- > > > > > > > > > Disclaimer Notice: This message, including any attachments, contains > > > confidential information intended for a specific individual and purpose > and > > > is protected by law. If you are not the intended recipient you should > > > delete this message. Any disclosure, copying, or distribution of this > > > message or the taking of any action based on it is strictly prohibited. > > > >
