Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail From: Ben Finney Newsgroups: comp.lang.python Subject: GitHub's =?utf-8?Q?=E2=80=9Cpull_request=E2=80=9D?= is proprietary lock-in (was: We will be moving to GitHub) Date: Sun, 03 Jan 2016 15:43:52 +1100 Lines: 32 Message-ID: References: <87si2hdoq3.fsf@jester.gateway.pace.com> <8560zcsbuu.fsf@benfinney.id.au> <56889608.50504@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: news.uni-berlin.de UKCzsWtSb2CuLlXZW1GRDARqABHtAnKk/47NzKKezuZw== Cancel-Lock: sha1:tbyWTpQVRjSA74ayaW06/CC3Ub4= Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.025 X-Spam-Evidence: '*H*': 0.95; '*S*': 0.00; 'git': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'thread': 0.10; '(unlike': 0.16; 'exported': 0.16; 'really?': 0.16; 'received:80.91.229.3': 0.16; 'received:io': 0.16; 'received:plane.gmane.org': 0.16; 'received:psf.io': 0.16; 'request)': 0.16; 'subject:lock': 0.16; 'url.': 0.16; 'wrote:': 0.16; 'cloud': 0.20; 'am,': 0.23; 'seems': 0.23; 'communities': 0.23; 'proprietary': 0.23; 'discussion': 0.24; 'header:User- Agent:1': 0.26; 'header:X-Complaints-To:1': 0.26; 'right.': 0.27; '(including': 0.30; 'code': 0.30; 'option': 0.31; 'another': 0.32; 'computing': 0.32; 'michael': 0.33; 'requirement.': 0.33; 'retain': 0.33; 'done': 0.35; 'instance': 0.35; 'according': 0.36; 'community': 0.36; 'tool': 0.36; 'data.': 0.36; 'to:addr:python- list': 0.36; 'subject:: ': 0.37; 'received:org': 0.37; 'aspects': 0.37; 'end': 0.39; 'why': 0.39; 'data': 0.39; 'easily': 0.39; 'subject:-': 0.39; 'to:addr:python.org': 0.40; 'valuable': 0.61; 'is.': 0.63; 'more': 0.63; 'within': 0.64; 'our': 0.64; 'subjectcharset:utf-8': 0.71; '\xe2\x80\x93': 0.72; 'sole': 0.76; 'attractive': 0.79; '_o__)': 0.84; 'received:125': 0.84; 'absolutely': 0.88; 'tied': 0.93 X-Injected-Via-Gmane: http://gmane.org/ X-Gmane-NNTP-Posting-Host: jigong.madmonks.org X-Public-Key-ID: 0xAC128405 X-Public-Key-Fingerprint: 517C F14B B2F3 98B0 CB35 4855 B8B2 4C06 AC12 8405 X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-pubkey.asc X-Post-From: Ben Finney User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) 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:101186 Michael Torrie writes: > On 01/02/2016 12:02 AM, Ben Finney wrote: > > GitHub's “pull request” workflow is entirely proprietary and can > > only be done within GitHub. > > Really? This seems like an entirely artificial github requirement. Yes, it is. > There's absolutely no reason why github couldn't do a pull request from > any arbitrary, valid git url. Right. The proprietary GitHub “pull request” has many more features (including a code review tool and discussion thread that are automatically tied to the pull request) which make it attractive. The fact these features (unlike Git) are wholly proprietary, and the valuable processes and data they generate cannot be exported and continued easily in another instance when a community chooses, are what makes GitHub's “pull request” an attractive nuisance. That and other vendor-locked workflow aspects of GitHub makes it a poor choice for communities that want to retain the option of control over their processes and data. -- \ “Try adding “as long as you don't breach the terms of service – | `\ according to our sole judgement” to the end of any cloud | _o__) computing pitch.” —Simon Phipps, 2010-12-11 | Ben Finney