Two things.

One, I will add to the chorus of people who don't like Gerrit, and this is from using the project. There is no chance we are switching to Gerrit based on our other options.

Two, it's too late to propose another workflow option anyway as we already spent this year getting proposals together. As outlined in my personal notes at , I am only considering GitHub and GitLab at this point; all other options are too late to be considered. If you have comments to make you can leave them on the doc, although since this is geared towards improving the workflow for core devs that means comments from people in that capacity will be valued the most.

I'm collecting feedback on the workflows from people until Dec 1. I'm going to take the feedback and questions people have back to the people who have made the proposals for answers by Dec 15 so I can make a decision by Jan 1.

On Mon, 23 Nov 2015 at 07:28 Brian Curtin <> wrote:
On Mon, Nov 23, 2015 at 7:01 AM, Donald Stufft <> wrote:
> Openstack is a bit different because almost every contributor is being paid to work on it. That means that they don’t have to worry (as much) about on boarding pain because those people are being paid to sit there and learn how to use the tooling. CPython on the other hand is almost entirely worked on by volunteers so on boarding pain is very likely to just have people drop off instead of trying to learn the toolchain.

There is close to zero chance I would have gotten into CPython while
sitting on my couch in the evenings if it used Gerrit. This is
actually a pretty big worry I have with a Gerrit-using project I work
on, in that we're only ever going to attract insiders instead of
having users get involved.
core-workflow mailing list
This list is governed by the PSF Code of Conduct: