[Dev] Rotating build sheriff duties?

Philippe Bossut pbossut at osafoundation.org
Wed Dec 7 16:49:16 PST 2005


Heikki Toivonen wrote:

>I am not so sure we can eliminate the sheriff completely, but if I can
>be proven wrong I would be happy. It also seems like nobody is
>disagreeing that we need sheriff currently because the tools are what
>they are.
>
>But since one wanted out: are there others who don't want to help out
>with sheriff duties while we improve the tools?
>  
>
I'll be happy to help and take my turn as a "sheriff". If nothing else, 
I'll learn something first hands with those tools and may even come up 
with ideas on how to improve them... :)

On the cost effectiveness of doing automating the tools: if the 
"sheriff" duty is taking 20% of one engineer every day (as suggested 
earlier in this thread), spending 4 weeks of one full time engineer 
automating it will pay for itself (we'll break even) in 20 weeks (5 
months). It makes a lot sense from a simple budget standpoint. I've the 
feeling that the economic outlook is even better than that (the sheriff 
duty taxing more than 20% of productivity and the tools taking less than 
4 weeks to develop...).

In the meantime though, I reinstantiate my offer to be a part "sheriff" 
team (a deputy so to speak.. ;) )so to make this less of a burden on 
Heikki and Bear.

Cheers,
- Philippe


More information about the Dev mailing list