Reminder: Change Proposal on custom license exceptions / modifiers / additions
Steve Winslow
Hello spdx-legal and spdx-tech team lists, As a reminder, following from the joint teams meeting in January, there is a pending Change Proposal [1] regarding whether and how to add the ability to express custom license "exceptions" (or "modifiers", or "additions") in SPDX license expressions. This is one of the primary open items to be decided upon in connection with the draft SPDX 3.0 licensing profile [2]. So if the licensing profile will include support for some form of this for 3.0, we'll need to conclude on what and how it will be implemented. If you have thoughts, please review that Change Proposal thread and the linked proposed PRs, and weigh in on that issue thread with your input. Best, Steve |
|
Steve Winslow
Hello SPDX legal and tech teams, This Thursday, April 27th at 12:00 EDT, during our regularly scheduled legal team meeting [1], we will be discussing and finalizing on the details of the change proposal for custom license "additions" [2]. This follows from the previous meeting on January 12 where this was discussed. [3] Based on the discussion in the change proposal thread, I am seeing greatest consensus for the use of `AdditionRef-` as the prefix for custom 'additions' to license text, as reflected in Alexios's PR at [4]. As previously agreed, the SPDX Exceptions List itself [5] would continue to be limited to solely exceptions to license conditions / additional permissions. `AdditionRef-` as a prefix would then be used for custom identifiers that are _not_ on the Exceptions List, to represent any additional text added to a license which is not a standalone license itself. I would ask that folks who will attend the April 27th meeting please review the threads linked below so that we can finalize on the decision during that call. Best, Steve
|
|
Karsten Klein
Hi all,
since we are discussing [2] I would like to keep another change proposal not too secret. In [6] I’ve written up a slightly more extensive change proposal that would also cover [2]. In this change proposal I’m extending the concept of a license modifier to cover different types of modifiers organized in categories (exceptions being one out of currently four).
See also the yet management amount of discussion in issue [7].
Perhaps the change proposal offers a perspective that is worthwhile to consider during the discussions on Thursday.
Please also mind the not yet merged PR [8]. It provides more examples that apply modifiers to convey license application/usage specifics.
Kind regards, Karsten
[1] https://github.com/spdx/meetings#legal-team-meetings [2] https://github.com/spdx/change-proposal/issues/4 [3] https://github.com/spdx/meetings/blob/main/legal/2023-01-12.md [4] https://github.com/spdx/spdx-spec/pull/839/files [5] https://spdx.org/licenses/exceptions-index.html
[6] https://github.com/spdx/change-proposal/blob/main/proposals/Modifiers.md [7] https://github.com/spdx/change-proposal/issues/6
From: <Spdx-legal@...> on behalf of Steve Winslow <swinslow@...>
Hello SPDX legal and tech teams,
This Thursday, April 27th at 12:00 EDT, during our regularly scheduled legal team meeting [1], we will be discussing and finalizing on the details of the change proposal for custom license "additions" [2]. This follows from the previous meeting on January 12 where this was discussed. [3]
Based on the discussion in the change proposal thread, I am seeing greatest consensus for the use of `AdditionRef-` as the prefix for custom 'additions' to license text, as reflected in Alexios's PR at [4]. As previously agreed, the SPDX Exceptions List itself [5] would continue to be limited to solely exceptions to license conditions / additional permissions. `AdditionRef-` as a prefix would then be used for custom identifiers that are _not_ on the Exceptions List, to represent any additional text added to a license which is not a standalone license itself.
I would ask that folks who will attend the April 27th meeting please review the threads linked below so that we can finalize on the decision during that call.
Best, Steve
On Tue, Mar 28, 2023 at 3:01 PM Steve Winslow via lists.spdx.org <swinslow=gmail.com@...> wrote:
|
|
J Lovejoy
Hi all,
toggle quoted message
Show quoted text
I’ve added some comments to https://github.com/spdx/change-proposal/issues/4 and am looking forward to coming to a conclusion on our first official use of the Change Proposal process at tomorrow’s meeting (and apologies to Alexios that its taken a bit longer than we intended). That said, I want to be clear that we will come to a conclusion at tomorrow’s meeting - for the reason already stated and because this is key to progressing 3.0!! As for Karsten’s Change Proposal - I have commented there and will repeat here: I’d really like to consider and conclude on Alexios’s first. Then proceed to consider Karsten’s. While I realize there is some overlap, part of the point of implementing the Change Proposal process was to have concrete proposals and conclusions. As such, I think we should honor each proposer by giving their proposals due and separate consideration. Thanks, Jilayne
|
|