Hey there fellow core-workflowers; I've been following the GitHub transition for a while now, and have some questions (which may have been answered already, I apologize in advance if so!).
So, I read the PEP again to see if it was answered, seems it wasn't clear (or I'm visually impaired, you get to choose). I understand that there's already a semi-official mirror of the cpython repo on GitHub, and I've been wondering why it isn't enough for our needs. Sure, a bunch of stuff needs to be done (like the CLA bot and the PR <-> issue linking), but surely they could be done on the current mirror. My workflow uses the GitHub mirror, and my patches are compatible with b.p.o and Rietveld. Is there something I'm missing as to why we can't re-use this one? Then, as someone who's been using git and GitHub for almost everything code-related and never touched Mercurial, is there something I can do to help with the transition? I would really love a more accessible workflow for both core developers and external contributors as soon as possible (don't we all?), so if I can help I'd love to; I do realize I'm a bit late to the party though. Keep up the good work! -Emanuel _______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
