Hi all, I just made a couple PRs to improve some of our documentation in the Github repo as per prior discussions. It'd be great to get some eyeballs on that and comments as to

Hello SPDX legal team, The next regularly-scheduled SPDX legal team meeting will be today, Thursday, April 15, at 9AM PDT / noon EDT. For today's call, we will be reviewing the issues currently tagged

Hi Warner, ~ Warner Losh [2021-04-02 19:03 +0200]: Thanks @Sebastian for bringing up REUSE! Indeed, I concur that it's a worthy goal for FreeBSD. It reminds me a bit of KDE's story. The project also

Thanks for the feedback. I'll take a look at this. I did have one question about REUSE. At one point it says: "To implement this method, each plain text file that can contain comments MUST contain

Dear Warner, I've read the policy draft you've written; clearly you have given this lots of thought already. I'd like to offer my take on it: The policy seems really similar to the REUSE standard

Hi Warner, Thanks for sharing this. It looks like a good, detailed way to document how the SPDX license identifiers will work for FreeBSD. I've seen several projects implement SPDX identifiers without

Greetings, The FreeBSD project is planning on expanding our use of the SPDX-License-Identifier. Currently, all files have the full license text. We have a mix of files with SPDX ID and those

Hello SPDX legal team, The next regularly-scheduled SPDX legal team meeting will be today, Thursday, April 1. It will be at 9AM PDT / noon EDT, following the SPDX general meeting one hour

Hello SPDX tech and legal teams, I've added a PR with an initial, incomplete / WIP draft of the Licensing profile for the SPDX 3.0 spec, at: https://github.com/spdx/spdx-spec/pull/503. I'm hoping we

As a single data point, we (Intel) use the mentioned: # SPDX-License-Identifier: MIT LICENSE = "GPLv2 & bzip2-1.0.4" under the understanding that the comment "SPDX-License-Identifier" applies only

Greetings, As discussed at the March 18th meeting, it's time to review our FAQ. I've created a google doc for people to make suggestions for improved wording, flagging areas that are unclear, etc. I

Hi Richard,

This is informative, and we are mindful of this history. Yea. I saw that. Things are close here. U-Boot wasn't much help. They seem to have made the change without having some kind of document

We don't have anything indicating the license of the metadata other than the top level license files so I'd have hoped the current situation was at least clear, LICENSE (and LICENSE_<packagename>)

Hello SPDX legal team, The next regularly-scheduled SPDX legal team meeting will be today, Thursday, March 18. It will be at our usual time of 9AM PDT / noon EDT. Note that the US is now on Daylight

Hi Richard:

Hi, I wondered if I might seek advice/opinions on a dilemma Yocto Project is facing with license identifiers. First, some background. We build software components from source and  combine them

Hi Warner: See some comments below. Hi Thomas: This is FYI as you may be able to provide some insights and recommendations based on the Linux kernel journey towards SPDX that could help Warner and

Greetings, I have a ton of questions about how a project can go about doing this. I'm looking at doing whatever it would take to create a framework so that the FreeBSD project could use

Hello all, The version 3.12 release of the license list is now tagged and live at https://spdx.org/licenses. 10 new licenses were added to the