Licensing information missing #5
tessel
ijohn
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi!
I think it is good practice to indicate under which license the different files in a repo are. The simplest would be to add a LICENSE file if all content is under the same license; otherwise more elaborate schemes like REUSE would be more appropriate (whereby compliance should then be ensured via pre-commit hooks).
Somewhat complicating in this case is, that the (JSON) content about the different NGI0 projects is part of the code (see also #7), so I am not quite sure how to differentiate between the code and the content (which might be under different licenses).
What do you think is the best way forward for us?
Hello, I think that we can easily add a global LICENSE file, but which license should we use is not up to me, or any of the "dev" team. I think that @tessel can guide us in this regard.
EUPL was suggested for code https://eupl.eu/
And CC BY licence for text was suggested
When it comes to the -NC or -ND clauses I am personally against it as those conditions would make the works non-free cultural goods.