Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Mark Lawrence <breamoreboy@yahoo.co.uk>
Newsgroups: comp.lang.python
Subject: Re: We will be moving to GitHub
Date: Fri, 1 Jan 2016 20:48:30 +0000
Lines: 28
Message-ID: <mailman.149.1451681345.11925.python-list@python.org>
References: <n66kmg$ig$1@ger.gmane.org> <CAJ4+4apactRU7=7Civoy_csOb2i0iXn=SHtBVYpH1YNVTt0SaQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <CAJ4+4apactRU7=7Civoy_csOb2i0iXn=SHtBVYpH1YNVTt0SaQ@mail.gmail.com>
Precedence: list
Xref: csiph.com comp.lang.python:101119

On 01/01/2016 20:03, paul.hermeneutic@gmail.com wrote:
> Mark, it is good to know that a decision has been made so that we can move
> forward.
>
> Is there a summary document that discusses the options examined and why
> others did not meet the requirements? I am -NOT- trying to dredge up
> arguments about the choice. I am guessing that there have been some.
>
> If this fact-based decision was based solely on the fact that the BDFL
> prefers GitHub, please just say so. It is clear that git is a capable tool.
>

There is no point in targetting any queries at me, I'm just the messenger :)

I've loosly followed the discussion on the core workflow mailing list, 
but frankly much of that said goes right over my head, as my knowledge 
of GitHub, GitLab, Mercurial and all the rest of them is roughly zero.

There is all ready disagreement over the decision.  I'll sit back and 
let the core developers sort that out, confident that eventually we'll 
end up with working processes backed up by working systems.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.

Mark Lawrence