On Wed, Feb 2, 2022 at 12:51 PM Mattia Verga <mattia.verga@xxxxxxxxxxxxxx> wrote: > > So, shall we just ignore the "all rights reserved" and only look at the license text? > > I'm reviewing a package [1] which has the same "problem" and it also carries a separate "all rights reserved" license file aside a BSD and an Apache license files... is it acceptable? It's extremely common in open source to see license notices coupled with copyright notices that include an "All rights reserved" statement. It doesn't mean anything. It's just an annoying habit rooted in pre-FOSS, pre-software copyright marking practices. I urge anyone reading this list who engages in open source development not to do it. But there's no point in treating it as a problem. On the other hand, suppose someone contributes a new source file to an upstream project that is licensed under, say, the Apache License 2.0, and they include a copyright notice with an "All rights reserved" statement but no license notice. That is most likely a problem for the following reason: Normally, in open source development, we don't see contributors including copyright notices without license notices in patches etc. (they might have no legal notices at all, which is by far the most common case, or they might have just a license notice, or they might have a copyright and license notice). Also, nowadays, sometimes "All rights reserved" without a FOSS or FOSS-like license notice is used to signal "I am not placing this material under a FOSS license, even though that's what I usually do" -- I typically don't see this in software but nonetheless it is a modern practice that affects how we should interpret "All rights reserved" in code. I hope this is helpful! Richard > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=2034758 > _______________________________________________ > legal mailing list -- legal@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to legal-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/legal@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure _______________________________________________ legal mailing list -- legal@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to legal-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/legal@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
