{"action":"created","issue":{"url":"https://api.github.com/repos/git-federation/gitpub/issues/2","repository_url":"https://api.github.com/repos/git-federation/gitpub","labels_url":"https://api.github.com/repos/git-federation/gitpub/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/git-federation/gitpub/issues/2/comments","events_url":"https://api.github.com/repos/git-federation/gitpub/issues/2/events","html_url":"https://github.com/git-federation/gitpub/issues/2","id":329395900,"node_id":"MDU6SXNzdWUzMjkzOTU5MDA=","number":2,"title":"ask w3c/activitypub how to extend the activitypub protocol","user":{"login":"21stio","id":17232576,"node_id":"MDQ6VXNlcjE3MjMyNTc2","avatar_url":"https://avatars2.githubusercontent.com/u/17232576?v=4","gravatar_id":"","url":"https://api.github.com/users/21stio","html_url":"https://github.com/21stio","followers_url":"https://api.github.com/users/21stio/followers","following_url":"https://api.github.com/users/21stio/following{/other_user}","gists_url":"https://api.github.com/users/21stio/gists{/gist_id}","starred_url":"https://api.github.com/users/21stio/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/21stio/subscriptions","organizations_url":"https://api.github.com/users/21stio/orgs","repos_url":"https://api.github.com/users/21stio/repos","events_url":"https://api.github.com/users/21stio/events{/privacy}","received_events_url":"https://api.github.com/users/21stio/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":21,"created_at":"2018-06-05T10:30:44Z","updated_at":"2018-06-07T06:45:27Z","closed_at":null,"author_association":"NONE","body":"maybe it would be a good idea to ask the activitypub authors for general guidelines on how to extend the protocol, to make sure it won't end in a big mess"},"comment":{"url":"https://api.github.com/repos/git-federation/gitpub/issues/comments/395311372","html_url":"https://github.com/git-federation/gitpub/issues/2#issuecomment-395311372","issue_url":"https://api.github.com/repos/git-federation/gitpub/issues/2","id":395311372,"node_id":"MDEyOklzc3VlQ29tbWVudDM5NTMxMTM3Mg==","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},"created_at":"2018-06-07T06:45:27Z","updated_at":"2018-06-07T06:45:27Z","author_association":"CONTRIBUTOR","body":"@arucard21: I thought of the 2 major case like this:\r\n\r\n## Forking\r\n\r\n1. Ken has a repository \"foobar/hello\" on Server A.\r\n2. Lennon wants to fork this repository. He has an account on Server B with the \"lennon\" namespace and he want to fork to be \"lennon/hello\" on Server B.\r\n3. Lennon instruct Server B to fork \"foobar/hello\" on Server A by providing the source repository URL.\r\n4. Server B discover the repository's git / https / ssh endpoint for cloning. It cloned the repository and setup \"lennon/hello\" with all the branches from \"foobar/hello\".\r\n5. For the sack of politeness, Server B tell Server A and say \"Hey, we have a fork of your foobar/hello at my lennon/hello. You may subscribe the changes here with the information attached here\".\r\n6. Server B might subscribe to \"foobar/hello\" and do something about it. Totally optional.\r\n7. Server A might display an other link to Server B. Or even subscribe to Server B's \"lennon/hello\". Totally optional.\r\n\r\n**Notes**\r\n* Server B might display a back link on Server A. That is not concerns the protocol.\r\n\r\n## Pull Request\r\n\r\n1. Lennon made some awesome changes on his \"lennon/hello\" repository on Server B. He made it available on the \"awesome\" branch there.\r\n2. Lennon say to Server B, \"hey, I want to send a PR to upstream server\".\r\n3. Server B, \"Ho. I remember. It is foobar/hello on Server A, right? If not, please tell me.\"\r\n4. Lennon, \"That is correct. Thanks for asking.\"\r\n5. Server B ask Server A, \"Hey pal. What are the branches on your foobar/hello?\"\r\n6. Server A shown Server B.\r\n7. Server B ask Lennon, \"Alright, here are the branches on foobar/hello on Server A. Which base branch do you want?\"\r\n8. Lennon, \"Mmm... I'd want to base on master\".\r\n9. Server B might show Lennon the diff. Or not. It'll say, \"OK. I'll tell Server A. Stay tuned.\"\r\n11. Server B tell Server A, \"Hello. My user Lennon would want to send you a PR. Here is the URL of the **branch** that we're talking about.\"\r\n12. Server A, \"OK. One moment\" It checks the repository and branch, or not.\r\n13. Server A check Ken's setting or its own policy. It found that it should not create the PR right the way. It ask Ken, \"Hey, there is an in coming PR and this is the branch's URL.\" It might also give Ken a preview, or not.\r\n14. Ken, \"Seems fine. I agree for you to create a PR here. But do not accept it just yet.\"\r\n15. Server A tell Server B, \"OK. The PR is created here.\"\r\n16. Server B tell Lennon, \"OK, Here is the PR address. Go see it on Server A. Remember to follow their rules. Enjoy\"\r\n17. Now. Lennon and Ken may have email conversation, or talks over Server A. Lennon may also need to create an account on Server A to reply Ken's comment. These does not concern the PR protocol itself.\r\n18. As requested by Ken, Lennon done several updates on Server B lennon/hello. Server B would tell Server A about these new pushes / remove / rebase. It would tell Server B if Lennon simply gave up and removed the branch. But Lennon persisted in the PR.\r\n19. Server A knows about the changes at the PR downstream branch. It might display to Ken.\r\n20. Finally, Ken agree that the PR is ready. Ken merged it and closed the PR from upstream.\r\n21. Server A tells Server B, \"Seems the PR is closed. Will let you know otherwise. I know where to find you anyway.\"\r\n22. Server B trusts Server A and said nothing back.\r\n23. Server B tells Lennon, \"The PR has been merged. Congrat.\"\r\n"}}
{"actor":{"display_login":"yookoala"}}