On 05/05/2015 03:52 PM, László Böszörményi (GCS) wrote: > This is not authoritative. For example someone could sent an email to > Ullrich with his/her patch. As it was not commited by the contributor > but Ullrich, the person's identity is lost.
Well, then Ullrich didn't use the version control system he was using properly. At least in git, you always differentiate between committer and author and therefore the authorship is always kept. > But well, the commit log can be a good starting point. May you Oliver > handle this? Oliver asked me do it instead but he made a good suggestion to look at the file cc65-2.13.3/doc/CREDITS from ftp://ftp.musoftware.de/pub/uz/cc65/cc65-sources-2.13.3.tar.bz2. Furthermore, there is a file packages/debian/copyright with the following interesting statement: =================================snip================================= This is the original compiler copyright: -------------------------------------------------------------------------- -*- Mode: Text -*- This is the copyright notice for RA65, LINK65, LIBR65, and other Atari 8-bit programs. Said programs are Copyright 1989, by John R. Dunning. All rights reserved, with the following exceptions: Anyone may copy or redistribute these programs, provided that: 1: You don't charge anything for the copy. It is permissable to charge a nominal fee for media, etc. =================================snip================================= In acknowledgment of this copyright, I will place my own changes to the compiler under the same copyright. However, since the library and all binutils (assembler, archiver, linker) are a complete rewrite, they are covered by another copyright: =================================snip================================= (text of the zlib license) I will try to contact John, maybe he is also willing to place his sources under a less restrictive copyright, after all these years:-) =================================snip================================= Thus, the code with the problematic license was always in the compiler part only. And for that, we can actually compare the current sources with the old sources: http://umich.edu/~archive/atari/8bit/Languages/Cc65/cc65-UNIX.tgz =================================snip================================= Additionally, I also have the following statement from Ullrich which I will translate from German: Der größte Teil der Software unterliegt bereits der zlib Lizenz. "Größter Teil" heisst, alle Tools mit Ausnahme des Compilers. Beim Compiler kann mein Code sowohl mit der alten (JRD) als auch mit der zlib Lizenz verteilt werden. Vom JRD Code übrig sind eigentlich nur noch ein paar Zeilen Code in den Dateien expr.c (bzw. expr.h), wegen denen der Compiler die alte Lizenz hat. Am einfachsten wäre es, wenn John seinen Code bzw. den der Dateien expr1.c, expr2.c und expr3.c die zlib stellt. Falls er das nicht will kann man den Code wahlweise gemischt lizensieren, oder sich tatsächlich die Mühe machen, den Rest alten Codes von John rauszuwerfen. =================================snip================================= Translation: The largest portion of the code is already licensed under the Zlib license. "Largest portion" means all tools with the exception of the compiler. As for the compiler, my code can be distributed both under John's old license as well as the Zlib license. The remaining parts from John's code are basically just a few lines in the files expr.c (expr.h respectively) which is why the compiler was still distributed under John's original license. Thus, the simplest thing would be if John just relicensed all of his code or the code in the files expr1.c, expr2.c and expr3.c under the Zlib license. If John doesn't like that, it may also be possible to use a mixed license for the code or just get rid of John's code altogether. =================================snip================================= So, according to Ullrich, who has been maintaining and developing the cc65 code for the longest time, all that is needed to be able to redistribute the code under the free Zlib license is to ask John for permission to put his contributions under the Zlib license as well which is what I did and for which I received a positive answer from John. Who if not Ullrich is authoritative to give such a statement regarding the license of the code. He wrote - by far - the largest portions of the code and supervised all contributions. I am pretty sure we can take his word on that. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
