<head></head><body><!-- <signature> --><br><!-- </signature> --><img class="n1-open" width="0" height="0" style="border:0; width:0; height:0;" src="https://link.nylas.com/open/1oeantoc6n5zav9mkp4e6rmlq/local-bcd5514a-5c6f?r=Y29yZS13b3JrZmxvd0BweXRob24ub3Jn"><div class="gmail_quote">
On Jul 9 2016, at 6:12 pm, Brett Cannon <brett@python.org> wrote:
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div dir="ltr"><div><br></div><br><div><div dir="ltr">On Sat, 9 Jul 2016 at 13:01 Carol Willing <<a href="mailto:willingc@willingconsulting.com">willingc@willingconsulting.com</a>> wrote:<br></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Hi Brett,<div><div><br></div><div>One thing that could be done is to use a pull request template to notify users BEFORE they make a PR that the CPython mirror is not the correct place to submit contributions.</div><div><br></div><div>See <a href="https://github.com/python/cpython/pull/41&r=Y29yZS13b3JrZmxvd0BweXRob24ub3Jn" target="_blank">https://github.com/python/cpython/pull/41</a> as an example of the template.</div></div></div></blockquote><div><br></div><div>The problem with a template is it has to be checked into the cpython repository which will make sense once we migrate, but I don't know if it does while we are not moved over yet.</div></div><div><br></div></div></blockquote><div class="gmail_quote"><br></div><div class="gmail_quote">I was thinking that you could check-in to the GitHub mirror in a .git directory unless mirroring would blow it away each update. I wasn't thinking it would need to be in the hg hosting of CPython code.</div><div class="gmail_quote"><br></div><div class="gmail_quote">Removing it once the migration happens.</div><div class="gmail_quote"><br></div><div class="gmail_quote"><br></div><div class="gmail_quote"><br></div><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div dir="ltr"><div><div><br></div><div><br></div><div>-Brett</div><div> </div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div><br></div><div>Carol</div><br>---<div style="line-height:19.6px">Carol Willing</div><div style="line-height:19.6px"><br></div><div style="line-height:19.6px">Research Software Engineer</div><div style="line-height:19.6px">Project Jupyter @ Cal Poly SLO</div><div style="line-height:19.6px"><br></div><div style="line-height:19.6px">Director, Python Software Foundation</div><div style="line-height:19.6px"><br></div><div style="line-height:19.6px"><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;line-height:normal"><i>Signature strengths</i></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;line-height:normal"><i>Empathy - Relator - Ideation - Strategic - Learner</i></div></div><br></div></div><div><div>
On Jul 9 2016, at 8:59 am, Brett Cannon <<a href="mailto:brett@python.org" target="_blank">brett@python.org</a>> wrote:
<br>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The problem with the python-tutor org is we don't control it and we don't know whose it is.<div><br></div><div>As for turning off the PRs for Python/cpython, GH doesn't provide a way to do that. Best we can do is reply to the PRs to say the repo is just a mirror and PRs are not accepted and get the transition done sooner rather than later (hoping to get the devguide moved this month; need to schedule it with the PDF infra team).<br><br><div><div dir="ltr">On Fri, Jul 8, 2016, 18:30 Senthil Kumaran <<a href="mailto:senthil@uthcode.com" target="_blank">senthil@uthcode.com</a>> wrote:<br></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I noticed two issues wherein the reporters were confused with the github mirrors of cpython.<div><br></div><div>1. <a href="http://bugs.python.org/issue25435#msg253159&r=YnJldHRAcHl0aG9uLm9yZw==&r=Y29yZS13b3JrZmxvd0BweXRob24ub3Jn" target="_blank">http://bugs.python.org/issue25435#msg253159</a></div><div><br></div><div>A pull request was raised against the github mirror.</div><div><br></div><div>2. <a href="http://bugs.python.org/issue27466&r=YnJldHRAcHl0aG9uLm9yZw==&r=Y29yZS13b3JrZmxvd0BweXRob24ub3Jn" target="_blank">http://bugs.python.org/issue27466</a></div><div><br></div><div>Issue was raised against a github mirror: <a href="https://github.com/python-git/python/issues/6&r=YnJldHRAcHl0aG9uLm9yZw==&r=Y29yZS13b3JrZmxvd0BweXRob24ub3Jn" target="_blank">https://github.com/python-git/python/issues/6</a></div><div><br></div><div>This project, <a href="https://github.com/python-git&r=YnJldHRAcHl0aG9uLm9yZw==&r=Y29yZS13b3JrZmxvd0BweXRob24ub3Jn" target="_blank">https://github.com/python-git</a> should either redirect to <a href="http://github.com/python&r=YnJldHRAcHl0aG9uLm9yZw==&r=Y29yZS13b3JrZmxvd0BweXRob24ub3Jn" target="_blank">github.com/python</a> or shutdown.</div><div>And the <a href="http://github.com/python&r=YnJldHRAcHl0aG9uLm9yZw==&r=Y29yZS13b3JrZmxvd0BweXRob24ub3Jn" target="_blank">github.com/python</a> project should disallow Pull Request / Issue Creation.</div><div><br></div><div>Who can I work with (in the python infra team) to accomplish these things? Also if anyone else has suggestions please share it in this email thread.</div><div><br></div><div>Thank you,</div><div>Senthil</div><div><br></div></div>
_______________________________________________<br>
core-workflow mailing list<br>
<a href="mailto:core-workflow@python.org" target="_blank">core-workflow@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/core-workflow&r=YnJldHRAcHl0aG9uLm9yZw==&r=Y29yZS13b3JrZmxvd0BweXRob24ub3Jn" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/core-workflow</a><br>
This list is governed by the PSF Code of Conduct: <a href="https://www.python.org/psf/codeofconduct&r=YnJldHRAcHl0aG9uLm9yZw==&r=Y29yZS13b3JrZmxvd0BweXRob24ub3Jn" rel="noreferrer" target="_blank">https://www.python.org/psf/codeofconduct</a></blockquote></div></div>
</blockquote>
</div></div></blockquote></div></div>
</blockquote>
</div></body>