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
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
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
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
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
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
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
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).