{"action":"created","issue":{"url":"https://api.github.com/repos/bitcoinclassic/bitcoinclassic/issues/171","repository_url":"https://api.github.com/repos/bitcoinclassic/bitcoinclassic","labels_url":"https://api.github.com/repos/bitcoinclassic/bitcoinclassic/issues/171/labels{/name}","comments_url":"https://api.github.com/repos/bitcoinclassic/bitcoinclassic/issues/171/comments","events_url":"https://api.github.com/repos/bitcoinclassic/bitcoinclassic/issues/171/events","html_url":"https://github.com/bitcoinclassic/bitcoinclassic/issues/171","id":158132150,"number":171,"title":"License and Attribution","user":{"login":"krisives","id":153967,"avatar_url":"https://avatars.githubusercontent.com/u/153967?v=3","gravatar_id":"","url":"https://api.github.com/users/krisives","html_url":"https://github.com/krisives","followers_url":"https://api.github.com/users/krisives/followers","following_url":"https://api.github.com/users/krisives/following{/other_user}","gists_url":"https://api.github.com/users/krisives/gists{/gist_id}","starred_url":"https://api.github.com/users/krisives/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/krisives/subscriptions","organizations_url":"https://api.github.com/users/krisives/orgs","repos_url":"https://api.github.com/users/krisives/repos","events_url":"https://api.github.com/users/krisives/events{/privacy}","received_events_url":"https://api.github.com/users/krisives/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-06-02T12:47:13Z","updated_at":"2016-06-03T10:47:26Z","closed_at":null,"body":"What is the plan for attribution regarding places where it currently says \"Bitcoin Core Developers\"? \r\n\r\n* is there going to be a new group name like \"Bitcoin Classic Developers\" which is appended to the source files giving 3 author attributions (Satoshi, Core, and the new group)\r\n\r\n* What should the About dialog display? Right now it says \"Bitcoin Core Developers\"\r\n\r\nAnother user started a [reddit post](https://www.reddit.com/r/btc/comments/4m6ohy/this_should_be_fixed_imo/d3szyrl) about this topic.\r\n"},"comment":{"url":"https://api.github.com/repos/bitcoinclassic/bitcoinclassic/issues/comments/223548765","html_url":"https://github.com/bitcoinclassic/bitcoinclassic/issues/171#issuecomment-223548765","issue_url":"https://api.github.com/repos/bitcoinclassic/bitcoinclassic/issues/171","id":223548765,"user":{"login":"zander","id":63063,"avatar_url":"https://avatars.githubusercontent.com/u/63063?v=3","gravatar_id":"","url":"https://api.github.com/users/zander","html_url":"https://github.com/zander","followers_url":"https://api.github.com/users/zander/followers","following_url":"https://api.github.com/users/zander/following{/other_user}","gists_url":"https://api.github.com/users/zander/gists{/gist_id}","starred_url":"https://api.github.com/users/zander/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zander/subscriptions","organizations_url":"https://api.github.com/users/zander/orgs","repos_url":"https://api.github.com/users/zander/repos","events_url":"https://api.github.com/users/zander/events{/privacy}","received_events_url":"https://api.github.com/users/zander/received_events","type":"User","site_admin":false},"created_at":"2016-06-03T10:47:26Z","updated_at":"2016-06-03T10:47:26Z","body":"> What is the plan for attribution regarding places where it currently says \"Bitcoin Core Developers\"? \r\n\r\nWe follow the law.\r\nHere is a good [description](http://www.gnu.org/licenses/gpl-howto.en.html)\r\n\r\n> Whichever license you plan to use, the process involves adding two elements to **each source file** of your program: a copyright notice (such as “Copyright 1999 Terry Jones”), and a statement of copying permission, saying that the program is distributed under the terms of [the license]\r\n\r\n> The copyright notice should include the year in which you finished preparing the release (so if you finished it in 1998 but didn't post it until 1999, use 1998). **You should add the proper year for each release**; for example, “Copyright 1998, 1999 Terry Jones” if some versions were finished in 1998 and some were finished in 1999. **If several people helped write the code, use all their names.**\r\n\r\n> For software with several releases over multiple years, it's okay to use a range (“2008-2010”) instead of listing individual years (“2008, 2009, 2010”) if and only if every year in the range, inclusive, really is a “copyrightable” year that would be listed individually; and you make an explicit statement in your documentation about this usage.\r\n\r\n> Always use the English word “Copyright”; by international convention, this is used worldwide, even for material in other languages. The copyright symbol “©” can be included if you wish (and your character set supports it), but it's not necessary. There is no legal significance to using the three-character sequence “(C)”, although it does no harm.\r\n\r\n\r\nThe Bitcoin Core group didn't follow these rules very well. It essentially did not honour copyright of individual contributors, instead giving it all to the group as a whole.\r\n\r\nIn Classic I think we can improve upon this and grant copyright to individuals in the files they edited.\r\n\r\nThe question of what to do with the copyright notice we inherited from Core is not easy to answer. Legally individuals still have their rights, but because they never claimed it they will have a really hard time claiming their rights.\r\n\r\nI personally don't want to touch their copyright notices as they are none of my business. I can't remove such a notice, even if I deem the entity claiming rights not existing, because I would destroy what little evidence there is of their ownership.\r\n\r\nMy personal position is that we should add, as suggested by the Free Software Foundation international lawyers which I quoted above, and not remove or change any of the notices in Bitcoin Classic."}}
{"actor":{"display_login":"zander"}}