[chef] Re: Chef 12 brainstorming

[Tim Smith < >]

Sounds great

On Jul 16, 2014, at 9:38 AM, Serdar Sutay < "> > 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 < " target="_blank"> > wrote:

On Tue, Jul 15, 2014 at 10:47 PM, Tim Smith < "> > 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  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 < "> >          * Sorry, I'm    ]
[ WWW: 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.