Re: [Python-Dev] GitHub migration planning has started

2016-01-10 Thread Brett Cannon 
On Sun, 10 Jan 2016 at 19:53 Terry Reedy  wrote:

> On 1/10/2016 12:43 PM, Brett Cannon wrote:
> > For those of you who have not heard, I made the decision a little over a
> > week ago to move Python's development from our home-grown workflow to
> > one hosted on GitHub (mainly for code hosting and code review; we're
> > keeping bugs.python.org  for our issue tracker).
> > The hope is that this will let core developers work through patches
> > faster so that we have a better turn-around time while being at least as
> > good as our current workflow for external contributors (but I will be
> > shocked if it isn't better). There are also people involved with the
> > migration who plan to put in the effort to make sure external
> > contributors can still submit patches without ever interacting with
> GitHub.
> >
> > If you want to help with the transition, then feel free to join the
> > core-workflow mailing list where all the discussions on the details of
> > the migration are occurring (including the PEP I'm starting to write to
> > outline the steps we will be taking):
> > https://mail.python.org/mailman/listinfo/core-workflow
>
> Is there a gmane mirror, or do you think this is too limited (and
> temporary) for that?
>

I have no idea if a gmane mirror was set up.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] GitHub migration planning has started

2016-01-10 Thread Terry Reedy 

On 1/10/2016 12:43 PM, Brett Cannon wrote:

For those of you who have not heard, I made the decision a little over a
week ago to move Python's development from our home-grown workflow to
one hosted on GitHub (mainly for code hosting and code review; we're
keeping bugs.python.org  for our issue tracker).
The hope is that this will let core developers work through patches
faster so that we have a better turn-around time while being at least as
good as our current workflow for external contributors (but I will be
shocked if it isn't better). There are also people involved with the
migration who plan to put in the effort to make sure external
contributors can still submit patches without ever interacting with GitHub.

If you want to help with the transition, then feel free to join the
core-workflow mailing list where all the discussions on the details of
the migration are occurring (including the PEP I'm starting to write to
outline the steps we will be taking):
https://mail.python.org/mailman/listinfo/core-workflow


Is there a gmane mirror, or do you think this is too limited (and 
temporary) for that?


--
Terry Jan Reedy

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] GitHub migration planning has started

2016-01-10 Thread Martin Panter 
On 11 January 2016 at 03:52, Terry Reedy  wrote:
> On 1/10/2016 12:43 PM, Brett Cannon wrote:
>> If you want to help with the transition, then feel free to join the
>> core-workflow mailing list where all the discussions on the details of
>> the migration are occurring (including the PEP I'm starting to write to
>> outline the steps we will be taking):
>> https://mail.python.org/mailman/listinfo/core-workflow
>
>
> Is there a gmane mirror, or do you think this is too limited (and temporary)
> for that?

I guess this is it: 
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] GitHub migration planning has started

2016-01-10 Thread Terry Reedy 

On 1/11/2016 12:58 AM, Martin Panter wrote:

On 11 January 2016 at 03:52, Terry Reedy  wrote:

On 1/10/2016 12:43 PM, Brett Cannon wrote:

If you want to help with the transition, then feel free to join the
core-workflow mailing list where all the discussions on the details of
the migration are occurring (including the PEP I'm starting to write to
outline the steps we will be taking):
https://mail.python.org/mailman/listinfo/core-workflow



Is there a gmane mirror, or do you think this is too limited (and temporary)
for that?


I guess this is it: 


Thanks.  When I right-click news.gmane.org (in Thunderbird) and select 
subscribe, it does not appear in the 'Current groups' tab.  I just 
discovered that there is also a 'New groups' tab that has it.


--
Terry Jan Reedy

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] GitHub migration planning has started

2016-01-10 Thread Brett Cannon 
For those of you who have not heard, I made the decision a little over a
week ago to move Python's development from our home-grown workflow to one
hosted on GitHub (mainly for code hosting and code review; we're keeping
bugs.python.org for our issue tracker). The hope is that this will let core
developers work through patches faster so that we have a better turn-around
time while being at least as good as our current workflow for external
contributors (but I will be shocked if it isn't better). There are also
people involved with the migration who plan to put in the effort to make
sure external contributors can still submit patches without ever
interacting with GitHub.

If you want to help with the transition, then feel free to join the
core-workflow mailing list where all the discussions on the details of the
migration are occurring (including the PEP I'm starting to write to outline
the steps we will be taking):
https://mail.python.org/mailman/listinfo/core-workflow
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] GitHub migration planning has started

2016-01-10 Thread Ryan Gonzalez 
Is it possible to contribute to this, even if you're not part of the core dev 
team?

On January 10, 2016 11:43:48 AM CST, Brett Cannon  wrote:
>For those of you who have not heard, I made the decision a little over
>a
>week ago to move Python's development from our home-grown workflow to
>one
>hosted on GitHub (mainly for code hosting and code review; we're
>keeping
>bugs.python.org for our issue tracker). The hope is that this will let
>core
>developers work through patches faster so that we have a better
>turn-around
>time while being at least as good as our current workflow for external
>contributors (but I will be shocked if it isn't better). There are also
>people involved with the migration who plan to put in the effort to
>make
>sure external contributors can still submit patches without ever
>interacting with GitHub.
>
>If you want to help with the transition, then feel free to join the
>core-workflow mailing list where all the discussions on the details of
>the
>migration are occurring (including the PEP I'm starting to write to
>outline
>the steps we will be taking):
>https://mail.python.org/mailman/listinfo/core-workflow
>
>
>
>
>___
>Python-Dev mailing list
>Python-Dev@python.org
>https://mail.python.org/mailman/listinfo/python-dev
>Unsubscribe:
>https://mail.python.org/mailman/options/python-dev/rymg19%40gmail.com

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] GitHub migration planning has started

2016-01-10 Thread Brett Cannon 
On Sun, 10 Jan 2016 at 09:48 Ryan Gonzalez  wrote:

> Is it possible to contribute to this, even if you're not part of the core
> dev team?
>

Sure! There's going to be plenty of code to write, decisions to be made,
etc. While I will making most of the final decisions, I will be asking for
feedback from people, asking some to go off and write some code, etc.

-Brett


>
> On January 10, 2016 11:43:48 AM CST, Brett Cannon 
> wrote:
>
>> For those of you who have not heard, I made the decision a little over a
>> week ago to move Python's development from our home-grown workflow to one
>> hosted on GitHub (mainly for code hosting and code review; we're keeping
>> bugs.python.org for our issue tracker). The hope is that this will let
>> core developers work through patches faster so that we have a better
>> turn-around time while being at least as good as our current workflow for
>> external contributors (but I will be shocked if it isn't better). There are
>> also people involved with the migration who plan to put in the effort to
>> make sure external contributors can still submit patches without ever
>> interacting with GitHub.
>>
>> If you want to help with the transition, then feel free to join the
>> core-workflow mailing list where all the discussions on the details of the
>> migration are occurring (including the PEP I'm starting to write to outline
>> the steps we will be taking):
>> https://mail.python.org/mailman/listinfo/core-workflow
>>
>> --
>>
>> Python-Dev mailing list
>> Python-Dev@python.org
>> https://mail.python.org/mailman/listinfo/python-dev
>> Unsubscribe: 
>> https://mail.python.org/mailman/options/python-dev/rymg19%40gmail.com
>>
>>
> --
> Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] GitHub migration planning has started

2016-01-10 Thread Stephane Wirtel 
On 01/10, Brett Cannon wrote:
> For those of you who have not heard, I made the decision a little over a
> week ago to move Python's development from our home-grown workflow to one
> hosted on GitHub (mainly for code hosting and code review; we're keeping
> bugs.python.org for our issue tracker). The hope is that this will let core
> developers work through patches faster so that we have a better turn-around
> time while being at least as good as our current workflow for external
> contributors (but I will be shocked if it isn't better). There are also
> people involved with the migration who plan to put in the effort to make
> sure external contributors can still submit patches without ever
> interacting with GitHub.
> 
> If you want to help with the transition, then feel free to join the
> core-workflow mailing list where all the discussions on the details of the
> migration are occurring (including the PEP I'm starting to write to outline
> the steps we will be taking):
> https://mail.python.org/mailman/listinfo/core-workflow

> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: 
> https://mail.python.org/mailman/options/python-dev/stephane%40wirtel.be

\o/

Already on core-workflow.

-- 
Stéphane Wirtel - http://wirtel.be - @matrixise
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com