On Fri, Oct 29 2021 at 11:44, Luis Chamberlain wrote: > --- /dev/null > +++ b/LICENSES/dual/copyleft-next-0.3.1 > @@ -0,0 +1,237 @@ > +Valid-License-Identifier: copyleft-next-0.3.1 > +SPDX-URL: https://spdx.org/licenses/copyleft-next-0.3.1 > +Usage-Guide: > + This license can be used in code, it has been found to be GPLv2 compatible > + by attorneys at Redhat and SUSE, however to air on the side of caution, air ? > + it's best to only use it together with a GPL2 compatible license using "OR". This paragraph is not really understandable for Joe Developer. copyleft-next-0.3.1 is explicitly compatible with GPLv2 (or later) and can therefore be used for kernel code. Though the best and recommended practice is to express this in the SPDX license identifier by licensing the code under both licenses expressed by the OR operator. Hmm? > + To use the copyleft-next-0.3.1 license put the following SPDX tag/value > + pair into a comment according to the placement guidelines in the > + licensing rules documentation: > + SPDX-License-Identifier: GPL-2.0 OR copyleft-next-0.3.1 > + SPDX-License-Identifier: GPL-2.0-only OR copyleft-next 0.3.1 > + SPDX-License-Identifier: GPL-2.0+ OR copyleft-next-0.3.1 > + SPDX-License-Identifier: GPL-2.0-or-later OR copyleft-next-0.3.1 Please don't propagate the GPL-2.0 and GPL-2.0+ tags. They are outdated (still valid) in the SPDX spec, which reminds me that I should update the relevant documentation... Thanks, tglx
