issues to review 9/8 edition
Thanks to Steve, Madhuri, and Shalini for joining the working session. It is great to have new people taking the time to understand how the process works, so they can contribute! Talking to Madhuri and Shalini also made me realize that we probably need some form of “annotated” inclusion guidelines… will try to work on that after this release! Please help keep moving the ball forward! Here is tonight’s installment of issues that need review! flex 2.6.4 - https://github.com/spdx/license-list-XML/issues/2104 lost - https://github.com/spdx/license-list-XML/issues/2100 As promised, I did a “bulk” review of the tex-live licenses. I created a Google doc in order to be able to view all the text in one place and put notes as to how I searched. You can see the Google doc here: https://docs.google.com/document/d/1xqSwTfJJ7btkhbblrIAZxOxv0iZPmAMGar9rU7DLKC8/edit These 3 are unique enough, I think they needed to be added separately. Need one more person to agree :) https://github.com/spdx/license-list-XML/issues/2068 https://github.com/spdx/license-list-XML/issues/2069 https://github.com/spdx/license-list-XML/issues/2071 There are 3 variations on “texlive-Arseneau” - I’m inclined to try to use markup to accommodate 2 of them assuming that is not too confusing, although one has a bit of a concern to me in doing so. Could use some input on that idea: https://github.com/spdx/license-list-XML/issues/2088 and https://github.com/spdx/license-list-XML/issues/2088 (it’s easier to see the differences in the Google doc) As mentioned in my previous email, I’ll have an update on the “HPND” variants (of which we now have 8!) after I do an initial review of them in bulk. Thanks! Jilayne > On Sep 7, 2023, at 10:27 PM, J Lovejoy wrote: > > Thanks to Ria for making some headway! > > In preparation for tomorrow (Friday’s) working session at 2:30pm Eastern > time, here is a list of issues to review: > > > Need initial review: > > > Unicode-3 - https://github.com/spdx/license-list-XML/issues/2105 > flex 2.6.4 - https://github.com/spdx/license-list-XML/issues/2104 > lost - https://github.com/spdx/license-list-XML/issues/2100 > > I also am trying to look at the bunch of tex-live licenses in bulk - update > on that tomorrow. > > I have also noticed that there are a number of HPND variants. The > license-diff and License Check tools have a hard time spotting these because > the HPND license itself has so much potential variation. I made a new label > (for the time being) to try and group anything that resembles HPND and will > look at those in bulk. I’m hoping out of that will come some guidance on this > particular flavor, as we have been seeing a lot of these. > > Thanks and look forward to a productive session tomorrow!! > > Jilayne > >> On Sep 6, 2023, at 9:41 PM, J Lovejoy wrote: >> >> Revised list below. Please have a look and comment as to acceptance or not >> to the SPDX License List on as many as possible >> prior to our (new!) quarterly working session on Friday :) >> >> There are more issues than these, but this is a start! >> >> Note: Fedora has 31 issues that are “blocked” on SPDX - meaning, Fedora >> package maintainers are waiting on SPDX-legal to determine acceptance for >> the SPDX License List. Please contribute to the SPDX License List, by >> helping make it representative of much software that exists and that we all >> use! > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3459): https://lists.spdx.org/g/Spdx-legal/message/3459 Mute This Topic: https://lists.spdx.org/mt/101251538/21656 Group Owner: spdx-legal+ow...@lists.spdx.org Unsubscribe: https://lists.spdx.org/g/Spdx-legal/leave/2655900/21656/2011363115/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: issues to review 9/7
One slight comment on Unicode 3 (full disclosure: I helped draft it and have submitted it to OSI for approval; it is still in the OSI discussion loop as part of the approval process). The canonical version (which I think is the version SPDX should be using here) uses the generic attribution notice: Copyright © The version you have linked to is the one that Unicode is using for its own code, in which they have inserted their own copyright notice: Copyright © 1991-2023 Unicode, Inc. So I’d suggest using the former, rather than the latter, for SPDX. For anyone wanting to review that license (don’t think I can as it’s a bit of a conflict), I have attached a redlined version of the new v3 license versus the old version (the 2015 version, there’s a 2016 version that didn’t go through OSI) with the (somewhat unwieldy) SPDX identifier of https://spdx.org/licenses/Unicode-DFS-2015.html From: Spdx-legal@lists.spdx.org On Behalf Of J Lovejoy Sent: Thursday, September 7, 2023 9:27 PM To: SPDX-legal Subject: issues to review 9/7 Thanks to Ria for making some headway! In preparation for tomorrow (Friday’s) working session at 2:30pm Eastern time, here is a list of issues to review: * ssh-keyscan - https://github.com/spdx/license-list-XML/issues/2077 (needs one more review) * if it breaks - https://github.com/spdx/license-list-XML/issues/2057 (match input) * glibc startup code exception - https://github.com/spdx/license-list-XML/issues/2055 (updated info on matching, needs further input) * BSD advert varia nt- https://github.com/spdx/license-list-XML/issues/2066 (accepted, need input on naming) * INBL - https://github.com/spdx/license-list-XML/issues/2098 (needs one more review and input on naming) * iPXE-UBDL-exception - https://github.com/spdx/license-list-XML/issues/2043 (license or exception - need another opinion) * sea file-openssl-exception - https://github.com/spdx/license-list-XML/issues/2080 (markup question) Need initial review: * Ferguson-Twofish - https://github.com/spdx/license-list-XML/issues/2117 * x11 fonts - https://github.com/spdx/license-list-XML/issues/2115 * Unicode-3 - https://github.com/spdx/license-list-XML/issues/2105 * flex 2.6.4 - https://github.com/spdx/license-list-XML/issues/2104 * lost - https://github.com/spdx/license-list-XML/issues/2100 * I also am trying to look at the bunch of tex-live licenses in bulk - update on that tomorrow. I have also noticed that there are a number of HPND variants. The license-diff and License Check tools have a hard time spotting these because the HPND license itself has so much potential variation. I made a new label (for the time being) to try and group anything that resembles HPND and will look at those in bulk. I’m hoping out of that will come some guidance on this particular flavor, as we have been seeing a lot of these. Thanks and look forward to a productive session tomorrow!! Jilayne On Sep 6, 2023, at 9:41 PM, J Lovejoy mailto:opensou...@jilayne.com> > wrote: Revised list below. Please have a look and comment as to acceptance or not to the SPDX License List on as many as possible prior to our (new!) quarterly working session on Friday :) There are more issues than these, but this is a start! Note: Fedora has 31 issues that are “blocked” on SPDX - meaning, Fedora package maintainers are waiting on SPDX-legal to determine acceptance for the SPDX License List. Please contribute to the SPDX License List, by helping make it representative of much software that exists and that we all use! -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3458): https://lists.spdx.org/g/Spdx-legal/message/3458 Mute This Topic: https://lists.spdx.org/mt/101231184/21656 Group Owner: spdx-legal+ow...@lists.spdx.org Unsubscribe: https://lists.spdx.org/g/Spdx-legal/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=- Unicode License v3 compare Unicode Inc. License Agreement - Data Files and Software.pdf Description: Adobe PDF document Unicode License v3 compare Unicode Inc. License Agreement - Data Files and Software.odt Description: application/vnd.oasis.opendocument.text
