Skip to content

Added two POSEIDON.yml fields to specify a data licence for a package#115

Merged
nevrome merged 4 commits intodevfrom
licensing
Dec 10, 2025
Merged

Added two POSEIDON.yml fields to specify a data licence for a package#115
nevrome merged 4 commits intodevfrom
licensing

Conversation

@nevrome
Copy link
Member

@nevrome nevrome commented Dec 2, 2025

I think it was @martynamolak who proposed this initially and I think it is a good feature to have. I tried to make it pretty flexible and, of course, fully optional.

The british spelling of "licence" nauseates me a bit, but I guess we should stick to it for consistency.

Copy link
Member

@stschiff stschiff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, that's definitely already fine as suggested here. Just some points that I'm thinking about:

In the YAML, I think I may actually prefer a hierarchical encoding, so:

- licence:
  - short_name: CC-BY-4.0
  - file: LICENCE.TXT

which I think we can encode through our levels in the POSEIDON_yml_fields.tsv, right?

I also would suggest to be more explicit that the file is more optional than the short name. I think it would lower the barrier to use licenses if one can just plug in a short name without having to find the text on the internet and copy it here.

@nevrome
Copy link
Member Author

nevrome commented Dec 10, 2025

Good point! I'll implement that

@nevrome nevrome merged commit 46b3a94 into dev Dec 10, 2025
@nevrome nevrome deleted the licensing branch December 10, 2025 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants