Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail From: Chris Angelico Newsgroups: comp.lang.python Subject: =?UTF-8?Q?Re=3A_GitHub=27s_=C2=B3pull_request=C2=B2_is_proprietary_lock=2Din?= Date: Sun, 3 Jan 2016 21:17:02 +1100 Lines: 41 Message-ID: References: <87si2hdoq3.fsf@jester.gateway.pace.com> <8560zcsbuu.fsf@benfinney.id.au> <56889608.50504@gmail.com> <85h9ivqcey.fsf@benfinney.id.au> <85d1tjq9lg.fsf@benfinney.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: news.uni-berlin.de PdJxbGcd617VLlIEQvprSAmzqfusqHMY27w3JJamDZ2A== Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.008 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'received:209.85.223': 0.03; 'feature.': 0.07; 'cc:addr:python-list': 0.09; 'before.': 0.09; 'git': 0.09; 'url:github': 0.09; 'example:': 0.10; 'jan': 0.11; 'discussions': 0.15; 'server,': 0.15; '2016': 0.16; '7:45': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'git.': 0.16; 'interacting': 0.16; 'received:io': 0.16; 'received:psf.io': 0.16; 'subject:lock': 0.16; 'uh,': 0.16; 'wrote:': 0.16; 'cc:2**0': 0.20; 'cc:addr:python.org': 0.20; 'are.': 0.22; 'header:In-Reply-To:1': 0.24; 'discussion': 0.24; 'feature': 0.24; 'chris': 0.26; 'message-id:@mail.gmail.com': 0.27; 'data,': 0.27; 'specifically': 0.28; 'talked': 0.29; 'allows': 0.30; "i'm": 0.30; 'system,': 0.30; 'code': 0.30; 'everyone': 0.31; 'anyone': 0.32; 'useful': 0.33; 'controls': 0.33; 'raising': 0.33; 'quickly': 0.34; 'running': 0.34; 'received:google.com': 0.35; 'community': 0.36; 'should': 0.36; 'received:209.85': 0.36; 'hosted': 0.36; 'pm,': 0.36; 'subject:: ': 0.37; 'link.': 0.37; 'received:209': 0.38; 'why': 0.39; 'data': 0.39; 'along': 0.39; 'subject:-': 0.39; 'here.': 0.62; 'course': 0.62; 'reviews': 0.63; 'different': 0.63; 'request.': 0.66; 'accessed': 0.66; 'talking': 0.67; 'therefore': 0.67; 'subjectcharset:utf-8': 0.71; 'vital': 0.76; 'alone,': 0.84; 'chrisa': 0.84; 'ultimately,': 0.84; 'to:none': 0.91; 'proposal.': 0.93 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type:content-transfer-encoding; bh=+QMuxfOHJ/qZthEgXLG5p4Ff4HdBVSvqMk1lWLStexo=; b=V7gZLFBWovsyacwK1RHM8G+7RBrdfJLZywEA6iyAU9jPc4ga+JxqpDpo5r4VkwJSju l/bqUyzml/nPNTHHcSJuYbXcHVRbK0+V83L7bZZBcv2Qb3lDh9ukjiaq5vK2+iZJtBqh cGT8npjGAm3NXuuylEjTNAOKMtmW20Ftqe4bOiqU02NE9t1Q+SbmAbsN4rYt4PB2A1h4 qr4YY2bbZobdQ2QNojRVAalzN7bm8wbEUBNWO91MSaHuLcWm5Akd5UvgbCQ8liFBRfLk KfNzXcuOrbITibk4wsO/xufDQMV1aQJaIOZJPIgkatv6OOoCi4YLrVd5mJn4T2Tm81Jw wF2Q== X-Received: by 10.107.14.73 with SMTP id 70mr45259591ioo.31.1451816222619; Sun, 03 Jan 2016 02:17:02 -0800 (PST) In-Reply-To: <85d1tjq9lg.fsf@benfinney.id.au> X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com comp.lang.python:101200 On Sun, Jan 3, 2016 at 8:46 PM, Ben Finney wro= te: > Chris Angelico writes: > >> On Sun, Jan 3, 2016 at 7:45 PM, Ben Finney = 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 =E2=80=9CGitHu= b pull > request=E2=80=9D. 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 =E2=80=9CGitHub pull request=E2=80=9D? > > 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