[Dev] Rotating build sheriff duties?

[Andi Vajda]

>> We would obviously need a page describing what to do and how.
>> 
>> What things do you think could be automated?
>
> Almost everything on your original list, actually.

+1

> Meanwhile, we could save the should's and shaming for things that matter more 
> than raw procedure, especially since it's clear that they aren't working very 
> well for this.  To be honest, the idea that we should do *more* of it rather 
> than less, strikes me as "The kids are being rowdy, let's try hitting them 
> harder."  :)

+1

> (Actually, it's even crazier than that.  Apart from Tinderbox monitoring, It 
> sounds to me like we're talking about having a rotating duty to keep an eye 
> on everybody else, instead of having people be responsible for doing their 
> own good work *every day*.  That sounds to me like an organizational failure, 
> because either some of this stuff really isn't that important, or the 
> organization is failing to communicate its importance, or is unwilling to 
> actually make the investments in automation and education (including coaching 
> and/or consequences) to get the issues resolved.  (I leave out the 
> possibility of "bad eggs" being an issue, because the continued presence of 
> bad eggs would itself be an organizational failure; i.e. failure to 
> coach/discipline/remove.))

+1

> I think that the intent of all of the things you mentioned can be met through 
> greater automation.  I expect I'll be getting involved in the build process 
> and our tools during the 0.7 timeframe, so I'll definitely be looking for 
> opportunities to address those issues.

If I can help with this, I'd be glad to.
But watching over my colleagues' shoulder, no thanks.

Andi..