# Chef 12 brainstorming

**URL:** <https://discourse.chef.io/t/chef-12-brainstorming/5524>\
**Category:** Chef Infra (archive)\
**Created:** [July 16, 2014, 2:47am UTC](https://discourse.chef.io/t/chef-12-brainstorming/5524 "2014-07-16T02:47:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tim\_Smith1](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/tim_smith1/32/283_2.png) [@Tim\_Smith1](https://discourse.chef.io/u/Tim_Smith1)\
**Post date:** [July 16, 2014, 2:47am UTC](https://discourse.chef.io/t/chef-12-brainstorming/5524/1 "2014-07-16T02:47:12Z")

</div>

I’m curious if there’s any brainstorming going on between the community and Chef Inc. about functionality for inclusion in the next major release of Chef (12). I see there’s a small wiki doc that hasn’t been updated in a year at [https://wiki.opscode.com/display/chef/Chef+12+Release+Checklist](https://wiki.opscode.com/display/chef/Chef+12+Release+Checklist) I think a lot of people could come up with some great minor/major changes that would really improve Chef for the next release. Some of the changes I had in mind seem too small for the full blown RFC process, but perhaps that’s where they should still be.

## -Tim

The information in this message may be confidential. It is intended solely  
for  
the addressee(s). If you are not the intended recipient, any disclosure,  
copying or distribution of the message, or any action or omission taken by  
you  
in reliance on it, is prohibited and may be unlawful. Please immediately  
contact the sender if you have received this message in error.

---

<div class="post-metadata">

**Author:** ![jdunn](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/jdunn/32/1800_2.png) [@jdunn](https://discourse.chef.io/u/jdunn)\
**Post date:** [July 16, 2014, 4:05am UTC](https://discourse.chef.io/t/chef-12-brainstorming/5524/2 "2014-07-16T04:05:36Z")

</div>

On Tue, Jul 15, 2014 at 10:47 PM, Tim Smith [tsmith@llnw.com](mailto:tsmith@llnw.com) wrote:

> I’m curious if there’s any brainstorming going on between the community and  
> Chef Inc. about functionality for inclusion in the next major release of  
> Chef (12). I see there’s a small wiki doc that hasn’t been updated in a  
> year at [https://wiki.opscode.com/display/chef/Chef+12+Release+Checklist](https://wiki.opscode.com/display/chef/Chef+12+Release+Checklist) I  
> think a lot of people could come up with some great minor/major changes that  
> would really improve Chef for the next release. Some of the changes I had  
> in mind seem too small for the full blown RFC process, but perhaps that’s  
> where they should still be.

There's been some internal thinking at ChefInc. about breaking (and  
other) changes on the next release, but nothing's really solidified.  
We should get the community involved though to restart the process  
again.

What do you think is the right format to have this discussion --  
after-party of the dev meeting in #chef-hacking? Same place but  
another time?

- Julian

--  
[Julian C. Dunn [jdunn@aquezada.com](mailto:jdunn@aquezada.com) \* Sorry, I'm ]  
[WWW: [Julian Dunn's Blog - Commentary on media, technology, and everything in between.](http://www.aquezada.com/staff/julian) \* only Web 1.0 ]  
[gopher://sdf.org/1/users/keymaker/ \* compliant!]  
[PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9]

---

<div class="post-metadata">

**Author:** ![Serdar\_Sutay1](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@Serdar\_Sutay1](https://discourse.chef.io/u/Serdar_Sutay1)\
**Post date:** [July 16, 2014, 4:38pm UTC](https://discourse.chef.io/t/chef-12-brainstorming/5524/3 "2014-07-16T16:38:02Z")

</div>

I'm going to share the internal Chef 12 thinking Julian is mentioning with  
a doc on chef-rfc repo in the next couple of days. We can get this as a  
starting point and iterate on the doc over a PR and chat more about it in  
the next Chef Developers' Meeting.

Does this sound good to kick off this discussion?

-- Serdar

On Tue, Jul 15, 2014 at 9:05 PM, Julian C. Dunn [jdunn@aquezada.com](mailto:jdunn@aquezada.com) wrote:

> On Tue, Jul 15, 2014 at 10:47 PM, Tim Smith [tsmith@llnw.com](mailto:tsmith@llnw.com) wrote:
> 
> > I’m curious if there’s any brainstorming going on between the community  
> > and  
> > Chef Inc. about functionality for inclusion in the next major release of  
> > Chef (12). I see there’s a small wiki doc that hasn’t been updated in a  
> > year at [https://wiki.opscode.com/display/chef/Chef+12+Release+Checklist](https://wiki.opscode.com/display/chef/Chef+12+Release+Checklist)  
> > I  
> > think a lot of people could come up with some great minor/major changes  
> > that  
> > would really improve Chef for the next release. Some of the changes I  
> > had  
> > in mind seem too small for the full blown RFC process, but perhaps that’s  
> > where they should still be.
> 
> There's been some internal thinking at ChefInc. about breaking (and  
> other) changes on the next release, but nothing's really solidified.  
> We should get the community involved though to restart the process  
> again.
> 
> What do you think is the right format to have this discussion --  
> after-party of the dev meeting in #chef-hacking? Same place but  
> another time?
> 
> - Julian
> 
> --  
> [Julian C. Dunn [jdunn@aquezada.com](mailto:jdunn@aquezada.com) \* Sorry, I'm ]  
> [WWW: [Julian Dunn's Blog - Commentary on media, technology, and everything in between.](http://www.aquezada.com/staff/julian) \* only Web 1.0 ]  
> [gopher://sdf.org/1/users/keymaker/ \* compliant!]  
> [PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9]

---

<div class="post-metadata">

**Author:** ![Tim\_Smith1](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/tim_smith1/32/283_2.png) [@Tim\_Smith1](https://discourse.chef.io/u/Tim_Smith1)\
**Post date:** [July 16, 2014, 5:05pm UTC](https://discourse.chef.io/t/chef-12-brainstorming/5524/4 "2014-07-16T17:05:45Z")

</div>

Sounds great

On Jul 16, 2014, at 9:38 AM, Serdar Sutay [serdar@getchef.com](mailto:serdar@getchef.com) wrote:

> I'm going to share the internal Chef 12 thinking Julian is mentioning with a doc on chef-rfc repo in the next couple of days. We can get this as a starting point and iterate on the doc over a PR and chat more about it in the next Chef Developers' Meeting.
> 
> Does this sound good to kick off this discussion?
> 
> -- Serdar
> 
> On Tue, Jul 15, 2014 at 9:05 PM, Julian C. Dunn [jdunn@aquezada.com](mailto:jdunn@aquezada.com) wrote:  
> On Tue, Jul 15, 2014 at 10:47 PM, Tim Smith [tsmith@llnw.com](mailto:tsmith@llnw.com) wrote:
> 
> > I’m curious if there’s any brainstorming going on between the community and  
> > Chef Inc. about functionality for inclusion in the next major release of  
> > Chef (12). I see there’s a small wiki doc that hasn’t been updated in a  
> > year at [https://wiki.opscode.com/display/chef/Chef+12+Release+Checklist](https://wiki.opscode.com/display/chef/Chef+12+Release+Checklist) I  
> > think a lot of people could come up with some great minor/major changes that  
> > would really improve Chef for the next release. Some of the changes I had  
> > in mind seem too small for the full blown RFC process, but perhaps that’s  
> > where they should still be.
> 
> There's been some internal thinking at ChefInc. about breaking (and  
> other) changes on the next release, but nothing's really solidified.  
> We should get the community involved though to restart the process  
> again.
> 
> What do you think is the right format to have this discussion --  
> after-party of the dev meeting in #chef-hacking? Same place but  
> another time?
> 
> - Julian
> 
> --  
> [Julian C. Dunn [jdunn@aquezada.com](mailto:jdunn@aquezada.com) \* Sorry, I'm ]  
> [WWW: [Julian Dunn's Blog - Commentary on media, technology, and everything in between.](http://www.aquezada.com/staff/julian) \* only Web 1.0 ]  
> [gopher://sdf.org/1/users/keymaker/ \* compliant!]  
> [PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9]

--  
The information in this message may be confidential. It is intended solely  
for  
the addressee(s). If you are not the intended recipient, any disclosure,  
copying or distribution of the message, or any action or omission taken by  
you  
in reliance on it, is prohibited and may be unlawful. Please immediately  
contact the sender if you have received this message in error.

---

<div class="post-metadata">

**Author:** ![Serdar\_Sutay1](https://avatars.discourse-cdn.com/v4/letter/s/c4cdca/32.png) [@Serdar\_Sutay1](https://discourse.chef.io/u/Serdar_Sutay1)\
**Post date:** [July 17, 2014, 4:29pm UTC](https://discourse.chef.io/t/chef-12-brainstorming/5524/5 "2014-07-17T16:29:24Z")

</div>

And here is the RFC:

> <https://github.com/chef-boneyard/chef-rfc/pull/22>
>
> This RFC codifies our policy as a community for the supported versions of Chef a…nd supported versions of Ruby for Chef. 
> 
> In the light of this policy it also contains a scoping exercise for Chef 12.

Please check it out and leave comments for things that doesn't make sense  
or the changes you'd like to see.

If you'd like Chef 12 to include a feature you can leave a comment with the  
mini template in this RFC or feel free to submit a pr to the chef-12 branch  
of the rfc repo 🙂

-- Serdar

On Wed, Jul 16, 2014 at 10:05 AM, Tim Smith [tsmith@llnw.com](mailto:tsmith@llnw.com) wrote:

> Sounds great
> 
> On Jul 16, 2014, at 9:38 AM, Serdar Sutay [serdar@getchef.com](mailto:serdar@getchef.com) wrote:
> 
> I'm going to share the internal Chef 12 thinking Julian is mentioning with  
> a doc on chef-rfc repo in the next couple of days. We can get this as a  
> starting point and iterate on the doc over a PR and chat more about it in  
> the next Chef Developers' Meeting.
> 
> Does this sound good to kick off this discussion?
> 
> -- Serdar
> 
> On Tue, Jul 15, 2014 at 9:05 PM, Julian C. Dunn [jdunn@aquezada.com](mailto:jdunn@aquezada.com)  
> wrote:
> 
> > On Tue, Jul 15, 2014 at 10:47 PM, Tim Smith [tsmith@llnw.com](mailto:tsmith@llnw.com) wrote:
> > 
> > > I’m curious if there’s any brainstorming going on between the community  
> > > and  
> > > Chef Inc. about functionality for inclusion in the next major release of  
> > > Chef (12). I see there’s a small wiki doc that hasn’t been updated in a  
> > > year at [https://wiki.opscode.com/display/chef/Chef+12+Release+Checklist](https://wiki.opscode.com/display/chef/Chef+12+Release+Checklist)  
> > > I  
> > > think a lot of people could come up with some great minor/major changes  
> > > that  
> > > would really improve Chef for the next release. Some of the changes I  
> > > had  
> > > in mind seem too small for the full blown RFC process, but perhaps  
> > > that’s  
> > > where they should still be.
> > 
> > There's been some internal thinking at ChefInc. about breaking (and  
> > other) changes on the next release, but nothing's really solidified.  
> > We should get the community involved though to restart the process  
> > again.
> > 
> > What do you think is the right format to have this discussion --  
> > after-party of the dev meeting in #chef-hacking? Same place but  
> > another time?
> > 
> > - Julian
> > 
> > --  
> > [Julian C. Dunn [jdunn@aquezada.com](mailto:jdunn@aquezada.com) \* Sorry, I'm ]  
> > [WWW: [Julian Dunn's Blog - Commentary on media, technology, and everything in between.](http://www.aquezada.com/staff/julian) \* only Web 1.0 ]  
> > [gopher://sdf.org/1/users/keymaker/ \* compliant!]  
> > [PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9]
> 
> The information in this message may be confidential. It is intended  
> solely for  
> the addressee(s). If you are not the intended recipient, any disclosure,  
> copying or distribution of the message, or any action or omission taken by  
> you  
> in reliance on it, is prohibited and may be unlawful. Please immediately  
> contact the sender if you have received this message in error.

---

<div class="post-metadata">

**Author:** ![Kenneth\_Barry](https://avatars.discourse-cdn.com/v4/letter/k/3da27b/32.png) [@Kenneth\_Barry](https://discourse.chef.io/u/Kenneth_Barry)\
**Post date:** [July 17, 2014, 4:37pm UTC](https://discourse.chef.io/t/chef-12-brainstorming/5524/6 "2014-07-17T16:37:03Z")

</div>

I’m going to suggest IRC, not because I think its the best idea, but  
because if there was something not directly “Chef” i’d love to have, it  
would be a much more active #chef IRC channel.