{"action":"created","issue":{"url":"https://api.github.com/repos/Xilinx/XilinxVirtualCable/issues/1","labels_url":"https://api.github.com/repos/Xilinx/XilinxVirtualCable/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/Xilinx/XilinxVirtualCable/issues/1/comments","events_url":"https://api.github.com/repos/Xilinx/XilinxVirtualCable/issues/1/events","html_url":"https://github.com/Xilinx/XilinxVirtualCable/issues/1","id":75149342,"number":1,"title":"Thank you! ... But this looks familiar?!","user":{"login":"tmbinc","id":334045,"avatar_url":"https://avatars.githubusercontent.com/u/334045?v=3","gravatar_id":"","url":"https://api.github.com/users/tmbinc","html_url":"https://github.com/tmbinc","followers_url":"https://api.github.com/users/tmbinc/followers","following_url":"https://api.github.com/users/tmbinc/following{/other_user}","gists_url":"https://api.github.com/users/tmbinc/gists{/gist_id}","starred_url":"https://api.github.com/users/tmbinc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tmbinc/subscriptions","organizations_url":"https://api.github.com/users/tmbinc/orgs","repos_url":"https://api.github.com/users/tmbinc/repos","events_url":"https://api.github.com/users/tmbinc/events{/privacy}","received_events_url":"https://api.github.com/users/tmbinc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-05-11T09:16:31Z","updated_at":"2015-05-11T09:35:26Z","closed_at":null,"body":"I'm very glad that Xilinx decided to publicly support the XVC protocol now. Makes so much stuff so much easier.\r\n\r\nOn the other hand, this code reminds me of code I wrote a few years ago (https://github.com/tmbinc/xvcd). The closer I look, the more similarities I find. Browsing back a few revisions (https://github.com/Xilinx/XilinxVirtualCable/commit/eae2da80c4ad4ff22083d88ab1aa2dad46fc3bc9), it becomes pretty clear that this is not accidental, but that this is in fact based on my code.\r\n\r\nNow, don't get me wrong - my original sourcecode wasn't particularly inventive, clever, clean or great in general. In fact if anybody would have asked, I'd happily have given it away as MIT-licensed or even public domain. But it irritates me a bit that _nobody asked_, and instead I find (parts of) my code with a big \"confidential and proprietary Xilinx, Inc.\" header in another repository, _without any attribution_ to my original source. That's not quite what I expected from either Avnet nor Xilinx.\r\n"},"comment":{"url":"https://api.github.com/repos/Xilinx/XilinxVirtualCable/issues/comments/100833307","html_url":"https://github.com/Xilinx/XilinxVirtualCable/issues/1#issuecomment-100833307","issue_url":"https://api.github.com/repos/Xilinx/XilinxVirtualCable/issues/1","id":100833307,"user":{"login":"saatanaperkele","id":10095259,"avatar_url":"https://avatars.githubusercontent.com/u/10095259?v=3","gravatar_id":"","url":"https://api.github.com/users/saatanaperkele","html_url":"https://github.com/saatanaperkele","followers_url":"https://api.github.com/users/saatanaperkele/followers","following_url":"https://api.github.com/users/saatanaperkele/following{/other_user}","gists_url":"https://api.github.com/users/saatanaperkele/gists{/gist_id}","starred_url":"https://api.github.com/users/saatanaperkele/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/saatanaperkele/subscriptions","organizations_url":"https://api.github.com/users/saatanaperkele/orgs","repos_url":"https://api.github.com/users/saatanaperkele/repos","events_url":"https://api.github.com/users/saatanaperkele/events{/privacy}","received_events_url":"https://api.github.com/users/saatanaperkele/received_events","type":"User","site_admin":false},"created_at":"2015-05-11T09:35:26Z","updated_at":"2015-05-11T09:35:26Z","body":"I hate seeing this happen, it's not difficult to include attribution or a license with a project provided things are compatible. Either way, this is despicable behavior."}}