20:01:33 #startmeeting milk 20:01:34 Meeting started Mon Feb 24 20:01:33 2014 UTC and is due to finish in 60 minutes. The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:01:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:01:37 The meeting name has been set to 'milk' 20:02:06 I'm here. 20:02:07 Finally. 20:02:24 :) 20:02:34 im pinging guillaume 20:04:15 oh way, lets proceed 20:04:29 #topic bootcamp 20:05:26 #link https://docs.google.com/a/yahoo-inc.com/document/d/1QiZ_PJTIFwKOmHPYhtez0TTEXHUb1r21OV0-PoNN45U/edit?usp=sharing 20:06:10 the bootcamp structure is laid out at the bottom of the gdoc 20:06:23 have you a look? 20:06:38 Yes, Is that doc a cut and paste from something else? 20:08:15 nope 20:08:24 all created last week 20:08:35 K, so a few questions... 20:09:12 question away 20:10:31 There's discussion about difficulty level which sounds very general. Are we talking about a certification system? I guess I don't understand the relevance. 20:11:07 im running an open source training program 20:11:30 the training guide we are working on right now 20:11:51 im creating a condensed version of the guide as a bootcamp 20:12:05 to get etc devs up to speed 20:13:05 the section Appendix: How To Participate Bootcamp 20:13:44 we are going to run through the first revision of that tomorrow 20:14:20 does that make more sense? 20:14:30 Ok got it. So as far as this doc is concerned we're focusing just on "how to participate"? 20:14:45 for tomorrow 20:14:47 just the last section 20:14:51 yup 20:15:25 the developer training as a whole is meant to take two weeks 20:15:36 we doing the condensed version 20:15:39 6 hours 20:16:17 Ok good, makes sense. I was concerned that we'd be burning time going over how to program in Python, TDD, or Agile etc. 20:16:26 I'm looking forward to it. 20:17:16 nope, not enough time 20:17:28 yeah 20:17:38 i working out the materials today 20:18:25 ill be patching them to #link http://docs.openstack.org/training-guides/ 20:19:16 So I'm thinking this is 100% the focus for tomorrow, so I won't worry about discussing framework er... work. 20:19:23 right 20:19:50 my intent is to get the team up to speed on how to contribute 20:20:19 then our framework contributions will be less difficult 20:20:47 Yep, great. Much needed. 20:21:05 Did Erik get you a head count yet? Any idea how many we have? 20:21:30 right now its you, me, and guillaume 20:21:43 which is fine as a first run at this 20:22:03 next time you guys can help teach the next batch 20:22:56 Sure, and makes sense if we're reviewing. 20:23:53 So how are we doing it, online, at ETC, irc, phone ? 20:23:59 at ETC 20:24:18 k, starting 9am? 20:25:49 #link https://groups.google.com/a/etcusc.org/forum/#!topic/milk-dev/fVKUlXJjWCk 20:26:06 i planned on 10am 20:26:18 im flying in tomorrow morning 20:26:51 ok, all good then. 20:27:20 lets change topics 20:27:30 #topic milk api 20:28:07 Ok, so I've done some work with this, more or less in a vacuum. 20:28:21 #link https://wiki.openstack.org/wiki/Milk#design 20:28:37 hit me with what you have 20:30:03 I've been putting together a Apiary 'blueprint'. 20:30:37 this one #link http://docs.milk.apiary.io/ 20:31:47 i agree with the approach 20:32:02 define verbs, methods 20:32:19 prototype in apiary 20:32:19 In it i've put a number of components there from our work on C4 that I think generalize well. 20:32:20 yes 20:32:24 that one 20:32:30 but I haven't published there yet 20:32:54 ah okay 20:32:58 I'd like to integrate with Guillaume's work 20:33:14 can you push your text to the milk wiki page? 20:33:49 we should be communicating through the wiki, mailing list 20:33:50 And I was waiting to understand how to link it properly with OpenStack submission process . 20:33:51 yes 20:34:10 Which I will learn how to do tomorrow. ;) 20:34:12 that way we can get the rest of the group involvved 20:34:15 right 20:34:29 dump what you are working on into the wiki 20:34:47 Yep, will do. 20:36:00 I created a starting spot for you in the wiki design section 20:36:16 see it? 20:36:23 Ah, yes good. 20:36:42 the wiki syntax is a bit primitive but works 20:37:31 K, I'll manage I'm more a markdown person anyway. 20:37:36 we just need to define some verbs, methods 20:37:45 write up what you have 20:37:58 once we decide on a few 20:38:07 Should I put the architecture notes from my email there too? 20:38:18 we can get some thing pushed to the repo pretty quick 20:38:25 yes 20:38:27 def 20:38:44 we can worry about cleaning up the structure 20:38:47 after the fact 20:39:06 better to get stuff on paper 20:39:17 ready, shoot, aim 20:40:54 I never got any comments on that one way or another. 20:40:54 launchpad is strange. I used the wrong email address, changed it, but now it still wants to use the one I started with. 20:40:54 sure, sounds good. 20:41:29 it creates an openid account 20:41:58 https://launchpad.net/~sarob 20:42:01 is mine 20:42:08 I'll try to dump as much as I can today, and over the next few days. 20:42:26 excellent 20:42:40 we could be done with the milk project in a few days 20:42:52 its pretty simple concept 20:43:04 its the collaboration that is the important bit 20:43:21 yes, always hard that. 20:43:31 well we two 20:43:49 Ok sorted launch pad, odd UX, I'm easily confused. 20:44:04 no prob 20:44:19 thats what tomorrow is for 20:44:42 to explain the contribution tools and workflow 20:45:14 companies have failed because they couldnt figure it out 20:45:37 its part of the reason openstack community work 20:46:15 see you on the mailing list and wiki before tomorrow? 20:46:28 ill be posting the link to the materials 20:47:02 Yep, I'll do my best. Bit of a tight schedule today to open up tomorrow, but I'll try to get out what I can. 20:47:11 understood 20:47:18 thanks for joining 20:47:21 signing off 20:47:27 k later 20:47:30 #endmeeting