https://bugzilla.redhat.com/show_bug.cgi?id=2304835 --- Comment #9 from Richard Fontana <rfontana@xxxxxxxxxx> --- Okay, I think you may be misunderstanding what is said here https://nasa-pds.github.io/collaborate/jpl-pds-oss-policy.html#exemptions unless I am myself misunderstanding it. I read this as saying "The general policy now is to use the Apache License 2.0, but this policy does not apply to the SPICE toolkit (for now)". You seem to be interpreting this (plus the SPICE toolkit terms) as saying "Permitted modified versions of the toolkit are under the Apache License 2.0" but I don't see any basis for that conclusion. In a comment above you say "I have obtained explicit permission from the NAIF manager to package CSPICE for Fedora. The packaging is necessarily a modification of the original distribution (both for the SRPM and the RPMS). As such the Fedora packages should be exempt from the upstream licensing exception entirely, and can be further distributed with the unmodified Apache 2.0 license." But it seems to me that if your package is truly under the Apache License 2.0 then it should be possible for a user to modify your package in such a way that they end up with something identical to the original distribution. If that is not the case, that would suggest that the license of your package is something like (in pseudo-SPDX-expressions) "Apache-2.0 WITH AdditionRef-SPICE-toolkit-SunRPC-type-restriction" which would not be allowed for Fedora since it's not an open source license. The SunRPC principle is that licenses that contain prohibitions on distribution in isolation are not considered open source. The CSPICE terms say: "Redistribution of the unmodified SPICE Toolkit, such as from a mirror site, is prohibited without prior, written clearance from the NAIF manager. However, including the SPICE Toolkit modules (source and object code), documentation, and relevant SPICE Toolkit programs and allied User Guides as part of a package supporting a customer-built SPICE-based tool is entirely appropriate. This includes providing a new 3rd party interface to the SPICE Toolkit, subject to the relevant rules listed elsewhere on this webpage." Which seems to me to be a variant on a SunRPC restriction. Obviously if NAIF decides in the future to conform to what appears to be the more enlightened present-day JPL open source policy and not insist on holding on to this pre-open-source approach, this can be revisited. -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2304835 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202304835%23c9 -- _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
