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 SPDX-License-I

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 that le

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 h

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 without.

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 com

LicenseRef is a good escape valve, even for the Free Licenses that aren't yet part of SPDX, or that are marginal cases until they can be prompted to full SPDX identifiers. It's also a good way to coll

I would suggest, though, that if we do this we strongly discourage people from using these identifiers for the 'copyright + SPDX-Identifier but no boilerplate' license scenarios. Since Fedora--, etc i

Sure. SPDX arouse as a way to cope with the variations on different licenses by providing a set of templates, with variations, to match. Since these variations had no legal differences, this was viewe

That was my plan, but I will have to do it next time. I'm fighting internet issues and since comcast is involved, it's looking like it is going to take a while. Warner

I'll give an update on FreeBSD's use of SPDX next time. Work has been unexpectedly busy so I've not had time to prepare. Warner

I wonder why they are using the Caldera license? Did they harvest these files from the 7th Edition of Unix, or did Sun license these and Caldera made them put this license on things? The version 7 /bi

I've been grappling with this in the FreeBSD project. I'll share my perspective. There's two parts to that advice. The first is to include the standard boilerplate text to invoke the license ("the sta

Right. This doesn't answer my question about their heirloom /bin/sh. Was it from Caldera or was it from Sun? And why did they drop the intro text? Warner

I'm ready to go if there's space in the agenda. My rehearsal of the talk clocks in at about 15 minutes, though I could trim this a bit because it's heavy on history to try to provide the full context

Perhaps we should recommend that any policy about the license marking of files should address this. FreeBSD's policy will likely state that the actual boiler plate license text in the file is controll

The plan for FreeBSD is to say that when there's an SPDX-License-Identifier: and no other grant of license, it should be construed (right word?) to include that identifier (eg MIT) from /usr/share/lic

There's no Linux drm code in FreeBSD proper. Certainly none with the new-style having the only SPDX-License-Identifier: tags (there's a few stragglers from some ancient drm implementation used only on

I'll point out that the variations are an enormous pain in the ass for FreeBSD and create more uncertainty and compliance issues not less. If I don't reproduce every single license in the tree, verbat

I agree here. I think semvar's notions are an imperfect fit for the nature of the license repo. We've selected major number to indicate a format (which one could argue is the semantic element that cou

Are you allowed to do that without it becoming an AND? You can't just change the terms w/o permission like that I'd imagine... And I'm not sure how it would generalize... Warner