17:00:43 #startmeeting training-guides 17:00:44 Meeting started Mon Feb 23 17:00:43 2015 UTC and is due to finish in 60 minutes. The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:47 roll call 17:00:48 The meeting name has been set to 'training_guides' 17:00:50 hey 17:00:52 hello 17:00:59 \o/ 17:01:39 hey 17:01:46 heloo hello 17:02:06 hi 17:02:19 dguitarbite? 17:02:29 vigneshvar: hello 17:02:45 sarob: hello :) 17:03:02 hi sarob, vigneshvar 17:03:18 hi matjazp 17:03:40 dguitarbite might be sleepy after getting the gate working 17:04:11 #topic state of the gate 17:04:39 thanks to matjazp ajaeger dguitarbite for working on gate issues 17:04:49 #link http://docs.openstack.org/icehouse/training-guides/content/ 17:05:07 #link http://docs.openstack.org/training-guides/content/ 17:05:56 matjazp any update on getting the new landing page plus slides working? 17:06:22 sarob: dont know for landing page 17:07:40 matjazp: you were working on fixing up some failing build pages though 17:08:12 sarob: yes, I fixed broken repo https://review.openstack.org/#/c/158140/ 17:08:16 its merged 17:08:55 matjazp: thank you. 17:09:01 matjazp: nice 17:09:48 so the last bit is trunk/training-guides publishing needs to fixed 17:10:21 right now it looks like it is the icehouse content 17:10:24 or it didnt get removed 17:10:31 after the last publish 17:10:40 prob the later 17:10:44 we don't have enough content 17:11:07 for trunk to get published 17:11:17 we need a complete set of lides 17:11:20 slides 17:12:16 true 17:12:23 all of the xml-to-rst bp 17:12:34 then can we enable publishing 17:13:06 jump agenda a bit 17:13:21 since we are discussing 17:13:25 #topic state of juno content 17:13:41 #link https://review.openstack.org/#/q/status:open+project:openstack/training-guides,n,z 17:14:35 labs-scripts for Juno are merged. 17:14:45 we are ready to branch kilo :-). 17:14:50 rluethi: excellent 17:14:51 yes :D 17:15:49 can you guys take a look at the chapter content 17:16:02 give a merge 17:16:10 if its ready 17:16:24 then we can get publishing back on track 17:16:36 sure 17:17:21 we are dangerously close to getting ourselves ready for inclusion into openstack.org/training 17:17:26 landing page 17:17:50 i dont want to make the argument until our publishing is all ready 17:18:15 sarob: but do we know where we will be included? 17:18:26 sarob: where the link will be? 17:18:49 i am going to make the argument for mid right hand side of the training page 17:19:31 in the openstack online help panel 17:20:05 hello 17:20:06 as i work through the ambassador group and my new user group assistants 17:20:18 apologizes for being late, was busy with a few meetings 17:20:20 dguitarbite: evening 17:20:29 dguitarbite: thx for gate! 17:20:33 morning/evening guys 17:20:45 dguitarbite: no prob 17:20:47 hi dguitarbite! 17:20:50 dguitarbite: hello 17:20:56 dguitarbite: you have been doing late night work 17:20:57 sarob, ajager needs the real thanks 17:21:15 dguitarbite: good enuf 17:21:30 dguitarbite: beers all around in vancouver if possible 17:21:39 sarob, thanks 17:21:44 :) always ready for beers 17:21:50 dguitarbite: roger that 17:22:04 who called me? 17:22:09 lolz ;) 17:22:10 well the other roger 17:22:18 roger roger 17:22:41 so the general idea for the training landing page 17:23:10 is to get our link into the openstack online help panel 17:23:33 and as we get user groups spun up on using the assoc and dev content 17:23:58 we get their sessions into the course pull downs like any other training 17:24:22 i think it is simple and doesnt step on any commercial toes 17:25:19 dguitarbite: how can i help with the landing page and trunk publishing fixup? 17:25:24 sarob: we can get "lost" among other commercial training offers 17:25:54 sarob, we need to first merge the RST and have the content ready to be published 17:26:08 dguitarbite: agreed 17:26:09 then we need some more HTML/CSS juice to pump on openstack.org 17:26:35 without the final content it will be difficult to setup the infra or even convience the infra team for the publishing etc. 17:26:36 dguitarbite: we are very close to having all of juno content ready 17:26:56 dguitarbite: need some reviews and a bit more fix up 17:27:26 sarob, yes, I will be reviewing this week 17:27:34 dguitarbite: coolo 17:28:50 dguitarbite: so id like to help if I can with the publishing details like landing page and publish 17:28:52 sarob, yes, now the priority goes for working on the RST 17:28:59 fixup, if I can be of use 17:29:05 I think the juno labs scripts are mostly merged and stable 17:29:11 when we are ready later this week 17:29:31 sarob, the landing page part sounds good, I am really terrible at HTML/CSS part 17:29:40 dguitarbite: me too 17:30:04 dguitarbite: i can use bluehost tools to get us started 17:30:12 dguitarbite: for juno 17:30:17 bluehost? 17:30:22 dguitarbite: then we can lean on reed and others 17:30:26 dguitarbite: my isp 17:30:36 dguitarbite: and hosting provider 17:30:51 dguitarbite: isp says it all 17:31:30 lets see if we can beat the 02mar juno branch by a day or two 17:31:44 sarob, which website do you have in mind? 17:31:55 reed: morn 17:32:25 reed: we need to create a landing page for the training guides trunk publishing page 17:32:31 sarob, I am not sure if that would work or is a feasible option 17:32:42 we should try to host the content on openstack.org itselves 17:32:54 since we are not going to hog a lot of memory/storage for sure 17:33:01 dguitarbite: you misunderstand 17:33:26 dguitarbite: i only meant i was planning on using their html gen tools 17:33:31 dguitarbite: not hosting 17:33:43 dguitarbite: i personally use bluehost for hosting 17:33:46 dguitarbite, www.openstack.org is not the best place for it, at the moment at least 17:33:47 dguitarbite: for sarob.com 17:33:51 reed: sarob: in Paris we had talked about a link on the marketplace but still housed on docs.openstack.org 17:33:57 sarob, ok 17:34:06 annegentle: yup 17:34:19 annegentle: once our landing page is ready 17:34:30 annegentle, the marketplace has a clear scope focusing on commercial offerings, so that option is not available 17:34:43 annegentle: im going to ask for our link to be added to the training page under openstack online help 17:34:52 we could put it in groups.openstack.org 17:35:02 and a link from www.o.o/community 17:35:03 reed: got it 17:35:17 reed: I had hoped for a "community" sidebox on the marketplace 17:35:40 maybe even host parts of the guides directly on www.o.o/community 17:36:31 reed: you dont think the community training could have a link in the online help section? 17:36:44 where is the online section? :) 17:36:53 online *help* 17:36:59 http://www.openstack.org/marketplace/training/ 17:37:11 reed: middle right 17:38:05 reed: right under getting started would be the place 17:38:07 * reed loading the site... taking forever 17:38:29 * sarob tap tap tap 17:38:45 sorry bad network 17:39:08 reed annegentle: lets sideline this to docs so we can finish our training agenda 17:39:14 reed: sarob: yes 17:39:26 reed: sarob: yes to sidelining, needs more discussion 17:39:40 sarob: cuz I'm kinda "not yes" on additions there :) 17:39:53 #topic path forward for merging upstream training 17:40:14 www is not loading on my side 17:40:15 reed: stay for this one if you can 17:40:22 sarob: I had to change some rst files to get them compliant to doc8 checks 17:40:36 #link https://review.openstack.org/#/c/132395/ 17:40:38 #link https://review.openstack.org/#/c/132395/ 17:40:47 beat you to it :) 17:40:49 * sarob got beat 17:40:59 ouch 17:41:09 so, still needs rebasing, doesn't it? 17:41:34 Patch in Merge Conflict 17:41:39 and it needs testing outside of my env :) I think it works for me 17:42:21 is this upstream university only, or intended for all slides? 17:42:52 I would like one solution for all content 17:43:04 sooo does this mean this rst will still publish for landslide 17:43:36 cause i thought we were going to push landslide for at least through kilo 17:43:41 then revisit 17:44:06 as long as the rst works both ways im all goodness 17:44:09 rluethi, it should work for everything 17:44:24 sarob, no landslide in my patch 17:44:39 reed: what's the difference in syntax between hiero an landslide? not much? 17:44:50 matjazp, not much, no 17:44:59 reed: can you rebase it on current master? there are merge conflicts, for instance in tox.ini, that I'm not sure how to resolve. 17:45:01 #action sarob work with reed annegentle on training guide inclusion into online help section of openstack.org/training page 17:45:16 rluethi, ok 17:45:30 reed: thanks! 17:45:42 #action reed to fix merge conflicts in https://review.openstack.org/#/c/132395/ 17:45:43 #action team review all existing rst patches, we need to merge them this week 17:45:46 matjazp, significant enough difference 17:45:53 dbyte_: like? 17:46:06 so, everyone, are we ready to move to sphinx? 17:46:06 matjazp, many minor details need to be changed 17:46:09 in the RST side 17:46:21 #action branch juno 02 march 2015 17:46:24 but overall sphinx should be better 17:46:42 I don't have a strong opinion either way, but I'd rather not have two tools for the same thing in the same repo. 17:47:03 #action landslide is the publishing tool through kilo, will revisit at the liberty summit 17:47:09 rluethi, +1 17:47:14 sarob, I finally loaded the marketplace/training page: you'll have to propose that to Marketplace manager (Heidi) 17:47:27 reed: understood 17:48:25 sarob: that's not an action :) 17:48:44 #undo 17:48:45 Removing item from minutes: 17:49:00 #info landslide is the publishing tool through kilo, will revisit at the liberty summit 17:49:02 thx 17:49:17 it would be an agreement (#agreed), if we had an agreement. 17:51:10 rluethi: two meetings ago with dhellman we discussed 17:51:15 rluethi: agreed, or at least i thought we did 17:51:30 sarob: fair enough :) 17:52:22 this is all a moot point.. if differences in rst syntax are small, we can switch easily anytime 17:52:35 I've already changed the slides not to use landslide 17:52:54 at least that's what I thought... 17:53:26 i'll have to sync up with the teachers of upstream training, will let them decide 17:54:00 reed: is there a difference in the published material? 17:54:08 reed: the result? 17:54:20 no, they all suck the same 17:54:23 matjazp: I sort of agree, but small differences may still trip up contributors, and newbies are likely going to be confused if different rst files are processed by different tools. 17:54:39 reed: i cant see a difference since it is using the same rules 17:54:40 the results are sucky either using landslide or the other thing 17:54:54 rluethi: yes, thats why I said that we can switch to hiero anytime 17:55:21 rluethi: yes we need one way to publish at a time 17:55:27 anytime could also mean right after reed merges his hiera patch :) 17:56:20 * sarob bangs head on table and passes out 17:56:53 any other parting thoughts? 17:56:54 * dbyte_ oh no now who will end the meeting! 17:57:08 i only want to get the publishing automation to be consistent and supportable 17:57:32 we need to get publishing up and running 17:57:43 so our customers can access the content 17:58:03 and we can find new customers through the user groups 17:58:50 meh. They don't pay me enough for me to call them customers. 17:59:00 I feel like we're running in circles here 17:59:14 #action reed will check on upstream training rst can be published through landslide through kilo release 17:59:31 dguitarbite has the landslide automation ready to go 17:59:36 no, please, don't drive me nut with formats 17:59:47 #undo 17:59:48 Removing item from minutes: 17:59:53 I think it's a waste of time to debate over format 18:00:00 reed: agreed 18:00:06 whatever works works 18:00:11 #action sarob will check on upstream training rst can be published through landslide through kilo release 18:00:22 reed: agreed 18:00:30 reed: exactly 18:00:33 right on time 18:00:37 end meeting. 18:00:40 :) 18:00:43 thanks 18:00:45 cheers everyone! 18:00:51 bye :) 18:00:54 #endmeeting