28
Community Powered Chef How I ended up being left in charge of Chef

Community Powered Chef

  • Upload
    chef

  • View
    301

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Community Powered Chef

Community Powered Chef

How I ended up being left in charge of Chef

Page 2: Community Powered Chef

@jonlives

Jon Cowie

Staff Operations Engineer

Page 3: Community Powered Chef
Page 4: Community Powered Chef

@jonlives

2010, working at

Page 5: Community Powered Chef

@jonlives

Close encounters of the #hugops kind

Joshua Timberman @jtimberman

(Gives awesome hugs)

Page 6: Community Powered Chef

@jonlives

The Cheffening

Page 7: Community Powered Chef

@jonlives

Too much Firefightening

Page 8: Community Powered Chef

@jonlives

It’s a Chef system - I know this!

Page 9: Community Powered Chef

@jonlives

“Hmm, this doesn’t work quite the way I want it to…”

Page 10: Community Powered Chef

@jonlives

…so I started writing and open sourcing tools.

Page 11: Community Powered Chef

@jonlives

Sometimes, I talk about the problems I’ve been

trying to solve…

Page 12: Community Powered Chef

@jonlives

…and sometimes I get a bit carried away.

Page 13: Community Powered Chef

@jonlives

And it’s all because of (and for) the Chef community.

Page 14: Community Powered Chef

@jonlives

“The community is changing…builders are becoming consumers.”

(Thought leadership by @nathenharvey)

Page 15: Community Powered Chef

@jonlives

Your perspective is more important than ever!

Page 16: Community Powered Chef

@jonlives

And with Chef, you have the power.

Page 17: Community Powered Chef

@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

Page 18: Community Powered Chef

@jonlives

Page 19: Community Powered Chef

@jonlives

Project Lead▪ Adam Jacob (usually)

▪ Resolves disputes

▪ Provides vision and roadmap

▪ Has universal veto power

▪ There can be only one

Page 20: Community Powered Chef

@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)

Page 21: Community Powered Chef

@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

Page 22: Community Powered Chef

@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

Page 23: Community Powered Chef

@jonlives

“I want to go on holiday for a month. Would you be project lead while I’m

away?”

- Adam Jacob, 2015

Page 24: Community Powered Chef

@jonlives

“Hi Barry, I’m in charge of your product for a

month”

- me, ChefConf 2015

Page 25: Community Powered Chef

@jonlives

That is how much Chef trust and empower us to make it

what we want it to be.

Page 26: Community Powered Chef

@jonlives

And we need your help!

Page 27: Community Powered Chef

@jonlives

http://jonliv.es/book

Discount Code: AUTHD

40% off Print 50% off Digital

Page 28: Community Powered Chef

@jonlives

Thanks! Questions?

@jonlives / http://jonliv.es / [email protected]