Incorrect/mixed licensing headers in some source files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) |
Fix Released
|
Medium
|
OpenERP's Framework R&D |
Bug Description
IN 7.0 there are license conditions where I cannot understand the effective license.
In the first example a AGPL license block is pasted above a the original LGPL2.1+ license. What the is effective license for the file in this case (AGPL 3.0+ ? LGPL 2.1+)? This is for
- report/
- report/
In the next example the license roughly says "some portions of this file is AGPL2.1+, some portions are LGPL 2.1+". What is the effective license in this case? This is about a large number of files, see the "AGPL (v2.1 or later) LGPL (v2.1 or later)" header in the attachment. One example is
- .../openerp_
I get the impression that OpenERP, SA have tried to relicense the original work in these cases. I'm by no means a lawyer, but it looks like these attempts has not been done in a proper way, and that thus any distribution of these files are problematic from a legal point of view(?). For Fedora, this is certainly is problem, and will most likely block the packaging of version 7.0.
I suggest OpenERP, SA sticks to the original LGPL 2.1+ license adds it's copyright notice to the existing licerse block. Or contacts the original author to get a permission to relicense completely. Or possibly clarifies the license in some other way.
Here are lso a large number of files without license clause. GIven the complicated licensing with at least three licenses in use, this also makes it harder to understand the legal status of the package. See attachment.
summary: |
- Bad licensing + Incorrect/mixed licensing headers in some source files |
Opps right comment in wriong bug. Please discard comment #2