~ Gary O'Neall [2020-01-27 19:38 +0100]: > For the SPDX documents, I would recommend making that part of the standard > release process. When new releases are published, you can publish a new > SPDX document for that release. This will probably require a bit of > tooling, some of which is available in open source at github.com/spdx.
As a side note, if you adopt the REUSE guidelines - so marking each file with copyright and licensing information using SPDX tags - creating an SPDX document will be just a matter of one command with the helper tool: `reuse spdx` For more information: https://reuse.software Best, Max -- Max Mehl - Programme Manager - Free Software Foundation Europe Contact and information: https://fsfe.org/about/mehl | @mxmehl Become a supporter of software freedom: https://fsfe.org/join -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1289): https://lists.spdx.org/g/spdx/message/1289 Mute This Topic: https://lists.spdx.org/mt/70149225/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/spdx/leave/2655439/1698928721/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
