Skip to content
This repository was archived by the owner on Jun 18, 2024. It is now read-only.

Emphasize license-free when discussing license examples #257

Closed
wants to merge 4 commits into from
Closed

Emphasize license-free when discussing license examples #257

wants to merge 4 commits into from

Conversation

konklone
Copy link
Contributor

This pull request by @JoshData and I updates the license examples page to explicitly recommend making an agency's data free of licensing, through a worldwide public domain dedication.

This isn't a very radical suggestion - CC0 and the PDDL are already listed on the license examples page. However, CC0 and PDDL are not licenses, but an explicit avoidance of licensing, so I've also updated the list to reflect that, and move CC0 and PDDL to their own section. HHS and the CFPB have both already made some of their work license-free via CC0.

This PR includes a link to the government data licensing guidance that a large number of non-governmental public interest groups signed on to in December. Some of the real world HHS and CFPB examples are referenced there, along with this project itself.

konklone and others added 4 commits January 26, 2014 23:28
…fference between licenses and public domain dedications, and link to best practices and guidance from civil society.
Also moving the PDDL up from a data license to a public domain dedication.
tweak the license-free revision
@JoshData
Copy link
Contributor

@konklone means (D)HHS, not DHS. :)

@konklone
Copy link
Contributor Author

Thanks, updated the text of the PR.

@waldoj
Copy link

waldoj commented Jan 27, 2014

👍 This needs to happen.

@philipashlock
Copy link
Contributor

👍

@KatataK
Copy link

KatataK commented Apr 5, 2014

Can you provide/point to some 1:1 suggestions of proprietary vs. open >formats<?
e.g. "instead of .doc or .docx we suggest .odt" Specifically looking for a .pdf alternate that maintains the appearance of the original file and generally meets the needs of comms/branding people.

Also, great summary of legal language and contract guidance on open licenses. thanks!

@konklone
Copy link
Contributor Author

konklone commented Apr 5, 2014

That's a very helpful discussion to have (and @philipashlock has done a lot of research on this exact issue), though probably off-topic for this particular thread. Maybe @philipashlock should start a discussion somewhere about it and CC us. 😄

@gbinal
Copy link
Contributor

gbinal commented Feb 3, 2015

+1

@rebeccawilliams
Copy link
Contributor

Thanks for these suggestions! I wanted to flag the recent licensing guidance updates, created with #454 + #456. As part of these updates, the /license-examples information was added (and redirected) to the /open-licenses page. Please reopen a new PR if any of your concerns were not addressed with those updates. Note: #257 and #196 remain open.

@konklone
Copy link
Contributor Author

konklone commented Jul 7, 2015

I think this definitely covers the spirit and content of our PR, and it looks like @JoshData agreed in #456 (comment).

Thank you, @rebeccawilliams @philipashlock @jlberryhill!

@JoshData
Copy link
Contributor

JoshData commented Jul 7, 2015

❤️

@ErieMeyer
Copy link
Contributor

Hi all -- flagging this issue for @corizarek

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants