<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Thu, 7 Jan 2016 at 13:06 francismb <<a href="mailto:francismb@email.de">francismb@email.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
On 01/05/2016 07:13 PM, Brett Cannon wrote:<br>
> Day 1 summary<br>
> ============<br>
><br>
> Decisions made<br>
> -----------------------<br>
><br>
> - Seems like our current commit ID -> URL service can be updated to handle<br>
> our transition<br>
><br>
><br>
> Open issues<br>
> -------------------<br>
> - What tools and commands will we use to convert the repos?<br>
> - How do we want to handle Misc/NEWS?<br>
> - What are the exact commands we are going to expect core devs to run<br>
> (which will be documented in the devguide)?<br>
> - Who to use for CI (although Donald is the only one to speak up and likes<br>
> Travis as do I, so this might be decided)?<br>
> - Who to use for code coverage (Donald has suggested codecov)?<br>
> - Do we want to add GitHub login support for b.p.o to ease in adding<br>
> people's GitHub username and to minimize the need for two accounts to<br>
> propose a patch that has a corresponding issue?<br>
><br>
<br>
a small question: could it be possible to access (some of) the services<br>
in a REST-ish form through a wrapper on <a href="https://www.python.org/dev" rel="noreferrer" target="_blank">https://www.python.org/dev</a><br>
<br>
I mean something like:<br>
<br>
Python-<br>
community-<br>
Service     External-Service        Python-Website-Address-Wrapper<br>
====================================================================<br>
cpython     GitHub       <a href="https://www.python.org/dev/cpython" rel="noreferrer" target="_blank">https://www.python.org/dev/cpython</a></blockquote><div><br></div><div>We will probably have <a href="http://git.python.org">git.python.org</a> handle this.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
issues      ...          <a href="https://www.python.org/dev/cpython-issues" rel="noreferrer" target="_blank">https://www.python.org/dev/cpython-issues</a></blockquote><div><br></div><div><a href="http://bugs.python.org">bugs.python.org</a> already exists.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
website     GitHub       <a href="https://www.python.org/dev/website" rel="noreferrer" target="_blank">https://www.python.org/dev/website</a><br>
buildbots   ...          <a href="https://www.python.org/dev/cpython-buildbots" rel="noreferrer" target="_blank">https://www.python.org/dev/cpython-buildbots</a></blockquote><div><br></div><div><a href="http://buildbot.python.org">buildbot.python.org</a> already exists.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
devinabox   GitHub       <a href="https://www.python.org/dev/cpython-devinabox" rel="noreferrer" target="_blank">https://www.python.org/dev/cpython-devinabox</a></blockquote><div><br></div><div>It's just a repo and not special enough to deserve a unique URL.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
coverage    codecov      <a href="https://www.python.org/dev/cpython-coverage" rel="noreferrer" target="_blank">https://www.python.org/dev/cpython-coverage</a></blockquote><div><br></div><div>This might be worth a URL if we get it set up.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
docs        GitHub       <a href="https://www.python.org/dev/cpython-docs" rel="noreferrer" target="_blank">https://www.python.org/dev/cpython-docs</a></blockquote><div><br></div><div>That's <a href="http://docs.python.org">docs.python.org</a>.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
...<br>
<br>
<br>
Couldn't be then some bots external-provider independent/decoupled?<br></blockquote><div><br></div><div>The plan is that anything we write for this will be sufficiently decoupled from GitHub that changing hosts will just require updating abstraction code to work with different REST APIs and not a major rewrite of the bot itself.</div><div><br></div><div>-Brett</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
Thanks in advance!<br>
<br>
francis<br>
<br>
PS: Sorry if I got some external-service wrong<br>
<br>
_______________________________________________<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" 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" rel="noreferrer" target="_blank">https://www.python.org/psf/codeofconduct</a><br>
</blockquote></div></div>