Decide on a machine readable way for licenses #9

New Issue

AliasAlreadyTaken · 2024-06-03T21:23:54+02:00

AliasAlreadyTaken commented

2024-06-03 21:23:54 +02:00

Apparently the open source world still has not decided on how to note licenses in a software package, especially when there is more than one. code and art and sounds and other media all come with their own license, all of those need to be added to the template and then referenced somewhere.

I propose we do it on the readme, which links to a licenses.md

The licenses.md would have a list of code (if more than one license on code is involved) and all the singular media and their licenses.

We also could add a license.json, but not sure if that is asking too much.

In any case it needs to note ALL licenses involved and prepare for more than one license in a machine readable way.

Apparently the open source world still has not decided on how to note licenses in a software package, especially when there is more than one. code and art and sounds and other media all come with their own license, all of those need to be added to the template and then referenced somewhere. I propose we do it on the readme, which links to a licenses.md The licenses.md would have a list of code (if more than one license on code is involved) and all the singular media and their licenses. We also could add a license.json, but not sure if that is asking too much. In any case it needs to note ALL licenses involved and prepare for more than one license in a machine readable way.

AliasAlreadyTaken referenced this issue from a commit

2024-06-04 01:40:35 +02:00

your-land/yl_template#9 Adds example licenses

AliasAlreadyTaken closed this issue

2024-06-04 01:40:43 +02:00

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/yl_template#9