[this is also available as https://gist.github.com/zvr/c852b4a560ac2c67885c473034cd4a93] # FOSDEM 2023 - SBOM devroom info and CfP ## Overview [FOSDEM] is one of the world's premier meetings of free s

McCoy, Your example was about snippets in files, but this also happens one level up: If there are some files under License-A and some files under License-B, how do you express the license of a package

May I propose something like github.com/spdx/help since “docs” covers a lot more things (even the specification itself). +1 on being a new, separate location. -- zvr

I guess it will… The OpenChain one took a couple of months to appear, though, so I don’t know how quickly this gets updated. -- zvr

Hi Christian, Thanks for reaching to the SPDX project! As this has purely to do with licenses, it may be better addressed to the legal working group at spdx-legal@.... Alternatively, feel f

Rewriting this to a simpler setup is definitely a valid idea for a future Community Bridge / GSoC project. 😉 -- zvr

The good folks at FSFE maintain a wiki page with Free Software alternatives: https://wiki.fsfe.org/Activities/FreeSoftware4RemoteWorking I should point out that in the SPDX calls we don't actually use

This license is empty: http://spdx.org/licenses/NLOD-1.0.html I assume because the reference (at least in the Excel file) is to “NLOD-1..txt” instead of “NLOD-1.0.txt”. -- zvr