17. @jonlives
The Chef Community
▪ All roles open to everybody
▪ “RFC” driven
▪ Weekly meetings to discuss RFCs
▪ Chef employees don’t get any more power than we do
▪ You can work on the overall project, or things you
specifically care about
19. @jonlives
Project Lead
▪ Adam Jacob (usually)
▪ Resolves disputes
▪ Provides vision and roadmap
▪ Has universal veto power
▪ There can be only one
20. @jonlives
Chef Components
▪ Core, testing, OS-specific etc
▪ People who most care
▪ Maintainers have full agency
▪ Lt exists to resolve disputes
▪ Lt also has veto power
(AFAIK never used thus far)
21. @jonlives
Chef RFCs
▪ “Request for Comment”
▪ Can be proposed by anybody
▪ RFC editors help guide you through the process
▪ Once approved, anyone can implement
▪ Proposal doesn’t mean *you* have to implement it
22. @jonlives
So, what do I do?
▪ RFC Editor
▪ Redhat / CentOS Lieutenant
▪ Maintainer for Redhat and Core components
▪ These are the things I care most about
▪ I got involved to “safeguard” those things
23. @jonlives
“I want to go on holiday for a
month. Would you be
project lead while I’m
away?”
- Adam Jacob, 2015