17:01:41 <sarob> #startmeeting training-guides
17:01:41 <openstack> Meeting started Mon Dec  1 17:01:41 2014 UTC and is due to finish in 60 minutes.  The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:42 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:01:45 <openstack> The meeting name has been set to 'training_guides'
17:01:54 <sarob> Hello
17:01:59 <rluethi> hi
17:02:01 <MeganR> Hello
17:02:06 <dbite> hi
17:02:45 <sarob> #bp for kilo
17:02:52 <sarob> Duh
17:03:05 <sarob> #topic bp for kilo
17:03:08 <dbite> I thought we were decided on specs ;)
17:03:53 <rluethi> my spec/bp is up. I don't see it happening for Kilo.
17:04:05 <dbite> I have a bunch of specs coming up
17:04:14 <sarob> Cool
17:04:53 <sarob> Whatca think of the overall plan I put out there
17:05:18 <rluethi> sarob: hey, what's with the agenda?
17:05:39 <sarob> I forgot to update it
17:05:46 * sarob blush
17:06:17 <rluethi> sarob: re: overall plan, I commented on the parts that I know about (on the ML).
17:06:56 <sarob> Rluethi right
17:07:18 <sarob> Rluethi haven't had a chance to respond yet
17:07:27 <dbite> sarob: I am still not sure if architects in cloud computing code for TDD based model
17:07:38 <dbite> but the overall plan seems good
17:07:44 <sarob> Dbite okay cool
17:08:09 <dbite> or am I right about the architects?
17:08:14 <matjazp> hi guys
17:08:15 <dbite> *right or wrong
17:08:19 <dbite> matjazp: hellp
17:08:21 <dbite> *hello
17:08:22 <sarob> I want to communicate the kilo plan
17:08:40 <matjazp> dbite: you're feeling better?
17:08:45 <sarob> So I'm good with being wrong
17:08:58 <dbite> matjazp: nope, but could not get sleep
17:09:01 <sarob> As long as someone else corrects me
17:09:27 <sarob> And can put out there what we should be doing
17:09:45 <sarob> Matjazp hey
17:10:46 <dbite> sarob: I was thinking in lines of openstack architect book
17:11:01 <dbite> as point of reference
17:11:07 <sarob> Dbite right
17:12:53 <sarob> So rluethi has a spec
17:13:29 <rluethi> as noted during last week's meeting.
17:13:52 <sarob> Dbite on arch guide I'm good with you coming up with one
17:14:01 <sarob> Diff than what I put out
17:14:25 <dbite> sarob: I am more preoccupied with koans and labs section also the release is a bit time consuming
17:15:03 <sarob> Okay, then we should have a few spec to describe that work with this cycle
17:15:45 <sarob> Rluethi I repeated your spec in the ml so the plan would make sense
17:16:05 <rluethi> sarob: most lab work does not need a spec. it's only updating to keep up with Juno/Kilo.
17:16:53 <sarob> Well maybe we should start writing specs or bugs for work tbd
17:17:23 <sarob> I'd like to be able to show to your mgr or mine
17:17:41 <sarob> What our work plan is for the next six months
17:18:09 <sarob> Even better what new people could work with you on
17:18:10 <matjazp> sarob: hmm.. for managers it would be better to put an executive summary on the wiki
17:18:15 <rluethi> sarob: I think things will get clearer as we get feedback from the pilot.
17:18:43 <sarob> Pilot?
17:19:01 <sarob> Rluethi meaning training in sfbay user group?
17:19:02 <rluethi> sarob: the thing in the user group.
17:19:16 <sarob> Rluethi true
17:19:28 <rluethi> sarob: we are eagerly awaiting your first set of slides.
17:19:43 <rluethi> sarob: also, feedback on training cluster.
17:20:00 <sarob> Yup
17:20:21 <sarob> This thurs is coming up fast
17:20:52 <dbite> sarob: we need to clean up the XML content before
17:20:52 <matjazp> I'll have a feedback of the training cluster by the end of this week
17:21:02 <sarob> Matjazp cool
17:21:04 <rluethi> matjazp: excellent.
17:21:16 <matjazp> rluethi: I hope everyting works ;)
17:21:28 <rluethi> matjazp, sarob: if you downloaded the zip file before the last fix, make sure to get the new version.
17:21:45 <sarob> Rluethi roger that
17:21:56 <sarob> Roger roger
17:22:09 <rluethi> if you built the Windows batch scripts locally, they're fine. but the one built on the build host were broken.
17:22:25 <matjazp> rluethi: np, I'll just delete all generated files and/or clone again from the start
17:23:26 <sarob> So I'm going to push these specs today to join rluethi spec
17:23:49 <sarob> Like dbite is saying they are not perfect
17:24:07 <sarob> But a good start to what needs to get done
17:24:36 <sarob> I'd like to whittle them down to what we can get done over this cycle
17:24:42 <sarob> Over this week
17:25:12 <sarob> So next meet we can discuss the bp and milestone assignment
17:26:02 <sarob> I'd like see on gerrit new specs and discussion as much as possible
17:26:24 <sarob> I like being told I'm wrong
17:26:39 <sarob> As long as you have an alternate solution
17:27:08 <sarob> I am interested in getting more people involved
17:27:27 <sarob> Having a plan will help a lot
17:27:41 <sarob> On launchpad
17:28:05 <sarob> Wiki is good too, but launchpad is our source of truth
17:28:25 <sarob> Sound good ?
17:28:51 <matjazp> ok
17:29:04 <rluethi> I'll wait and see.
17:30:18 <sarob> Anyone else?
17:30:40 <sarob> Dbite sayali shilla?
17:31:07 <sarob> Reed or loic are you lurking?
17:31:14 <dbite> yes
17:31:15 <dbite> sounds good
17:31:17 <MeganR> I am good with having a plan, and liked the one on the ML
17:31:32 <sarob> Meganr dbite Thx
17:31:59 <sarob> Let's move on then
17:32:20 <sarob> #topic dbite big patch
17:32:43 <dbite> sarob: Its cleaned and its out
17:33:03 <dbite> I will be writing a spec in manuals and get training-guides-install-guides shipped for the newer slides
17:33:12 <dbite> just wanted to report
17:33:17 <sarob> Cool
17:34:53 <sarob> #topic any other business
17:35:15 <dbite> Specs for Labs Section as per https://etherpad.openstack.org/p/training-guides-kilo-summit - Roger (rluethi), Pranav (dguitarbite), Sayali (sayali)     Icehouse release for Training guides - Roger(rluethi), Pranav (dguitatarbite)     Delete/Remove XML content - Pranav (dguitarbite)     Pilot: experience/feedback/slides
17:35:46 <rluethi> aka "today's agenda"
17:35:52 <ShillaSaebi> hi all, sorry im late
17:36:04 <dbite> well we discussed some parts of it already
17:36:09 <sarob> Shillasaebi np
17:36:18 <dbite> but we need to work on the important points there
17:36:23 <dbite> like the release for Icehouse
17:37:30 <matjazp> dbite: yes, official release (branch stable/icehouse) of the labs would be great
17:37:32 <sarob> Branching first
17:37:38 <sarob> ?
17:37:47 <dbite> sarob: branching is part of the release
17:38:00 <rluethi> sayali, dbite and I worked over the weekend to get the scripts ready for branching. they are done.
17:38:01 <dbite> we also address your user group training by keeping the XML content in the icehouse branch
17:38:05 <sarob> Well it is the release
17:38:11 <dbite> while we can delete and clean up the XML to make way for the slides
17:38:34 <dbite> are there any blockers from anyone? any concerns or issues that we might have overlooked
17:38:56 <sarob> None from me
17:39:04 <matjazp> go for it
17:39:16 <dbite> kool sounds good :)
17:39:38 <dbite> and sarob we where working on a list of potential specs which is at the end of the etherpad here
17:39:51 <dbite> #link https://etherpad.openstack.org/p/training-guides-kilo-summit
17:40:09 <sarob> I see them down there now
17:40:28 <sarob> Has that been there since the summit?
17:40:38 <sarob> Totally didn't see it
17:40:48 <dbite> sarob: I think that was filtered as per our discussions from the summit
17:40:56 <sarob> Okay
17:41:30 <rluethi> note that those are proposed BPs. they are _not_ what is going to get done for Kilo.
17:42:02 <sarob> Rluethi understood
17:42:04 <dbite> sarob: the major focus will be on the slides as they are most important for this release
17:42:10 <sarob> Agreed
17:42:25 <dbite> and I will maintain the installation sections and roger with labs
17:42:37 <sarob> Let's get the bp published asap
17:42:40 <dbite> so that we have something usable in a few monhts
17:42:48 <dbite> sarob: yep, kool!
17:42:57 <sarob> Specs next
17:43:30 <sarob> We can figure out how much work we can get done
17:43:36 <sarob> At our next meet
17:43:58 <dbite> we might have the Icehouse release out till then if everything goes as planned
17:44:11 <sarob> After the bp and spec have gotten some feedback
17:45:11 <sarob> I think getting on a release schedule can be a spec bp as well
17:45:53 <rluethi> sarob: hey, are we looking for excuses to write up spec bps?
17:46:05 <rluethi> I know I'm not.
17:46:31 <sarob> Rluethi not really, but we should describe work plans in launchpad
17:47:07 <sarob> Rluethi getting on a release schedule is non trivial work
17:47:31 <sarob> If I had an intern for three weeks
17:47:44 <sarob> What would I have them work on?
17:47:50 <rluethi> last time I checked the docs team had 1 or 2 specs.
17:48:03 <rluethi> we don't need specs for obvious stuff.
17:48:26 <dbite> I agree with roger, its more like a milestone and a branch
17:48:37 <sarob> We need bugs or specs to describe non trivial work
17:48:52 <rluethi> agreed.
17:49:01 <sarob> If branching is trivial already then cool
17:49:31 <dbite> sarob: I am not able to see how we track the spec in other projects which are used for release management
17:49:37 <dbite> I can count atleast 2-3 of them
17:49:46 <dbite> and also if other projects follow that method
17:50:00 <sarob> Dbite not sure I understand?
17:50:15 <dbite> the release is done more from the other infra repositories
17:50:25 <dbite> and done by the infra guys as far as I remember
17:50:50 <sarob> Ah okay
17:51:21 <sarob> I think we branch when we are ready
17:51:46 <sarob> But coordinate in the future with docs and the rest
17:51:48 <dbite> sarob: I dont think its that organic at this point of time in OpenStack
17:52:03 <sarob> Dbite ?
17:52:13 <sarob> Organic is a fancy word
17:52:14 <dbite> I am not sure if we are even allowed to create a branch like that
17:52:23 <sarob> Dbite ah
17:52:26 <dbite> I am sleepy :D
17:53:21 <dbite> sarob: andreas was very helpful and explain how to release
17:53:40 <sarob> Dbite I'd like to coordinate with docs
17:53:46 <dbite> its not that simple, we need to ask the infra guys for that
17:53:49 <dbite> sarob: yes
17:54:18 <sarob> Dbite I'm used to doing it manually so
17:54:33 <rluethi> sarob: coordinate what, exactly? we are behind more than one release.
17:54:34 <dbite> ahh, may be I got something wrong then
17:54:49 <dbite> rluethi: are we not just rolling release?
17:54:52 <sarob> Dbite let's ask andreas how he and the rest of the docs team
17:55:03 <sarob> Wants to proceed
17:55:05 <ShillaSaebi> yeah lets get some input from them
17:55:21 <rluethi> I think that's pretty much what dbite already did.
17:55:47 <matjazp> Docs team has it documented... maybe we should just adopt this.. #link https://wiki.openstack.org/wiki/Documentation/Release
17:56:21 <rluethi> matjazp: +1
17:56:39 <ShillaSaebi> yeah that makes sense
17:56:50 <dbite> matjazp: +1
17:57:01 <matjazp> do we need a vote?
17:57:27 <dbite> matjazp: I am not sure we have that liberty to decide how to release
17:57:40 <rluethi> matjazp: vote on what?
17:57:40 <sarob> So we want to branch just a subdirectory?
17:57:45 <matjazp> why not? we have a separate repo
17:57:59 <sarob> I think the whole repo needs to be ready
17:58:41 <sarob> We are out of time
17:58:59 <rluethi> well done.
17:59:18 <rluethi> see you guys next week. or on the ML, or the docs channel.
17:59:23 <sarob> Let's continue on docs channel
17:59:27 <matjazp> bye all
17:59:38 <sarob> #endmeeting