https://bugzilla.redhat.com/show_bug.cgi?id=1559699 Tom "spot" Callaway <tcallawa@xxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tcallawa@xxxxxxxxxx Blocks| |182235 (FE-Legal) --- Comment #2 from Tom "spot" Callaway <tcallawa@xxxxxxxxxx> --- So... the same legal issue which derailed 499875 is present here. We've got two conflicting license statements: >From README.txt "libdasm is public domain software. You can do whatever you like with it." But, the code (and the top of README.txt) says: (c) 2004 - 2006 jt / nologin.org If something is in the Public Domain, it means that the author has abandoned their copyright on a work. But, if you have a (c) statement, then they are asserting... copyright on the work. They do not have to make that statement to have copyright (thanks to the Berne Convention), but by having it present, it effectively negates the public domain declaration, leaving everyone (except the copyright holder) with no license terms on the work. There are several ways to fix this. I'll list them in the order of preference: * Relicense the work under an established open source license. In bz499875, the upstream appeared to be willing to relicense under BSD, which would work fine. This also resolves the international complexity and ambiguity which Public Domain works have. * Switch to a Creative Commons Zero license, which is intended to resolve the Public Domain issues by enabling a license when it is not possible to abandon copyright entirely. * Remove all of the (c) statements from the codebase and README, and replace them with the public domain statement, making it clear that copyright is abandoned on the work. I filed an issue in the upstream github repo (https://github.com/jtpereyda/libdasm/issues/3), hopefully that will be a good start in getting this fixed. As is, I'm blocking this against FE-Legal. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=182235 [Bug 182235] Fedora Legal Tracker -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
