This defines an extension to the resource DSL to allow file-type resources
(file, cookbook_file, template, remote_file) to verify content before
continuing. The common use case for this is checking server configuration
files are valid. This RFC had been provisionally accepted several weeks ago but
was only merged this week.
RFC 28: Mailing List Migration
This RFC defines the plan to migrate the Chef mailing lists from locally-hosted
Sympa to Google Groups.
RFC 29: Governance Policy
This RFC defines the new governance policy for Chef as a project, establishing
an advisory board to provide input on the future of Chef. See my post for more information and an overview of the policy.
RFC 30: Maintenance Policy
This RFC defines how Chef will be maintained going forward. This includes how
how people will get commit access and how we will determine the roadmap. See my post for more information and an overview of the
This lays out an overall plan for rebuilding chef-solo on top of chef-client’s --local mode. This will be done incrementally, and 100% compatibility with
solo as it stands today is a requirement.
RFCs Being Discussed
Four RFCs have been discussed since the last community meeting.
Adding PowerShell DSC Module Resource
This proposes adding a Chef resource to configure PowerShell DSC modules.
Token Authentication for Chef Server
This proposal outlines adding a token-based authentication mechanism to Chef
Root Aliases in Cookbooks
This proposes aliases for commonly used files in cookbooks to simplify the
The proposal outlines adding a testing DSL to Chef recipes based on RSpec and
Serverspec to allow for easier testing integration.
Due to the Thanksgiving holiday in the US, the next developer meeting has
been rescheduled to Tuesday, November 25th at 9AM PST.
As always, the meeting will be held in the #chef-hacking channel on Freenode
IRC. Hope to see you there!