17:02:11 #startmeeting training-guides 17:02:12 Meeting started Mon Dec 22 17:02:11 2014 UTC and is due to finish in 60 minutes. The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:02:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:02:15 The meeting name has been set to 'training_guides' 17:02:29 Hello 17:02:34 hello 17:02:35 hey 17:02:41 hi 17:02:49 Hi 17:03:12 Let's dig in 17:03:30 #topic branching 17:03:56 Dguitarbite how's it going? 17:04:09 waiting for docs team to merge the spec, the required changes are implemented 17:04:37 #link https://review.openstack.org/#/c/141369/ 17:05:43 Got my posture 17:05:43 anne already gave +2 so it's just a matter of time (and proofreading :) sean will give +2 too, right :) 17:05:46 Arg 17:05:51 Positive 17:06:07 Just did 17:06:11 sarob: thanks 17:06:34 New patch so need annegentle to review it once more 17:07:03 sarob: AFAIK shes happy with the patch and we are waiting for Andreas to comment on it 17:07:19 Question about juno branch 17:07:28 sarob: shoot 17:09:01 that must be one helluva question. 17:10:03 So 17:10:03 If we branch with only xml and scripts 17:10:03 We merge RST 17:11:07 Update scripts to include juno 17:11:07 Then branch again, 17:11:07 Quickly? 17:11:07 So we can focus on kilo? 17:11:07 Whatca think? 17:11:35 sarob: I think we discussed this earlier 17:11:38 but ill repeat 17:11:55 Juno till Feb 15 ~ depending on various things ofcourse it may be delayed 17:12:02 and then release Juno 17:12:14 go on with Kilo hopefully with the docs team 17:12:14 Dguitarbite did we? 17:12:24 sarob: yes 17:12:25 *Feb 2015 17:12:55 so by the Kilo release we should expect training-guides to be on track with other projects (release schedule wise) 17:12:57 Hmm, so I don't forget again 17:14:28 #action sarob create another bp and spec to track the goal of juno branch by 2015 feb 17:14:43 So I don't forget again ;) 17:15:06 Let's move on then 17:15:22 #topic kilo blueprints status 17:15:36 I can go first 17:15:45 sure 17:16:34 I've got a few patches out there 17:16:43 Pending branch 17:17:40 sarob: there7s still a question of how to progress after we branch.. see #link https://review.openstack.org/#/c/142350/ comments at the end 17:17:47 I will be posting the rest next few days 17:18:40 what do others think of this? merge as a starting point so we can all contribute ASAP? 17:19:38 I think we should wait till we branch 17:19:44 matjazp: as long as we are confident that it will come out of draft mode in the foreseeable future... 17:19:49 Matjazp the plan is to branch icehouse with xml only 17:19:49 I'm hopeful we can branch today or tomorrow 17:19:54 sayali: absolutely. 17:19:59 matjazp: first thing would be to wait for branch, after that delete the XML content which should be one single patch and then start pushing Juno stuff into master branch 17:20:03 till we release Juno 17:20:13 sayali: I agree 17:20:42 yes, that's why I said AFTER we branch.. of course we branch first 17:21:04 Dguitarbite we shouldn't make any huge changes 17:21:28 I think deleting all the content is a huge change 17:21:55 sarob: I thought that's what we've been saying since Paris. 17:22:09 We can move through the chapters as patches pretty quickly 17:22:40 18 dec goal is about making this change quickly 17:22:44 sarob: I do see a point in deleting content chapter wise 17:22:55 For getting the rst up 17:22:55 may be book wise would be good 17:23:07 But don't want to break it 17:23:13 sarob: break what? 17:23:30 The published content 17:23:39 sarob: that will be taken care of 17:23:48 the end-users will not see any downtime if that is what you mean 17:23:56 Yeah I know we can do it 17:23:57 the XML content will still be published as it is now 17:24:21 While we are getting the rst HTML fixed up 17:24:38 We still have the rest published 17:24:52 Could be as short as a day 17:24:58 Transitsition 17:25:19 But with patch review and holidays 17:25:23 Never know 17:26:25 And there is reeds patch for hieroglyph 17:27:03 yeah, I was just thinking about that ... hieroglyph is not bad 17:27:09 sarob: so what do you propose? 17:27:48 Rluethi we branch so we can move forward 17:27:54 We start merging rst 17:28:04 but I am not sure mixing slides and text-based content in the same file is really a viable option 17:28:41 sarob: I think we all agree that we want to branch soon. Do you want to vote on that? 17:28:52 In parallel we agree or disagree on landslide or hieroglyph 17:29:06 i personally agree on hieroglyph 17:29:07 there are some projects that can generate different HTML5 presentations from RST source. 17:29:28 although I don't disagree on anything else either 17:29:32 if reed prefers hieroglyph, I support it, too. 17:29:43 And once we are ready to publish slides we switch 17:29:47 sarob: I agree on Hieroglyph 17:29:55 I think we should have a vote on this 17:30:00 And then patch to remove xml 17:30:24 sarob: I thought first thing after branching is cleaning up the XML content 17:30:37 we will have it in the Icehouse branch 17:31:01 But we still need the published xml 17:31:03 reed, how do you propose to keep text (eg. presenatation notes)? 17:31:17 reed: separate document? 17:31:28 matjazp, notes should stay in the hieroglyph file 17:31:31 As HTML 17:31:51 hiero can build notes as presenter's notes :) 17:31:58 just like landslide 17:32:17 reed: ok, thanks 17:32:25 Dguitarbite shouldn't we wait to reemove xml until rst is ready to be HTML published 17:32:49 sarob: we have the content in Icehouse, it will not have any effect on the docs.openstack.org page either 17:33:04 I prefer cleaning up the mess as its difficult to do that once the RST content is in 17:33:17 and I am afraid of new people patching on the XML code 17:33:19 Dguitarbite hmm, okay 17:33:31 thats another thing I prefer to totally avoid 17:33:58 exactly. 17:34:00 dguitarbite: patches will come as ppl will use icehouse version of the docs, I'm afraid 17:34:07 Dguitarbite avoiding zombie xml patches 17:34:19 dguitarbite: so some proosed patches will come nevertheless 17:34:24 matjazp: bugs mostly and they can be backported I will love to have them 17:34:38 but if the same patches are there in the master branch then we need to maintain two copies 17:34:46 and backport them etc. etc. 17:34:53 should we not make our lives easier? 17:35:28 Dguitarbite yes easier is good 17:35:33 dguitarbite: I'm sold on "make our lives easier" ;) 17:35:50 I am not saying that XML content will be completely removed :), they will be maintained in the Icehouse branch 17:35:52 :) 17:35:53 yes makes sense :) 17:38:08 And sense it's part of the branching spec I +2 17:38:14 ;) 17:38:42 So we need more specs 17:39:05 If you have signed on for a bp 17:39:05 I have pushed 1 patch https://review.openstack.org/#/c/143270/ 17:39:12 but it needs some more work 17:39:24 And one more will come soon 17:39:32 I see 17:39:46 Sayali I will review 17:39:52 I need to do some more findings for the 2nd one 17:40:25 Sayali okay, get it pushed as soon as you can 17:40:31 sure, you can do that after I upload the new patchset 17:40:53 Matjazp we need a couple of specs for your bp as well 17:40:55 I'm still a bit behind on my specs. Some urgent work before holidays kick in I'm afraid.. 17:41:20 Matjazp understood 17:41:23 will try to finish both of them asap 17:41:39 Matjazp we are all volunteers here 17:41:49 Matjazp so we do what we can 17:42:03 My spec has been in limbo for two weeks and I am very okay with where it is. https://review.openstack.org/#/c/137299/ 17:42:34 It won't make it in kilo. 17:42:40 I was talking with my coworker Miha about joining in occasionally... 17:42:54 may be you need to learn from inception and try and get it out of limbo asap or you may get lost! 17:43:32 Rluethi I was distracted with the other work 17:43:45 Rluethi I will comment 17:43:51 sarob: excuses, excuses :) 17:44:14 Rluethi I've got hundreds of em 17:44:42 Let's move on 17:44:42 seriously, though, we don't have the resource to do it. but hopefully we will get additional information in this cycle that will helps with it eventually. 17:44:44 hehe-- there are always Christmas miracles, right? Maybe Santa can deliver some quality Specs under my tree 17:45:01 matjazp: good luck with that :) 17:45:26 Rluethi yes, I believe we are getting traction 17:45:30 hehe 17:45:50 Rluethi we keep the work going 17:46:06 Rluethi more help will come 17:46:33 Rluethi esp with the user group visibility 17:47:05 Down soapbox 17:47:25 sarob: of course we are all interested in feedback from the pilot 17:47:58 I'm getting the trainers group started up 17:48:09 I've got some feedback for you rluethi 17:48:35 I've created a survey 17:48:36 matjazp: excellent. 17:48:45 sarob: cool! 17:49:04 everything works as it should (minus small issue with locale settings you already fixed) 17:49:36 #action sarob share user group training survey results with training team 17:49:48 matjazp: nice. I suppose you had no Windows users? 17:49:57 there are some issues with performance - nested virtualization on Virtual Box could be too slow for some advanced testing 17:50:40 matjazp: dguitarbite and sayali are working on KVM support, that should help with performance. 17:51:00 Rluethi I want to get the user group using osbash 17:51:00 rluethi: no, I didn't push it ;) We explicitly booted Linux (Ubuntu). But I will have more feedback after holidays, when they test at home 17:51:23 Rluethi need the trainers to include 17:51:50 matjazp: cool. feel free to give them my email address. 17:51:51 yes performance is much fater. dguitarbite had it running on KVM 17:51:51 Rluethi and learn how to manage with 30 people 17:52:19 faster* 17:52:58 * sarob osbash KVM spec..... 17:53:33 rluethi: maybe we should also look again at Vagrant- it already has many providers supported (KVM an HyperV inscluded) 17:54:17 sarob: that should also be pushed by eom as far as I remember my discussion with dguitarbite 17:54:28 matjazp: problem with vagrant is that it's non-trivial to install, even more so if you want to use its plugins. 17:54:40 Sayali okay 17:54:42 matjazp: _and_ rebooting during install is a PITA. 17:54:47 rluethi: non trivial? how so? 17:55:00 rluethi: yes, rebooting is an issue 17:55:41 Real quick 17:55:50 Before we run out of time 17:56:12 matjazp: the versions of vagrant that come with various distros are quite different, so we might have to ask users to manually install an update. 17:56:28 I want to propose we use the nova method for proposing new core reviewers 17:56:55 rluethi: yes, but this is covered on the net in countless blog posts 17:57:04 matjazp: on Windows, last time I checked there were environment variables to set, and installing plugins required extra work. 17:57:14 sayali: eom? 17:57:52 #link https://wiki.openstack.org/wiki/Nova/CoreTeam#Adding_or_Removing_Members 17:57:57 dguitarbite: was it later? I could have misunderstood 17:58:11 Read up and let's discuss next meeting 17:58:12 sarob: first thiings first, release 17:58:19 I dont want to do 100 things at the same time 17:58:38 I'm good with that 17:58:39 dguitarbite: its a small thing to agree to 17:58:43 Last thing 17:58:52 Let's miss the next meeting 17:59:01 :) 17:59:09 Next meeting 06 January 17:59:22 That's two meeting miss 17:59:36 k 17:59:39 ok 17:59:40 Everyone good with that? 17:59:46 yep 17:59:54 wait, on a tuesday? 18:00:09 Oops that week the 18:00:13 The 18:00:16 Then 18:00:20 okay, 5th then. 18:00:26 Right 18:00:34 Time to go 18:00:42 bye 18:00:45 bye all 18:00:45 Merry Christmas everyone 18:00:49 happy hollidays 18:00:53 bye! 18:00:54 And cheers! 18:00:58 happy holidays :) 18:01:01 bye 18:01:15 #endmeeting