Re: We will be moving to GitHub

Path	csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From	Michael Torrie <torriem@gmail.com>
Newsgroups	comp.lang.python
Subject	Re: We will be moving to GitHub
Date	Sat, 02 Jan 2016 20:24:50 -0700
Lines	23
Message-ID	<mailman.191.1451791929.11925.python-list@python.org> (permalink)
References	<n66kmg$ig$1@ger.gmane.org> <CAPTjJmq1Qevy7h4pqrQPobLRO-_ooLrXsZhK9Z9YCKPyFnxKsQ@mail.gmail.com> <CAKJDb-MFM6i+MMZXcPkV6x-rFnKr9Yxt4f3ne1dF3dk_SkoFpw@mail.gmail.com> <mailman.146.1451678991.11925.python-list@python.org> <5687718d$0$1612$c3e8da3$5496439d@news.astraweb.com>
Mime-Version	1.0
Content-Type	text/plain; charset=windows-1252
Content-Transfer-Encoding	7bit
X-Trace	news.uni-berlin.de XQerw+bfqtAReLfUwoUrPwOxt3FLvrR5CE8a59tAHkkQ==
Return-Path	<torriem+gmail@torriefamily.org>
X-Original-To	python-list@python.org
Delivered-To	python-list@mail.python.org
X-Spam-Status	OK 0.005
X-Spam-Evidence	'H': 0.99; 'S': 0.00; 'repository': 0.05; 'read- only': 0.07; 'effect.': 0.09; 'git': 0.09; 'jan': 0.11; 'options.': 0.15; '2016': 0.16; 'after,': 0.16; "developers'": 0.16; 'from:addr:torriem': 0.16; 'from:name:michael torrie': 0.16; 'mercurial,': 0.16; 'received:io': 0.16; 'received:psf.io': 0.16; 'tool.': 0.16; 'wrote:': 0.16; 'tracker': 0.20; 'arguments': 0.22; 'am,': 0.23; 'sat,': 0.23; 'header:In-Reply-To:1': 0.24; 'requests': 0.25; 'hosting': 0.25; 'header:User-Agent:1': 0.26; 'developers': 0.26; '(which': 0.26; 'sense': 0.26; 'chris': 0.26; 'host': 0.28; 'there.': 0.30; 'push': 0.30; 'especially': 0.32; 'expensive': 0.32; 'plans': 0.32; "d'aprano": 0.33; 'http': 0.33; 'steven': 0.33; 'message-id:@gmail.com': 0.34; 'python.org': 0.35; 'primarily': 0.35; 'but': 0.36; 'too': 0.36; 'hosted': 0.36; 'to:addr:python-list': 0.36; 'pm,': 0.36; 'subject:: ': 0.37; 'really': 0.37; 'received:org': 0.37; 'why': 0.39; 'received:192': 0.39; 'to:addr:python.org': 0.40; 'charset:windows-1252': 0.62; 'matter': 0.63; 'more': 0.63; 'complete': 0.63; 'capable': 0.65; 'differences': 0.66; 'oss': 0.84
X-Virus-Scanned	amavisd-new at torriefamily.org
User-Agent	Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
In-Reply-To	<5687718d$0$1612$c3e8da3$5496439d@news.astraweb.com>
X-BeenThere	python-list@python.org
X-Mailman-Version	2.1.20+
Precedence	list
List-Id	General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe	<https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive	<http://mail.python.org/pipermail/python-list/>
List-Post	<mailto:python-list@python.org>
List-Help	<mailto:python-list-request@python.org?subject=help>
List-Subscribe	<https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Xref	csiph.com comp.lang.python:101185

Show key headers only | View raw

On 01/01/2016 11:43 PM, Steven D'Aprano wrote:
> On Sat, 2 Jan 2016 07:09 am, Chris Angelico wrote:
> 
>> Yes, git is a capable tool. But so is Mercurial, and the arguments
>> weren't primarily based on differences in functionality (which are
>> pretty minor). It's mainly about the network effect.
> 
> You call it the network effect. I call it monoculture.

Indeed. The whole purpose of git is to allow development to be
distributed.  Is it a matter of hosting space?  Is it too expensive for
python.org to host their own public-facing git repository?  Especially
if python.org has no plans to use github's issue tracker this move makes
little sense to me.  A pull request can be made from any developer's own
git repository without github, or even from github if other developers
really want to work there.

I can understand why OSS projects like github given its complete
project-management options.  But if it's just the repository you're
after, I get far more mileage from my own locally-hosted git
repositories.  It's not at all hard to push to a read-only public http
git repository.  Pull requests can be made against individual
developers' http repos or hosted git providers.

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-02 07:09 +1100
  Re: We will be moving to GitHub Steven D'Aprano <steve@pearwood.info> - 2016-01-02 17:43 +1100
    Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-02 18:12 +1100
    Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-02 11:48 +0200
      Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-02 21:29 +1100
        Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-02 13:22 +0200
          Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-02 22:40 +1100
            Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-02 16:26 +0200
              Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-03 01:38 +1100
                Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-02 16:52 +0200
                Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-03 02:12 +1100
                Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-03 02:33 +0200
                Re: We will be moving to GitHub Chris Angelico <rosuav@gmail.com> - 2016-01-03 11:42 +1100
                Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-03 03:14 +0200
                Re: We will be moving to GitHub m <mvoicem@gmail.com> - 2016-01-04 11:13 +0100
                Re: We will be moving to GitHub Marko Rauhamaa <marko@pacujo.net> - 2016-01-04 13:28 +0200
      Re: We will be moving to GitHub Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-01-04 23:53 +0100
    Re: We will be moving to GitHub Tim Chase <python.list@tim.thechases.com> - 2016-01-02 06:58 -0600
    Re: We will be moving to GitHub Michael Torrie <torriem@gmail.com> - 2016-01-02 20:24 -0700

csiph-web