Update license.csv

[stufraser1]

Updating license.csv to include more licenses.

Initial proposal: is what the table would look like with 'other conformant licences' added to the recommended conformant licences, which were already included from https://opendefinition.org/licenses/ per #123 I question the value of including the several deprecated licences. Your views in terms of practicality - @pzwsk @matamadio ? Best practice considerations - @odscjen @odscrachel @duncandewhurst ?

Update: decision to include only OD conformant licences and those listed by WB Data Catalog.

Related issues

123

Merge checklist

• [x] Update the changelog (style guide)
• [ ] Run ./manage.py pre-commit

[stufraser1]

Removed deprecated and specified versions. I still don't know if this is practically needed -- I have never heard of most of the licences just added so not sure we will use them, but table should be comprehensive? Or, as @odsjen says, should we include the ones we want people to use (in which case this PR is not needed) and if they want to use a niche one, they can.

[pzwsk]

After considering @odscjen comments, I agree it is better to only list the license we want users to adopt while offering them the possibility to apply any other one (open list).

I would therefore stick to the list provided by the WB Data Catalog. Is this the list we already have?

[pzwsk]

One additional comment:

HDX has been promoting the use of the Creative Commons 3.0 BY-IGO (with a specific statement regarding the fact that national jurisdictions do not apply in the case of international organizations).

However, I do not see this license in the new 4.0 CC set and so would not consider adding it.

[stufraser1]

stick to the list provided by the WB Data Catalog. Is this the list we already have?

Agree with above comments. WB Data Catalog allows:

[stufraser1]

@odscjen your re-review and pre-commit please.