On Sun, Jan 3, 2016 at 8:46 PM, Ben Finney <ben+pyt...@benfinney.id.au> wrote: > Chris Angelico <ros...@gmail.com> writes: > >> On Sun, Jan 3, 2016 at 7:45 PM, Ben Finney <ben+pyt...@benfinney.id.au> >> wrote: >> > Anyone can take email data from the email server, migrate it to a >> > different implementation of the same email system, keep it running >> > with the same data and allow the same people to continue interacting >> > with it as before. >> > >> > Those are traits I think a community should require of any system >> > that controls vital discussions like pull requests. >> >> They are. Ultimately, a GitHub pull request is backed by a git pull >> request. Here's an example: >> >> https://github.com/MikeiLL/appension/pull/187 > > Yes, of course the VCS data is in Git and therefore can be accessed with > Git. Please stop raising that when *I'm not talking about* the VCS data > alone, I'm talking also about the data of the pull request feature.
Uh, that's a pull request link. I'm talking specifically about the pull request feature here. > The discussion data, code review data, etc. is all part of “GitHub pull > request”. How do we export, along with the VCS data, the data and system > that control the code review discussino and other useful features > entailed by “GitHub pull request”? > > How do we get that data and confidently and quickly set up a system > hosted on a different provider that allows everyone involved to continue > the same code reviews and discussions etc. without GitHub? That's why I talked about what it's like if discussion continues to happen on b.p.o. Which is the current proposal. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
