Proposed fix4all rotation for May / June 2017

Here's a proposed fix4all schedule through the next 8 weeks:

Week commencing	Person	Team
June 26, 2017	@godfat	CI/CD
June 19, 2017	@tiagonbotelho	Discussion
June 12, 2017	@annabeldunstone	Frontend AC
June 5, 2017	@WarheadsSE	Build
May 29, 2017	@fatihacet	Frontend DC
May 22, 2017	@mkozono	Platform
May 15, 2017	@dbalexandre	Discussion
May 8, 2017	@jivanvl	Frontend AC

@godfat is a repeat, and there are still a few people who haven't done fix4all at all yet. However, this isn't the first repeat, and if we bias towards people who haven't yet done a rotation, we'll also bias towards frontenders 😕 I've also excluded release managers for 9.2 and 9.3.

The above perhaps implies more science than there is; I just used the following, and re-rolled until it looked 'fair' 🤷

~/Code/www-gitlab-com{master}$ bin/pick-random-team-members 8 --reports-to='Platform Lead' --reports-to='Build Lead' --reports-to='Discussion Lead' --reports-to='CI/CD Lead' --reports-to='Edge Lead' --reports-to='Frontend DC Lead' --reports-to='Frontend AC Lead'

Is this good for everyone?

/cc @jschatz1 @timzallmann @ayufan @marin @DouweM @rymai @stanhu