15:31:10 <markvan> #startmeeting openstack-chef
15:31:11 <openstack> Meeting started Fri Oct 10 15:31:10 2014 UTC and is due to finish in 60 minutes.  The chair is markvan. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:31:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:31:14 <openstack> The meeting name has been set to 'openstack_chef'
15:31:36 <markvan> os-chef-bot: task list
15:31:36 <os-chef-bot> #1 - markvan look up git change log
15:31:36 <os-chef-bot> #2 - j^2 look up how to standardize email maintaining like openstack
15:32:03 <markvan> Howdy all, meeting time.
15:32:17 <markvan> @core meeting time!
15:32:17 <os-chef-bot> @core meeting time!
15:32:42 <j^2> Hey
15:35:14 <markvan> #topic Review action list
15:35:55 <markvan> for my action on Changelog, I did find that that other projects have this file generated based upon the git logs
15:36:24 <j^2> Oh sweet
15:36:26 <markvan> It's not a bad format, but lacks the version break down we currently have.
15:37:29 <markvan> So, i'll continue to look into this a bit to understand how the flow works and how it avoids changelog rebase collisions that I have been hitting all the time.
15:38:34 <markvan> Looks like the solution will be to remove the manual Changelog files from the cookbooks, and instead have them generated at some point.
15:38:45 <markvan> j^2: and info on email action?
15:38:49 <markvan> any
15:40:20 <j^2> Yeah it seems that we should probably just remove email from metadata.rv
15:40:40 <j^2> No one uses it and few if any are checked
15:41:59 <markvan> #link https://docs.getchef.com/essentials_cookbook_metadata.html
15:42:16 <markvan> Looking at the link, I don't see which fields are required or optional.
15:43:26 <markvan> the base openstack projexts like nova, use  author-email = openstack-dev@lists.openstack.org
15:43:31 <markvan> https://github.com/openstack/nova/blob/master/setup.cfg#L8
15:43:46 <markvan> So, maybe using our list is not that bad of an idea here.
15:45:13 <j^2> Eeehhh
15:45:26 <j^2> That could be a lot of noise
15:45:47 <j^2> But at the same time we would get eyes on issuse
15:46:32 <markvan> yup, having it come thru does not sound so bad....might miss things otherwise
15:46:37 <j^2> But either we stdize or remove. One or the other imo
15:47:44 <markvan> yup, I vote for the list approach.  Maybe put up a patch for Common with that, and we'll get more feedback that way.
15:48:09 <j^2> Sounds good. I can take that action item
15:48:45 <j^2> Common and I have an close relationship now a days
15:49:01 <markvan> ok
15:49:24 <markvan> #topic General Discussion
15:49:53 <markvan> Opening this up if anybody has something on their mind...
15:50:06 <j^2> Leaps and bounds with the testing framework
15:50:23 <j^2> We talked about it before the meeting though
15:51:19 <markvan> Yup, maybe add the link to it here again
15:52:03 <j^2> #link http://GitHub.com/jjasghar/singlestack
15:53:10 <j^2> I changed the name of the repo too because its not singlestack anymore
15:53:28 <j^2> But it'll take you to the correct place
15:54:32 <markvan> I will have to find more time to dig thru this again...
15:55:14 <j^2> :) just a little longer and we can have real integration tests.
15:56:11 <j^2> And then with that we can start building swift clusters and all so we can actually see this stuff work.
15:56:24 <j^2> I'm really excited about this
15:57:18 <markvan> For feedback on that, where would you like that?  github issues?     Just looking now, I see a few minor comments I would like to make (can't resist a review opp)
15:58:11 <j^2> Yeah GitHub issues probably to start. After its GA I was going to give it to stackforge
15:58:33 <j^2> And ask to deprecate chef-repo
15:59:04 <markvan> ok, I'll create a single issue with a bunch of minor cleanup comments so you can easily track them.
15:59:33 <j^2> Awesome :) and if you can I'd love for you to play with it
15:59:33 <markvan> And yes either replace or merge with chef-repo as they are covering much of the same ground.
16:00:04 <markvan> yeah, I have to set aside the internal setup I always use and switch to this, hopefully next week.
16:00:25 <j^2> Sweet
16:02:02 <markvan> Any other topics for tday, anyone?
16:04:33 <j^2> Not here :)
16:04:53 <markvan> #endmeeting