[chef-dev] Re: ideas for chef-hackday at Chefconf, Tuesday afternoon, May 15

[Jim Hopp < >]

+1. This is a hot topic for us right now.

Another topic to consider is the each-cookbook-in-its-own-repo thing:
we're trying to figure out a good workflow for that.

-Jim

On 4/24/12 1:17 PM, "Bryan Berry" 
<
 >
 wrote:

>Yo Chefs!
>
>Somehow I have been drafted into organizing a Chef hackday on the
>Tuesday afternoon ahead of Chefconf. For this Hackday to be somewhat
>productive, esp. in such a short window of time, it needs to be very
>focused. My initial thoughts are to focus on testing as that is my own
>current focus. What would you Chef-devs like to see such an event
>focus on?
>
>My idea so far is to focus on testing the application cookbook in
>every possible configuration using various methodologies such as
>vagrant, toft, chefspec, etc. Even better test it on different
>platforms. As Jay Feldblum has suggested in the past, each cookbook
>needs to be a self-contained project, including with its own set of
>battle-hardened integration tests.  My only concern about focusing on
>the application cookbook is that it is currently undergoing a lot of
>change.
>
>I would love to hear from you guys what you would like to see such an
>event focus on. Perhaps testing is boring and we should have an
>installfest putting omnibus through its paces!
>
>I have created this planning document here:
>https://github.com/bryanwb/chef-hackday/blob/master/Planning.md
>
>yours in cookery,
>
>BryanWB