legal November 2017

legal@lists.fedoraproject.org

15 participants
13 discussions

Dealing with patented code included in tarballs
by Igor Gnatenko 10 Nov '17

10 Nov '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, I maintain some package and it used to include some patented stuff before. Now I sanitize tarball, but what's the deal with old versions? - -- - -Igor Gnatenko -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAloFs2YACgkQaVcUvRu8 X0zJsxAAonqdBKx8eKt4pnYHZc323DNWJQ4H11JPwxmFJBk2/GGwTT8veMo9znn6 Mk3cofDmJttvom/DBM2gequjVOtiGgqlH0a7M4pXxmNXy4+cU2ktjaduKTmgT+th RJL8qjvp3Wpwz/SoutwJN3DCJ1B/7fEjtaFXLXXvmNNqClSlkYGr2T3OWUfIp0z9 hAtVCsPqh625w6HdeSpISxxRfkWNtWao6d5kIA2+Cmce+odT+oPdZhc+WNLzBTpd //EHEeXoOHJxhWcTJOVO9d8Civ+0+1jh6gTGWuy8wXEe0DiSiwG/XY1Gx6jeSeBH 01xzPs2Qo6Fn/VMbwX7SH0UC8IUshuWVhhx4EqI/KdWj+a2+XKk+jnxa70wVpCIb b0uHJW0PyRxN+K+8bYej98e5u/6GSP1O+Ftf44DKlEzwf+32tiMqqTHxdHww8/z1 gMxP7jFzeeFvf3pQB4ctpzOMnRlGhIX3X1oWkgHXYiQLfcMJC7HGfpIUreWz89vQ hRRTdF/vnT3veSXR/2SHD9pN1vzOrZY4dDmX3T6tIE1iFbksDkD0s2srrEYBdMtC MiwiXTRgl3mlFiRO6X3r29NnvQOnDI3wXjLcQmoWV7TrageHlKcjraIw5qaNxQs9 5uRaxY8Z5GFA2LOY87JDPuP2PY/RlelvfDqZYm5ExXDofav2LJ8= =+QpI -----END PGP SIGNATURE-----

2 1

CDDL 1.0 and 1.1
by Fernando Nasser 06 Nov '17

06 Nov '17

Hi all, We have this entry in our good software licenses table: Common Development Distribution License CDDL Yes *NO* *NO* https://fedoraproject.org/wiki/Licensing/CDDL But there are now two CDDL licenses: Common Development and Distribution License 1.0 <https://spdx.org/licenses/CDDL-1.0.html> Common Development and Distribution License 1.1 <https://spdx.org/licenses/CDDL-1.1.html> Please note that the CDDL 1.1 is not yet in the OSI license list: https://opensource.org/licenses/alphabetical But it is already in the SPDX list: https://spdx.org/licenses/ How should I proceed to get the CDDL 1.1 added to our list? Should we make the new short name "CDDL 1.1" and leave the 1.0 one as just "CDDL" or should we make it "CDDL 1.0" so packages using that eventually get the License tag updated? Regards to all, Fernando

2 2

Antlr license
by Fernando Nasser 06 Nov '17

06 Nov '17

Hi guys, Our antlr package has "Public Domain" in the License tag. However the author does add some conditions for credit being given, headers in source files be kept, etc. Please see the LICENSE.txt and README.txt files. This is what probably caused SPDX to create a specific "license" denomination for this: ANTLR Software Rights Notice <https://spdx.org/licenses/ANTLR-PD.html> |ANTLR-PD| Note: There is no reference to this license or anything specific to Antlr in OSI. Although it is true that it is public domain, we need to make sure his credit and header conditions are met. Should we add an Antlr license to our table and change the package to use it on the next update? Should we use the SPDX "ANTLR Software Rights Notice" and as short name "ANTLR PD"? Or should we ignore all these details and just keep it as "Public Domain" ? Contents of LICENSE.txt for your convenience: ------------------------------------------------------------- SOFTWARE RIGHTS ANTLR 1989-2006 Developed by Terence Parr Partially supported by University of San Francisco & jGuru.com We reserve no legal rights to the ANTLR--it is fully in the public domain. An individual or company may do whatever they wish with source code distributed with ANTLR or the code generated by ANTLR, including the incorporation of ANTLR, or its output, into commerical software. We encourage users to develop software with ANTLR. However, we do ask that credit is given to us for developing ANTLR. By "credit", we mean that if you use ANTLR or incorporate any source code into one of your programs (commercial product, research project, or otherwise) that you acknowledge this fact somewhere in the documentation, research report, etc... If you like ANTLR and have developed a nice tool with the output, please mention that you developed it using ANTLR. In addition, we ask that the headers remain intact in our source code. As long as these guidelines are kept, we expect to continue enhancing this system and expect to make other tools available as they are completed. The primary ANTLR guy: Terence Parr parrt(a)cs.usfca.edu parrt(a)antlr.org

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

legal November 2017