On 15 June 2018 at 20:49, Nick Coghlan <ncoghlan@gmail.com> wrote:
On 15 June 2018 at 20:27, Nick Coghlan <ncoghlan@gmail.com> wrote:
On 15 June 2018 at 11:34, Brett Cannon <brett@python.org> wrote:
ther big issue with bpo as CLA host is we don't have easy way that can
let the-knights-who-say-ni update the label in the PR once the contributor has signed the CLA.
I've been thinking about this and I think we can with a bit of effort (basically we need some way to know what repos Ni is hooked up to and then a cron job that checks all "CLA not signed" PRs). We could also provide a URL people can visit to trigger a check.
bugs.python.org could also be updated to hit a knights-who-say-ni HTTPS endpoint whenever the CLA field or GitHub username field in a user account gets modified.
It's just a Python project - modifying it shouldn't be noticeably more scary than modifying any of the other web bots, and if there are process problems with that (which we know there are), then the first question should be "How do we help the bugs.python.org maintainers streamline their process?", not "How do we create yet another service to maintain?".
I've filed http://psf.upfronthosting.co.za/roundup/meta/issue655 to help turn this into a concrete process improvement proposal.
Ezio was happy with the idea of migrating the meta-tracker, so the discussion of migrating the instance repo has moved to https://github.com/python/bugs.python.org/issues/2 (where Ernest has chimed in with several relevant technical details that suggest this should be quite a feasible change to make - the downstream Roundup fork would remain on hg.python.org, but the CPython specific templates, plugins, hook scripts, etc, could all migrate over to the new repo) Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia