[core-workflow] My initial thoughts on the steps/blockers of the transition

Brett Cannon brett at python.org
Tue Jan 5 17:40:27 EST 2016


On Tue, 5 Jan 2016 at 14:19 Eric Snow <ericsnowcurrently at gmail.com> wrote:

> On Tue, Jan 5, 2016 at 11:13 AM, Brett Cannon <brett at python.org> wrote:
> > Day 1 summary
> > ============
> >
> > Decisions made
> > -----------------------
> >
> > Open issues
> > -------------------
>
> And a couple things that we are punting on:
>
> * code review tool (if GH proves undesirable)
>

Well, that's implicit if we find GitHub doesn't work for us for code
review. I don't think it requires explicitly calling it out.


> * separate (sub)repos for docs/tutorials--they could have a less
> restricted workflow than the rest of the cpython repo, a la the
> devguide
>

Sure, it can be mentioned.


>
> Both of these can wait until later, though they still deserve mention
> in the PEP.


You really don't like GitHub's review tool, huh? ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160105/d63fa203/attachment.html>


More information about the core-workflow mailing list