{"action":"created","issue":{"url":"https://api.github.com/repos/git-federation/gitpub/issues/11","repository_url":"https://api.github.com/repos/git-federation/gitpub","labels_url":"https://api.github.com/repos/git-federation/gitpub/issues/11/labels{/name}","comments_url":"https://api.github.com/repos/git-federation/gitpub/issues/11/comments","events_url":"https://api.github.com/repos/git-federation/gitpub/issues/11/events","html_url":"https://github.com/git-federation/gitpub/issues/11","id":329947238,"node_id":"MDU6SXNzdWUzMjk5NDcyMzg=","number":11,"title":"Federated issue tracking","user":{"login":"yookoala","id":91274,"node_id":"MDQ6VXNlcjkxMjc0","avatar_url":"https://avatars2.githubusercontent.com/u/91274?v=4","gravatar_id":"","url":"https://api.github.com/users/yookoala","html_url":"https://github.com/yookoala","followers_url":"https://api.github.com/users/yookoala/followers","following_url":"https://api.github.com/users/yookoala/following{/other_user}","gists_url":"https://api.github.com/users/yookoala/gists{/gist_id}","starred_url":"https://api.github.com/users/yookoala/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yookoala/subscriptions","organizations_url":"https://api.github.com/users/yookoala/orgs","repos_url":"https://api.github.com/users/yookoala/repos","events_url":"https://api.github.com/users/yookoala/events{/privacy}","received_events_url":"https://api.github.com/users/yookoala/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2018-06-06T16:40:55Z","updated_at":"2018-06-07T08:00:44Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"### Problem\r\n1. Ken on server A created an issue to Lennon's repository on server B.\r\n2. Mandy on server B is a contributor to Lennon's repository.\r\n3. Oprah on server C is also a contributor to Lenonn's repository.\r\n4. Who should have the permission to close the issue? And how?\r\n\r\n@tantek has experience on [Github bridging](https://indieweb.org/GitHub#Tantek). And he has some insight about cross domain permission handling. He raised interesting point in the ActivityPub community group meeting tonight that lead me thinking of this problem. (I think @cwebber tried to raise the same point but I was too stupid to pick up.)\r\n\r\nThe same problem also applies to a PR. Do we handle it? Or do we omit it?"},"comment":{"url":"https://api.github.com/repos/git-federation/gitpub/issues/comments/395329497","html_url":"https://github.com/git-federation/gitpub/issues/11#issuecomment-395329497","issue_url":"https://api.github.com/repos/git-federation/gitpub/issues/11","id":395329497,"node_id":"MDEyOklzc3VlQ29tbWVudDM5NTMyOTQ5Nw==","user":{"login":"bill-auger","id":1642691,"node_id":"MDQ6VXNlcjE2NDI2OTE=","avatar_url":"https://avatars3.githubusercontent.com/u/1642691?v=4","gravatar_id":"","url":"https://api.github.com/users/bill-auger","html_url":"https://github.com/bill-auger","followers_url":"https://api.github.com/users/bill-auger/followers","following_url":"https://api.github.com/users/bill-auger/following{/other_user}","gists_url":"https://api.github.com/users/bill-auger/gists{/gist_id}","starred_url":"https://api.github.com/users/bill-auger/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bill-auger/subscriptions","organizations_url":"https://api.github.com/users/bill-auger/orgs","repos_url":"https://api.github.com/users/bill-auger/repos","events_url":"https://api.github.com/users/bill-auger/events{/privacy}","received_events_url":"https://api.github.com/users/bill-auger/received_events","type":"User","site_admin":false},"created_at":"2018-06-07T08:00:44Z","updated_at":"2018-06-07T08:00:44Z","author_association":"NONE","body":"in the pagure model issues are just git repos - that inherently makes it federated - new issues and issue comments then are just a git commits that can be handled in exactly the same way as a pull request against the code repo - as no external tooling would be required for that it seems the simplest razor solution - it can be argued that the protocol should not assume the implementation but we are talking about git forges and pull requests are an intrinsic feature that needs to be specified anyways - even if not implemented as a git repo on a particular server, making a patch file of the issue in order to fake a pull request seems like very simple adaptor - in any case it would be highly desirable that entire issue sets can be completely migrated from one inter-operating git forges to another\r\n"}}
{"actor":{"display_login":"bill-auger"}}