Topics

Migration to SPDX


Ashok Madugula
 

Hi  :

We are planning to migrate to SPDX Licenses.

If we are using general MIT  License . Can we replace the existing license file with SPDX Identifier  ?

Do we need to generate new  SPDX Document and publish them regularly   ?

 

Regards

Ashok Madugula

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


Gary O'Neall
 

Hi Ashok,

 

You can keep the existing license file in the distribution but we recommend adding SPDX identifiers to the source files – see https://spdx.org/ids for more information.

 

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. 

 

Let us know if you have any other questions or would like more details.

 

Regards,

Gary

 

From: spdx@... <spdx@...> On Behalf Of Ashok Madugula
Sent: Sunday, January 26, 2020 11:18 PM
To: spdx@...
Subject: [spdx] Migration to SPDX

 

Hi  :

We are planning to migrate to SPDX Licenses.

If we are using general MIT  License . Can we replace the existing license file with SPDX Identifier  ?

Do we need to generate new  SPDX Document and publish them regularly   ?

 

Regards

Ashok Madugula

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.


Max Mehl
 

~ 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