New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Choosing a license #229

Open
amy-silcock opened this Issue Jan 9, 2019 · 6 comments

Comments

Projects
None yet
5 participants
@amy-silcock
Copy link
Contributor

amy-silcock commented Jan 9, 2019

Hi,

When a publisher account is created please can we make the option to select a license mandatory? Or just take out the 'license not specified' option?

@siemvaessen

This comment has been minimized.

Copy link

siemvaessen commented Feb 1, 2019

@amy-silcock what licensing options are currently available? Closed licensing should not be in a list, seeing IATI data is ont supposed to be closed as per IATI guidance:

"As an open data standard, IATI requires you to make your data available under an open licence so it can be freely used. This is central to improving transparency and efficiency in all development cooperation and humanitarian work."

@amy-silcock

This comment has been minimized.

Copy link
Contributor Author

amy-silcock commented Feb 1, 2019

@siemvaessen if you log into the Registry and go to 'manage' on your publisher account. You can see the dropdown list.

@andylolz

This comment has been minimized.

Copy link
Contributor

andylolz commented Feb 1, 2019

@siemvaessen For convenience, here’s a list:

  • License not specified
  • Open Data Commons Public Domain Dedication and License (PDDL)
  • Open Data Commons Open Database License (ODbL)
  • Open Data Commons Attribution License
  • Creative Commons CCZero
  • Creative Commons Attribution
  • Creative Commons Attribution Share-Alike
  • GNU Free Documentation License
  • Other (Open)
  • Other (Public Domain)
  • Other (Attribution)
  • UK Open Government Licence (OGL)
  • Creative Commons Non-Commercial (Any)
  • Other (Non-Commercial)
  • Other (Not Open)

So, all open except the final three (which are closed) and the first one (which is ambiguous).

@andylolz

This comment has been minimized.

Copy link
Contributor

andylolz commented Feb 1, 2019

Big +1 on this ticket (which relates to current datastore discussions).

please can we make the option to select a license mandatory? Or just take out the 'license not specified' option?

^^ I think this should be an “and”, not an “or”. I.e. the license field should be mandatory, and the “license not specified” option should be removed.

@siemvaessen

This comment has been minimized.

Copy link

siemvaessen commented Feb 5, 2019

@andylolz should we tie this list into that discussion? Or too detailed?

@gtkChop gtkChop self-assigned this Feb 13, 2019

@PetyaKangalova

This comment has been minimized.

Copy link

PetyaKangalova commented Feb 21, 2019

Linking to the latest post: https://discuss.iatistandard.org/t/iati-data-licensing-for-unencumbered-data-use/1651/8

We want to make the field mandatory as soon as possible. Once the updated list has been agreed by the community, we need to look at options for those publishers affected by the changes- see step 3 in the post.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment