Wednesday, May 24, 2017

Chef Community Engineering – Quarterly Update

Chef Community Engineering – Quarterly Update
// Chef Blog

We're excited to be in Austin, TX this week for ChefConf. Today we're hosting a Community Summit so it's a great time to reflect on some of the amazing things the community and community engineering team at Chef completed in the first three months of the year!


The Chef Supermarket is here to make it easy to be successful with Chef through sharing the successes of a community of practitioners. Use the public Supermarket to collaborate with the community or install your own private Supermarket and collaborate with your co-workers.

Cookbook Engineering

The cookbook engineering team is responsible for managing and modernizing the Chef-managed cookbooks that are published to the Supermarket. These cookbooks serve as a guide for some good practices for developing cookbooks and help automate common infrastructure components.

Open Source Projects

Chef is based on open-source software and a thriving community of contributors is important to the continued success of the project. Lots of PRs were merged and there was at least one release per week across a number of different tools in the ecosystem, test-kitchen, ChefSpec, foodcritic, and the like.

Come together!

As a community we gather online and in-person. The first three months of the year saw growing participation in both Slack and our mailing list.


The community around compliance automation is really starting to take off, too. In the first three months of the year there were eleven first-time contributors to InSpec and more compliance profiles were published to the Supermarket.


Habitat continues to see very rapid growth and adoption!

Remember, if you are unable to join us in Austin, you can live stream the ChefConf keynotes on Tuesday and Wednesday.

If you're at the conference, come find me for a hug!

The post Chef Community Engineering – Quarterly Update appeared first on Chef Blog.


Read in my feedly

Sent from my iPhone

No comments:

Post a Comment