We can set a commit status that will show red if the user hasn’t signed the CLA (just like if Travis tests failed or so). No need to use a banner or anything.
This is a great idea. Almost any automated check we want to run against PRs can be captured as a Travis/CI test that shows up on the PR with its own status.
Nick
On Tue, 5 Jan 2016 at 14:19 Eric Snow <ericsnowcurrently@gmail.com> wrote:On Tue, Jan 5, 2016 at 11:13 AM, Brett Cannon <brett@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
devguideSure, 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? ;)
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