PR duty

[Meta]

On Wednesday, 4 April 2018 at 05:31:10 UTC, Andrei Alexandrescu 
wrote:
> Hi folks, I was thinking of the following.
>
> To keep the PR queue trim and in good shape, we'd need at least 
> one full-time engineer minding it. I've done that occasionally, 
> and the queue size got shorter, but I couldn't do much else 
> during that time.
>
> I was thinking, we can't afford a full-time engineer, and even 
> if we did, we'd probably have other important matters for that 
> engineer as well. However, what we can afford - and indeed 
> already benefit from - is a quantum of time from each of many 
> volunteers. By organizing that time better we may be able to 
> get more output. Here's what I'm thinking.
>
> Let's define a "PR duty" role that is one week long for each of 
> a pool of volunteers. During that week, the person on PR duty 
> focuses on minding github queues - merge trivial PRs, ping 
> authors of old PRs, email decision makers for specific items in 
> PRs, etc. Then the week ends and the role is handed off to the 
> next person in the pool.
>
> A calendar maintained by an impartial person - maybe we can ask 
> Mike - would keep track of everything.

On the actual topic of the thread, the scrum master for this 
sprint could have some of these duties rolled in as well. 
Therefore, for a given sprint, they would be in charge of:

- taking care of trivial PRs
- pinging authors of old PRs(?)
- email decision makers
- make sure previously decided-upon action items are taken care 
of before the next sprint
- being a central point of contact for questions on items for 
that sprint
- generally being available on Slack and coordinating the team

I wonder if the Github bot can be configured to automatically tag 
new items for the next sprint... Also, I put a question mark 
beside "pinging authors of old PRs" because that seems like 
something the bot could also do automatically (maybe ping every 2 
weeks, and if the submitter has not responded after 3 pings it's 
auto-closed).