(original) (raw)



On Sun, 10 Jan 2016 at 09:48 Ryan Gonzalez <rymg19@gmail.com> 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 <brett@python.org> 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


\--
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.