17:00:18 <sarob> #startmeeting training-guides
17:00:19 <openstack> Meeting started Mon Dec 15 17:00:18 2014 UTC and is due to finish in 60 minutes.  The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:22 <openstack> The meeting name has been set to 'training_guides'
17:00:55 <matjazp> hey
17:01:00 <timfreund> Hello
17:01:04 <dguitarbite> hello
17:01:04 <sayali> hello
17:01:10 <sarob> hello all
17:01:10 <MeganR> Hi
17:01:45 <sarob> agenda from #link https://wiki.openstack.org/wiki/Meetings/training-guides#Agenda_15st_December
17:02:03 <sarob> #topic status on branch
17:02:41 <dguitarbite> work in progress
17:02:48 <sarob> patch can be found here #link https://review.openstack.org/#/c/141369/
17:02:53 <dguitarbite> waiting for feedback from docs team
17:03:12 <sarob> spec on branch can be found there
17:04:03 <sarob> I added a question we can answer here
17:04:05 <sarob> discuss maybe
17:04:23 <sarob> launchpad has a juno series
17:04:41 <sarob> we plan to ignore that for this branch
17:06:27 <sarob> when i release, launchpad tarballs the repo, right?
17:07:14 <sarob> dguitarbite?
17:07:51 <dguitarbite> sarob: I am not sure if I follow you
17:08:05 <sarob> in launchpad
17:08:15 <sarob> we have series and milestones
17:08:23 <sarob> we assign bp to milestones
17:08:31 <sarob> milestones are set to series
17:08:41 <sarob> as part of the release
17:08:44 <sarob> process
17:08:55 <matjazp> are you saying that launchpad will create tarballs with icehouse version and pack it as juno?
17:09:07 <sarob> no,
17:09:11 <dguitarbite> sarob: we do not have a proper release cycle yet
17:09:22 <dguitarbite> tarballs will be created by github and git.openstack.org
17:09:22 <sarob> dguitarbite: i get that
17:09:29 <dguitarbite> need not worry about them
17:09:38 <dguitarbite> for now its more important to branch for archival purposes
17:09:45 <sarob> dguitarbite: understood
17:09:47 <dguitarbite> and make the content easily available for others
17:10:01 <dguitarbite> so that RST work can proceede
17:11:27 <sarob> dguitarbite: im just thinking throught the launchpad part
17:11:37 <sarob> dguitarbite: the rest makes sense
17:12:25 <dguitarbite> sarob: I am a bit ignorant of launchpad part
17:12:44 <dguitarbite> IMHO, I think that its that relevant as of now
17:13:11 <matjazp> sarob: I still don't get it where is the problem? Can you elaborate?
17:13:17 <rluethi> dguitarbite: you mean not relevant!?
17:13:18 <sarob> dguitarbite: its the last detail
17:14:18 <sarob> look to #link https://launchpad.net/openstack-manuals
17:14:54 <sarob> id like to follow #link https://launchpad.net/openstack-manuals/kilo
17:15:27 <sarob> once you set it as released, its listed as release in launchpad
17:15:55 <dguitarbite> launchpad is under our control, its easier to modify the release tracking and specifications there
17:15:56 <sarob> i want to understand what the docs program wants to do a part of branching
17:16:24 <sarob> should we be concluding the series within launchpad as well
17:16:32 <dguitarbite> I am not sure if we could get Icehouse in there
17:16:34 <sarob> by marking the series as released
17:16:54 <sarob> dguitarbite: we never listed icehouse so i guess not
17:16:56 <dguitarbite> the release is Icehouse (content wise) where as the branch name may be Juno
17:17:04 <dguitarbite> sarob: I am not sure if Icehouse can be listed here
17:17:13 <sarob> dguitarbite: perhaps not
17:17:23 <dguitarbite> it may be because we got separate repository when we where in Juno cucle
17:17:25 <dguitarbite> *cycle
17:17:32 <dguitarbite> so icehouse may not be possible there
17:18:16 <sarob> dguitarbite: id like to understand what the rest of the docs cores think we should be doing for branching with launchpad
17:18:30 <sarob> as the whole docs team
17:18:47 <dguitarbite> sarob: I do not understand what branching with launchpad exactly implies
17:19:05 <sarob> dguitarbite: well i guess im not sure either
17:19:38 <dguitarbite> sarob: as I told you, I think we can worry about the launchpad tracking part after the spec is merged and the branching in git is carried out
17:19:42 <sarob> dguitarbite: so we need to decide the launchpad whats and hows for releases with annegentle and others
17:19:56 <sarob> dguitarbite: sure that sounds right
17:20:20 <dguitarbite> sarob: if you look at the link register a series
17:20:29 <sarob> dguitarbite: i understand github and launchpad are separate
17:20:33 <dguitarbite> it would be simpler I guess to know that its kind of trivial to do it on our own
17:20:37 <dguitarbite> once the repos are set
17:20:50 <sarob> dguitarbite: we have a series of things to do as part of branching
17:21:30 <sarob> dguitarbite: i just want to understand what we are supposed to be doing in launchpad as well when we branch
17:22:12 <sarob> dguitarbite: i dont think its a big deal
17:22:24 <dguitarbite> sarob: I may not be accurate but I think we need to register a new seriers name it icehouse and track it to the icehosue branch
17:22:35 <dguitarbite> but I can be totally wrong
17:22:45 <dguitarbite> as I told before I do not know much about how to go with launchpad
17:22:51 <sarob> dguitarbite: i can fiddle with it
17:24:05 <sarob> dguitarbite: i think we can figure this out alot faster by working with the rest of the docs cores, or not
17:24:48 <sarob> it looks like the manuals juno series hasnt been released in launchpad #link https://launchpad.net/openstack-manuals/juno
17:25:19 <sarob> dguitarbite: ill ping the docs cores over the ML with a link to your spec
17:25:19 <dguitarbite> sarob: I think that we have more pressing matters than trying to figure out how launchpad works
17:25:30 <dguitarbite> RST content and branching is more important
17:25:35 <dguitarbite> IMO
17:25:41 <matjazp> dguitarbite: exactly
17:25:51 <sarob> okay guys
17:26:11 <sarob> so what other work on branching do we have left
17:26:35 <dguitarbite> we just need to add the watermark and get some feedback from the docs team
17:26:38 <dguitarbite> rest of the work is done
17:27:46 <sarob> dguitarbite: are you going to add the watermark as a patch, the spec as dependent
17:28:26 <sarob> dguitarbite: i will remove my launchpad comment and figure out later
17:28:47 <dguitarbite> sarob: I think Ill add it to the existing patch in the review
17:28:50 <dguitarbite> pipeline
17:29:09 <matjazp> talking about specs... are we still blocked by https://review.openstack.org/#/c/133372/ for new specs?
17:30:04 <sarob> matjazp: yes we are
17:30:23 <dguitarbite> matjazp: sarob it does not matter
17:30:29 <dguitarbite> just push the patches
17:30:40 <dguitarbite> the code can be rebased and cherrypicked once ready to be merged
17:31:09 <dguitarbite> create a folder kilo and add your spec file, just make sure that the file names are not conflicting with other patches in the review and it should be fine
17:31:40 <sarob> dguitarbite: we dont need the index.rst file
17:32:01 <dguitarbite> sarob: as I said that can be figured out and fixed once the spec is reviewed, later on
17:32:14 <sarob> dguitarbite: okay
17:32:39 <dguitarbite> if any doubts, I have done the same
17:32:44 <dguitarbite> and people have reviewed the spec
17:32:51 <sarob> dguitarbite: its not a problem
17:33:18 <sarob> dguitarbite: i will switch my #link https://review.openstack.org/#/c/140109/ then
17:34:00 <sarob> lets move to the next topic
17:34:07 <sarob> #topic kilo blueprints
17:34:17 <sarob> since we kinda are already
17:35:12 <sarob> #link https://blueprints.launchpad.net/openstack-training-guides
17:35:44 <sarob> from #link https://etherpad.openstack.org/p/training-guides-kilo-summit
17:35:50 <sarob> the bottom of the etherpad
17:36:15 <sarob> we selected a few blueprints that each of us want to work on
17:36:39 <sarob> matjazp: i need two specs
17:36:41 <matjazp> I want to change https://blueprints.launchpad.net/openstack-training-guides/+spec/moodle-for-online-quizzes to smth more general... I work with Moodle every day and I'm not impressed. I would like to step back and get the feedback from the community about alternatives. If nothing better pops up, we use Moodle.
17:37:21 <sarob> matjazp: okay, i create another and then push a spec linked to it
17:38:00 <matjazp> ok... I'm wrinig a spec for "Online Assessment for Training Guides". Will create a BP then
17:38:28 <sarob> matjazp: bp is edited and here #link https://blueprints.launchpad.net/openstack-training-guides/+spec/online-quizzes
17:39:14 <matjazp> ok
17:39:28 <sarob> cool
17:39:59 <sarob> so dguitarbite: you have two bps
17:40:13 <sarob> plus the branch
17:40:26 <dguitarbite> sarob: yes, I think may be more than two bps
17:40:31 <dguitarbite> I do not know the numbers
17:40:37 <dguitarbite> but they will be proposed soonish
17:40:44 <dguitarbite> if all goes as planned before the new years
17:40:45 <sarob> kvm/libvert osbash support
17:40:59 <sarob> dguitarbite: cool thanks
17:41:44 <sarob> matjazp, dguitarbite: think about which of M2 or M3 you can assign to the bp
17:41:51 <sarob> sign up for rather
17:42:24 <sarob> sayali: you have two bp as well
17:42:41 <sarob> sayali: well maybe three
17:42:49 <sayali> yeah I will be helping dguitarbite with a few things and one of my own
17:43:19 <sayali> so 3 in all that I will be contributing to
17:43:32 <sarob> color support for osbash and videos you will be primary?
17:43:38 <sayali> yep
17:43:52 <sarob> cool
17:44:07 <sarob> sayali: can i get specs on these this week?
17:44:27 <sarob> sayali: and an estimate of m2 or m3 as deadline
17:44:34 <sayali> sarob: yes I will be able to do it this week
17:44:43 <sarob> sayali: cool thx
17:45:05 <sarob> there are a few others without signups
17:45:14 <sarob> thats okay for now
17:45:41 <sarob> i covered the third topic already
17:45:43 <MeganR> sarob: Shilla won't be able to make the meeting today - is there anything you want me to pass on to her?
17:46:42 <sarob> meganr: she should comment on any specs for bp she has signed on for when they get pushed
17:46:56 <MeganR> ok, will do - thank you
17:46:57 <sarob> we have two last things
17:47:06 <sarob> one of them has to do with shilla
17:47:31 <sarob> #topic requirements for core reviewers
17:48:10 <sarob> #link https://wiki.openstack.org/wiki/Training-guides#Core_Reviewer_Responsibilities
17:48:31 <sarob> i cleaned up the wiki page last week
17:48:53 <dguitarbite> sarob: it looks much better
17:49:27 <sarob> along with that, core reviewers req were debated amonst the core reviewers
17:49:31 <rluethi> sarob: thanks.
17:49:31 <sarob> dguitarbite: thx
17:50:07 <sarob> any questions on the core reviewer req
17:50:38 <sarob> i dont think its very controversial
17:50:53 <sarob> pretty much the same as other groups
17:51:14 <dguitarbite> sarob: I agree, if we all agree to the points, lets push them to a wiki page
17:51:27 <dguitarbite> for better documentation and then edit/update it as required in future
17:51:43 <sarob> dguitarbite: right
17:52:50 <dguitarbite> rluethi: matjazp do we agree on the points? if not just post a comment on the ML
17:53:13 <matjazp> dguitarbite: I alredy commented on ML. I agree
17:53:28 <rluethi> dguitarbite: I think we are in agreement.
17:53:45 <dguitarbite> :)
17:53:57 <sarob> so sayali and shilla have been discussed as new core reviewers
17:54:22 <sayali> cool!
17:54:51 <dguitarbite> sayali: discussed not decided if I read sarob's comment properly
17:55:05 <sayali> yep i know
17:55:12 <sarob> dguitarbite: yeah, we should discuss here
17:55:54 <sarob> and i want to make sure that no one feels like its bad if they dont meet the bar for core reviewer yet
17:56:05 <dguitarbite> call for vote?
17:56:09 <sarob> just means we need something more
17:56:13 <sarob> dguitarbite: yes
17:56:25 <sarob> member only cores should vote on this one
17:57:02 <sarob> #startvote sayali as core reviewer
17:57:03 <openstack> Unable to parse vote topic and options.
17:57:13 <sarob> #startvote sayali as core reviewer?
17:57:14 <openstack> Begin voting on: sayali as core reviewer? Valid vote options are Yes, No.
17:57:15 <openstack> Vote using '#vote OPTION'. Only your last vote counts.
17:57:28 <sarob> Yes
17:57:46 <matjazp> #vote yes
17:57:55 <sarob> #vote yes
17:58:14 <dguitarbite> #vote yes
17:58:23 * rluethi abstains
17:58:33 <sarob> #showvote
17:58:49 <sarob> #endvote
17:58:50 <openstack> Voted on "sayali as core reviewer?" Results are
17:59:43 <sarob> #startvote shilla as core reviewer?
17:59:44 <openstack> Begin voting on: shilla as core reviewer? Valid vote options are Yes, No.
17:59:45 <openstack> Vote using '#vote OPTION'. Only your last vote counts.
18:00:32 <rluethi> #vote no
18:00:39 <sarob> #vote no
18:00:45 <matjazp> #vote no
18:01:05 <dguitarbite> #vote no
18:01:08 <sarob> #endvote
18:01:09 <openstack> Voted on "shilla as core reviewer?" Results are
18:01:30 <sarob> okay i will reach out to shilla and discuss with her
18:01:33 <krtaylor> time
18:01:39 <sarob> #endmeeting