{"action":"opened","issue":{"url":"https://api.github.com/repos/falling-fruit/falling-fruit/issues/24","repository_url":"https://api.github.com/repos/falling-fruit/falling-fruit","labels_url":"https://api.github.com/repos/falling-fruit/falling-fruit/issues/24/labels{/name}","comments_url":"https://api.github.com/repos/falling-fruit/falling-fruit/issues/24/comments","events_url":"https://api.github.com/repos/falling-fruit/falling-fruit/issues/24/events","html_url":"https://github.com/falling-fruit/falling-fruit/issues/24","id":235742946,"number":24,"title":"legally impossible terms in README","user":{"login":"wolftune","id":2801853,"avatar_url":"https://avatars3.githubusercontent.com/u/2801853?v=3","gravatar_id":"","url":"https://api.github.com/users/wolftune","html_url":"https://github.com/wolftune","followers_url":"https://api.github.com/users/wolftune/followers","following_url":"https://api.github.com/users/wolftune/following{/other_user}","gists_url":"https://api.github.com/users/wolftune/gists{/gist_id}","starred_url":"https://api.github.com/users/wolftune/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wolftune/subscriptions","organizations_url":"https://api.github.com/users/wolftune/orgs","repos_url":"https://api.github.com/users/wolftune/repos","events_url":"https://api.github.com/users/wolftune/events{/privacy}","received_events_url":"https://api.github.com/users/wolftune/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-06-14T02:12:40Z","updated_at":"2017-06-14T02:12:40Z","closed_at":null,"body":"> We reserve the right to prohibit use on a project-by-project basis\r\n\r\nIs legally *impossible* under the licenses you have chosen and actually under *any* form of open public license. You simply cannot reserve that right without being flat-out proprietary software and proprietary data.\r\n\r\nI understand the desire to have some control and want to block use that you find objectionable, but the best way to do that is simply with the strongest copyleft licenses. For data, that could CC BY-SA (without the NC) but I actually recommend for your case the [Open Database License](https://opendatacommons.org/licenses/odbl/summary/), and for the software, you will do *much* better at stopping exploitation with the AGPL than with the GPL. The AGPL *is* the GPL with the extra Affero clause that closes the loophole for use over a server (with the plain GPL, your software could be exploited in use on a web service and they don't have to follow the GPL at all because they aren't distributing the software for others to run!) So, the AGPL is better for giving you the control you want to ensure the software stays in the public and isn't exploited by proprietary interests.\r\n\r\nIncidentally, changing your database license is a weirder question because copyright on this sort of data is a weird question in itself. But moving the software from GPL to AGPL is easy because the GPL already has a clause that says you can use GPLv3 code under AGPLv3\r\n\r\nAnyway, you can still have a non-legal statement that says you would *like* people to check with you before using the software or data, even though you can't legally stop uses that follow the licenses."}}
{"actor":{"display_login":"wolftune"}}