Re: We will be moving to GitHub

Path	csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From	Zachary Ware <zachary.ware+pylist@gmail.com>
Newsgroups	comp.lang.python
Subject	Re: We will be moving to GitHub
Date	Fri, 1 Jan 2016 13:58:59 -0600
Lines	27
Sender	zachary.ware@gmail.com
Message-ID	<mailman.144.1451678342.11925.python-list@python.org> (permalink)
References	<n66kmg$ig$1@ger.gmane.org> <CAPTjJmq1Qevy7h4pqrQPobLRO-_ooLrXsZhK9Z9YCKPyFnxKsQ@mail.gmail.com>
Reply-To	python-list@python.org
Mime-Version	1.0
Content-Type	text/plain; charset=UTF-8
X-Trace	news.uni-berlin.de +7D0fwFzTId5CZYDPUadDwUGWj6RpgrCL2ecl4Gb0gRg==
Return-Path	<zachary.ware@gmail.com>
X-Original-To	python-list@python.org
Delivered-To	python-list@mail.python.org
X-Spam-Status	OK 0.001
X-Spam-Evidence	'H': 1.00; 'S': 0.00; 'cpython': 0.05; 'repository': 0.05; 'url:pipermail': 0.05; 'not': 0.07; 'acceptance': 0.07; 'cc:addr:python-list': 0.09; 'accepted,': 0.09; 'falls': 0.09; 'bug': 0.10; 'received:209.85.218': 0.10; 'jan': 0.11; '2016': 0.16; "brett's": 0.16; 'phone)': 0.16; 'received:io': 0.16; 'received:psf.io': 0.16; 'wiki,': 0.16; 'wrote:': 0.16; 'sender:addr:gmail.com': 0.18; '>': 0.18; 'email addr:gmail.com>': 0.18; 'cc:20': 0.20; 'cc:addr:python.org': 0.20; 'tracker': 0.20; 'saying': 0.22; '(on': 0.22; 'either.': 0.22; 'lawrence': 0.22; 'cc:no real name:20': 0.22; 'am,': 0.23; 'seems': 0.23; 'sat,': 0.23; 'header:In-Reply-To:1': 0.24; 'hosting': 0.25; "i've": 0.25; 'developers': 0.26; 'not.': 0.27; 'message-id:@mail.gmail.com': 0.27; 'pep': 0.29; "i'm": 0.30; 'certain': 0.31; 'url:python': 0.33; 'though.': 0.33; 'open': 0.33; 'worked': 0.34; 'list': 0.34; 'received:google.com': 0.35; 'clear': 0.35; 'interact': 0.35; 'but': 0.36; 'should': 0.36; 'there': 0.36; 'url:org': 0.36; 'received:209.85': 0.36; 'pm,': 0.36; 'subject:: ': 0.37; 'received:209': 0.38; 'several': 0.38; 'does': 0.39; 'system.': 0.39; 'url:mail': 0.40; 'mark': 0.40; 'still': 0.40; 'decision': 0.61; 'details': 0.62; 'future.': 0.67; 'header:Reply-To:1': 0.67; 'levels': 0.70; 'reply-to:no real name:2**0': 0.71; 'reply- to:addr:python.org': 0.84; 'to:none': 0.91; '1:47': 0.91; 'canonical': 0.91
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:cc:content-type; bh=ucHQokWcjjdqCwgEtdb+A8dT46YUjlB706N1AWWwEsk=; b=bjQmO7/TSahRGA7AJX1CRTsvthvXz/z+EQC0Skx/XxePwjZePSArMJbO8Q2qldkNad rqOU+9JMyzFvy0/WHo1D7Y1NToet2k7warAbdKiv3YWzuMXr4QtulJO+KBYyuNJM1hqI kOo1NKjE7p71ML02oWuo5KFPoP/eojSIPZ66LS3+ufjWDIiEcJ7GwGp8XjAzTIO3Behr DEEhsPZws+SV8wyxIJIU9NJxwndAY+n0FjxnvTDzD8RZ3C6bIsWFA5MKnDaQi15X6eat VshGFcrSWYKCul0a/mIOvCUE6iDdU8KkwJn3349f+e4qBLiwHCEBO18M1UrFPKIyOwu7 ktcw==
X-Received	by 10.202.173.9 with SMTP id w9mr47702989oie.79.1451678340057; Fri, 01 Jan 2016 11:59:00 -0800 (PST)
In-Reply-To	<CAPTjJmq1Qevy7h4pqrQPobLRO-_ooLrXsZhK9Z9YCKPyFnxKsQ@mail.gmail.com>
X-Google-Sender-Auth	LoQYHwua1HrNS9tLsd7PNBdMmK0
X-Content-Filtered-By	Mailman/MimeDel 2.1.20+
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:101113

Show key headers only | View raw

On Jan 1, 2016 1:47 PM, "Chris Angelico" <rosuav@gmail.com> wrote:
>
> On Sat, Jan 2, 2016 at 6:39 AM, Mark Lawrence <breamoreboy@yahoo.co.uk>
wrote:
> > Please see
> > https://mail.python.org/pipermail/core-workflow/2016-January/000345.html
> >
> > This should encourage developers at all levels to help out, such that
the
> > list of open issues on the bug tracker falls drastically.
>
> How does that interact with the still-Draft status of PEP 481? The
> email seems to mainly be saying "not GitLab", but until PEP 481 is
> accepted, I'm not certain that GitHub is accepted either.
>
> It's not entirely clear whether that message is an acceptance of PEP 481
or not.

I've lost track of the pep numbers, but Brett's decision is final; the
canonical CPython repository will be moving to GitHub in the near future.
Note that we will *not* be using the GitHub issue tracker or wiki, just the
hosting and review/pull request system. There are still several details to
be worked out, though.

--
Zach
(On a phone)

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

Thread

Re: We will be moving to GitHub Zachary Ware <zachary.ware+pylist@gmail.com> - 2016-01-01 13:58 -0600
  Re: We will be moving to GitHub Paul Rubin <no.email@nospam.invalid> - 2016-01-01 12:33 -0800
    Re: We will be moving to GitHub Zachary Ware <zachary.ware+pylist@gmail.com> - 2016-01-01 14:46 -0600
      Re: We will be moving to GitHub Paul Rubin <no.email@nospam.invalid> - 2016-01-01 13:19 -0800
    Re: We will be moving to GitHub Ben Finney <ben+python@benfinney.id.au> - 2016-01-02 18:02 +1100
    Re: We will be moving to GitHub Michael Torrie <torriem@gmail.com> - 2016-01-02 20:31 -0700
    GitHub's “pull request” is proprietary lock-in (was: We will be moving to GitHub) Ben Finney <ben+python@benfinney.id.au> - 2016-01-03 15:43 +1100
      Re: GitHub's ³pull request² is proprietary lock-in (was: We will be moving to GitHub) Michael Vilain <vilain@NOspamcop.net> - 2016-01-02 20:56 -0800
        Re: GitHub's ³pull request² is proprietary lock-in Random832 <random832@fastmail.com> - 2016-01-03 02:04 -0500
          Re: GitHub's ³pull request² is proprietary lock-in Christian Gollwitzer <auriocus@gmx.de> - 2016-01-03 08:44 +0100
            Re: GitHub's ³pull request² is proprietary lock-in Ben Finney <ben+python@benfinney.id.au> - 2016-01-03 19:03 +1100
              Re: GitHub's ³pull request² is proprietary lock-in Christian Gollwitzer <auriocus@gmx.de> - 2016-01-03 09:33 +0100
                Re: GitHub's ³pull request² is proprietary lock-in Ben Finney <ben+python@benfinney.id.au> - 2016-01-03 19:45 +1100
                Re: GitHub's ³pull request² is proprietary lock-in Chris Angelico <rosuav@gmail.com> - 2016-01-03 20:18 +1100
                Re: GitHub's ³pull request² is proprietary lock-in Random832 <random832@fastmail.com> - 2016-01-03 04:31 -0500
                Re: GitHub's ³pull request² is proprietary lock-in Paul Rubin <no.email@nospam.invalid> - 2016-01-03 01:50 -0800
                Re: [python] Re: GitHub's ³pull request² is proprietary lock-in "W. Trevor King" <wking@tremily.us> - 2016-01-03 01:42 -0800
                Re: GitHub's ³pull request² is proprietary lock-in Ben Finney <ben+python@benfinney.id.au> - 2016-01-03 20:46 +1100
                Re: GitHub's ³pull request² is proprietary lock-in Chris Angelico <rosuav@gmail.com> - 2016-01-03 21:17 +1100
                Re: GitHub's ³pull request² is proprietary lock-in Chris Angelico <rosuav@gmail.com> - 2016-01-03 21:24 +1100
                Re: GitHub's ³pull request² is proprietary lock-in Paul Rubin <no.email@nospam.invalid> - 2016-01-03 02:42 -0800
                Re: GitHub's ³pull request² is proprietary lock-in Chris Angelico <rosuav@gmail.com> - 2016-01-03 23:33 +1100
                Re: GitHub's ³pull request² is proprietary lock-in Paul Rubin <no.email@nospam.invalid> - 2016-01-03 21:29 -0800
                Re: GitHub's ³pull request² is proprietary lock-in Christian Gollwitzer <auriocus@gmx.de> - 2016-01-04 08:02 +0100
          Re: GitHub's ©¯pull request© is proprietary lock-in Michael Vilain <vilain@NOspamcop.net> - 2016-01-03 12:51 -0800
        Re: GitHub's �pull request� is proprietary lock-in Michael Torrie <torriem@gmail.com> - 2016-01-03 08:05 -0700
        Re: GitHub's �pull request� is proprietary lock-in Michael Torrie <torriem@gmail.com> - 2016-01-03 08:14 -0700
      Re: GitHub's “pull request” is proprietary lock-in Kevin Walzer <kw@codebykevin.com> - 2016-01-03 16:58 -0500
      Re: GitHub's “pull request” is proprietary lock-in m <mvoicem@gmail.com> - 2016-01-04 11:21 +0100
        Re: GitHub's “pull request” is proprietary lock-in Michael Torrie <torriem@gmail.com> - 2016-01-04 10:41 -0700
          Re: GitHub's "pull request" is proprietary lock-in Josef Pktd <josef.pktd@gmail.com> - 2016-01-04 13:29 -0800
          Re: GitHub's “pull request” is proprietary lock-in m <mvoicem@gmail.com> - 2016-01-05 01:24 +0100
    Re: GitHub's “pull request” is proprietary lock-in Random832 <random832@fastmail.com> - 2016-01-03 19:51 -0500
    Re: GitHub's “pull request” is proprietary lock-in Michael Torrie <torriem@gmail.com> - 2016-01-03 21:16 -0700
    Re: GitHub's “pull request” is proprietary lock-in Random832 <random832@fastmail.com> - 2016-01-03 23:58 -0500

csiph-web