[infra][upstream-institute] Bot to vote on changes in the sandbox
tony at bakeyournoodle.com
Fri Feb 1 04:33:49 UTC 2019
During the Berlin forum the idea of running some kinda of bot on the
sandbox  repo cam up as another way to onboard/encourage
The general idea is that the bot would:
1. Leave a -1 review on 'qualifying' changes along with a request for
some small change
2. Upon seeing a new patchset to the change vote +2 (and possibly +W?)
on the change
Showing new contributors approximately what code review looks like,
and also reduce the human requirements. The OpenStack Upstream
Institute would make use of the bot and we'd also use it as an
interactive tutorial from the contributors portal.
I think this can be done as a 'normal' CI job with the following
* Because we want this service to be reasonably robust we don't want to
code or the job definitions to live in repo so I guess they'd need to
live in project-config. The bot itself doesn't need to be
stateful as gerrit comments / meta-data would act as the store/state
* We'd need a gerrit account we can use to lodge these votes, as using
'proposal-bot' or tonyb would be a bad idea.
My initial plan would be to develop the bot locally and then migrate it
into the opendev infra once we've proven its utility.
So thoughts on the design or considerations or should I just code
something up and see what it looks like?
 The details of what counts as qualifying can be fleshed out later
but there needs to be something so that contributors using the sandbox
that don't want to be bothered by the bot wont be.
 So it would a) be faster than typical and b) not all new changes are
greeted with a -1 ;P
 Another repo would be better as project-config is trusted we can't
use Depends-On to test changes to the bot itself, but we need to
consider the bots access to secrets
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: not available
More information about the openstack-discuss