Add Licenses

[maxwolfs]

Signed-off-by: maxwolfs mail@maxwolfs.com

closes #3

[itrich]

I recommend to not use the CC license for the code parts within this repository. Either we find a suitable software license (e.g. the same used by the Docsaurus project) or we add two licenses: one for creative content, one for code.

[maxwolfs]

I recommend to not use the CC license for the code parts within this repository. Either we find a suitable software license (e.g. the same used by the Docsaurus project) or we add two licenses: one for creative content, one for code.

You're totally right. I have corrected it.

[itrich]

I'm still struggling to find the best way of maintaining multiple license files within one repository. IMHO the best approach is the one suggested here (and quoted from the SPDX documentation): https://softwareengineering.stackexchange.com/a/371435

Thus, we should have one LICENSE file that makes it clear to visitors how the content of this repository is licensed. You can note something like

The content of this repository is published under multiple licenses.
All files within `docs` are licensed under [CC-BY-SA 4.0](LICENSE-CC-SA-BY.md). 
All source code is licensed under the [MIT](LICENSE-MIT.md) license.

SPDX-License-Identifier: MIT AND CC-BY-SA 4.0

And then add the unmodified license files as LICENSE-CC-BY-SA.md and LICENSE-MIT.md.

See also https://codeberg.org/Community-Square/pages/pulls/4 for reference and https://spdx.github.io/spdx-spec/using-SPDX-short-identifiers-in-source-files/#e4-representing-multiple-licenses.

Sidenote: We should find a consistent way of handling those cases within the community and apply this to ALL our repositories. This will become even more important as soon as we start to use @oss-review-toolkit.

[maxwolfs]

@itrich

Good point. I have found this blog post by GitHub regarding the issue of multiple Licenses within one repository: LINK

I have also made an exmaple repository to see how it works which you can see here: LINK

As they have build a feature to find multiple licenses automatically, I would suggest to use it as it is easy to use. Nevertheless I added your proposed also to the Readme.md to be as declarative as possible.

[itrich]

@itrich

Good point. I have found this blog post by GitHub regarding the issue of multiple Licenses within one repository: LINK

I have also made an exmaple repository to see how it works which you can see here: LINK

As they have build a feature to find multiple licenses automatically, I would suggest to use it as it is easy to use. Nevertheless I added your proposed also to the Readme.md to be as declarative as possible.

This looks good! Thank you for letting me learn something new 😄

[itrich]

Can you please capitalize LICENSE-docs? My inner monk is dying 😂

[maxwolfs]

Can you please capitalize LICENSE-docs? My inner monk is dying 😂

You are right, I have totally forgotten :D