{"action":"opened","issue":{"url":"https://api.github.com/repos/mvs-org/metaverse/issues/300","repository_url":"https://api.github.com/repos/mvs-org/metaverse","labels_url":"https://api.github.com/repos/mvs-org/metaverse/issues/300/labels{/name}","comments_url":"https://api.github.com/repos/mvs-org/metaverse/issues/300/comments","events_url":"https://api.github.com/repos/mvs-org/metaverse/issues/300/events","html_url":"https://github.com/mvs-org/metaverse/issues/300","id":330164133,"node_id":"MDU6SXNzdWUzMzAxNjQxMzM=","number":300,"title":"Request/Suggestion: MIT secret content field","user":{"login":"CaptainStevey","id":39695829,"node_id":"MDQ6VXNlcjM5Njk1ODI5","avatar_url":"https://avatars0.githubusercontent.com/u/39695829?v=4","gravatar_id":"","url":"https://api.github.com/users/CaptainStevey","html_url":"https://github.com/CaptainStevey","followers_url":"https://api.github.com/users/CaptainStevey/followers","following_url":"https://api.github.com/users/CaptainStevey/following{/other_user}","gists_url":"https://api.github.com/users/CaptainStevey/gists{/gist_id}","starred_url":"https://api.github.com/users/CaptainStevey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CaptainStevey/subscriptions","organizations_url":"https://api.github.com/users/CaptainStevey/orgs","repos_url":"https://api.github.com/users/CaptainStevey/repos","events_url":"https://api.github.com/users/CaptainStevey/events{/privacy}","received_events_url":"https://api.github.com/users/CaptainStevey/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-07T08:16:05Z","updated_at":"2018-06-07T08:16:05Z","closed_at":null,"author_association":"NONE","body":"Is it feasible for an MIT to have a 'secret' content field so that only the current owner can view the secret content?  Not sure of the legalities of this alongside the code difficulty."}}
{"actor":{"display_login":"CaptainStevey"}}