14:01:45 #startmeeting docteam 14:01:46 Meeting started Wed Jun 11 14:01:45 2014 UTC and is due to finish in 60 minutes. The chair is Sam-I-Am. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:50 The meeting name has been set to 'docteam' 14:01:55 thanks 14:02:06 Sam-I-Am started so I can leave early, my apologies but an appt. I can't miss. 14:02:09 Here's the agenda 14:02:19 #link https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting 14:02:20 i have it up... 14:02:36 #topic action items from last meeting 14:02:46 Let's review the action items 14:02:53 good morning 14:02:53 both were Andreas's and he's out this week and next 14:02:57 morning dianefleming! 14:03:07 Andreas will streamline the Documentation/HowTo page 14:03:08 the last apac meeting mostly didnt happen, so this goes back to 5/21 14:03:18 and we're abandoning the separate writers guide 14:03:24 that's it for actions 14:03:44 #topic training team migration 14:03:46 Let's discus the Training team move to separate repo; looking for core reviewers 14:04:11 The repo is now set up since https://review.openstack.org/#/c/96334/8 merged 14:04:29 Next I'll propose the change to the governance repo to point to it under the Documentation Program 14:04:42 i can support with reviewing the training guide 14:04:53 berendt: great! 14:04:57 sarob approched me about reviewing the training guide since it does/will reference parts of the installation guide 14:05:02 the repo is openstack/training-guides 14:05:18 Sam-I-Am: I'm encouraging them to use as much of it as possible 14:05:23 it makes sense 14:05:36 Phil and I are looking at scripted labs -- I like the idea very much 14:06:09 Sean (sarob) and I talked yesterday and I want to give the team time to get ramped up, but also ensure quality, by the Juno-2 milestone release 14:06:15 That's July 24th 14:06:19 (juno-1 is tomorrow) 14:06:27 I believe they are the way to go 14:06:28 wow, sosoon 14:06:40 feels like we just released! 14:06:41 the TC gives teams 2 milestone releases, so the July 24th date is simply a check in 14:06:55 I'd prefer that the training group focus on training deliverables -- the lab is a great example 14:07:13 my general sense is that the guides have quality issues but they are working towards our conventions and so on 14:07:21 I think they will also track their bugs separately 14:07:25 any questions? 14:08:03 The mailing list thread has the most indepth info 14:08:19 #link http://lists.openstack.org/pipermail/openstack-docs/2014-June/004572.html 14:08:28 Ok, next topic, Style questions: IBM Style Guide for core reviewers 14:08:39 #topic ibm style guide for core reviewers 14:08:57 I've sent emails to our current core except for Lorin who's not working on OpenStack anymore, boo hoo 14:09:04 You can either get a Kindle version or a paperbook 14:09:21 thing is, there are only 6 copies paperback available right now, so I'm working through the preferences and shipping 14:09:26 Will probably take me the rest of this week 14:09:34 cool 14:09:42 The idea is, while reviewing, use the IBM Style Guide for anything that isn't covered in our Conventions page 14:09:47 is it possible to get the kindle version for non-core reviewers? 14:09:55 #link https://wiki.openstack.org/wiki/Documentation/Conventions 14:10:20 berendt: I couldn't find a way to "lend" but I can probably just get Rackspace to buy you one if you want 14:10:46 Seems useful for people who review often 14:11:07 at least I try this so I think it would be useful to increase the quality of my reviews 14:11:38 Sam-I-Am: one thing I wondered is if the IBM style guide answered your last two questions to the mailing list? 14:11:40 Wish there was and easy way to get more copies 14:11:56 phil_h: it's not hard - if you want one I'll find you one 14:12:03 annegentle: i hadn't looked... i can do that. 14:12:09 the key is finding stuff 14:12:12 thanks 14:12:13 I've let the Rackspace editor know we won't need the Rackspace one 14:12:28 #action Anne to send IBM Style Guide Kindle to berendt 14:12:35 phil_h: do you want paperback or kindle version? 14:12:54 @annegentle can you add a link on the conventions page to the kindle version? 14:13:00 so anyone can get it? 14:13:09 kindle would be fine if I can use my android 14:13:19 i think there's a kindle reader app for most platforms 14:13:24 yes 14:13:26 #action Anne to send IBM Style Guide Kindle to phil_h 14:13:28 Yep 14:13:42 Ok, I'll keep working that list 14:13:44 phil_h: https://play.google.com/store/apps/details?hl=en&id=com.amazon.kindle 14:13:49 Irony moment: buying from amazon. :) 14:13:53 lol 14:14:14 Ok, wanted to make sure everyone knows about the decisions on Debian install guide reviews 14:14:31 #topic debian install guide reviews 14:14:41 that was a fun thread 14:14:42 Oh and one other thing about IBM Style Guides, many RedHat writers already have it 14:15:09 Sounds like it's all resolved, I appreciate everyone's discussion on the list (and that I didn't have to break out of vacay mode) :) 14:15:11 i was thankfully away looking for housing for most of it... but i tried to sum it up with a happy conclusion 14:15:24 It seems like the reviews are going oka 14:15:25 okay 14:15:31 tom agreed with the two resolutions 14:15:34 and I guess he keeps the screenshots? 14:15:46 I was just trying to make sure I know how to review, also 14:15:58 seems like we add zaro (Thomas Goirand) to those patches as reviewer 14:15:59 screenshots = no good! 14:16:02 for now, yes... but there will be more 'translatable' information surrounding the screen shots 14:16:19 annegentle: yes, he gets tagged in debian-affecting patches (like most of the install guide improvements) 14:16:33 whether or not he wants to do his stuff as separate patches is his choice 14:16:43 right now i'm trying to leave the debian stuff as-is as much as possible 14:17:09 Okay 14:18:05 The Mailing List thread crossed the May/June boundary, but I think it's all wrapped up here 14:18:07 #link http://lists.openstack.org/pipermail/openstack-docs/2014-June/004563.html 14:18:22 Any questions? 14:18:41 just a correction, Thomas' nick is zigo ;) 14:18:49 gpocentek: ha! Thanks! 14:18:58 somewhere in that is the conclusion of the thread 14:19:02 gpocentek: And I'm around! :) 14:19:06 That's right, zaro is... now I forget! 14:19:10 zigo: hiya! 14:19:17 annegentle: Hello! :) 14:19:26 #link http://lists.openstack.org/pipermail/openstack-docs/2014-June/004579.html 14:19:28 zigo: Any remaining concerns about Debian and install? 14:19:30 thats the summary 14:19:45 annegentle: Well, I still got some remaining patch review not done. 14:19:53 thanks Sam-I-Am 14:20:16 zigo: ok yep 14:20:18 #link https://review.openstack.org/#/c/98329/ 14:20:23 That one needs review 14:20:32 https://review.openstack.org/97158, https://review.openstack.org/96687, https://review.openstack.org/98329 14:20:34 Ah, and a rebase 14:20:41 yeah, a rebase... 14:20:46 the qm/mq thing 14:20:46 Yeah, will work on that. 14:20:52 Ok, I'll also add those links to this week's What's Up Doc so people can take a look 14:21:02 Plus I need to explicitely write what some debconf screen do in the directives, but that's going to be later on. 14:21:04 zigo: anything else you can think of? Thanks for the discussion 14:21:27 That's going to be within each service chapters... 14:21:41 Like for example, the core_plugin directive in Neutron, etc. 14:21:56 zigo: to avoid patch collisions, for the larger 'install guide updates' patches... do you want to edit the big patch, or upload another patch after approval to handle the debian stuff? 14:22:20 I'm trying to get my patches as small and incremental as possible, yeah. 14:22:32 ok, so sounds like a separate patch later then 14:22:36 can you tag me in your patches 14:22:49 You mean add you for the review? I will, thanks. 14:22:52 yeah 14:22:58 sounds good 14:22:59 https://review.openstack.org/97158 <--- For that one, I'm not sure how to handle it. 14:23:19 No, not that one, hang on. 14:23:22 and we'll tag you in the 'big' install guide update patches, but mainly just to make sure we didn't completely break the debian stuff. you'll do your improvements in a later patch. 14:23:30 zigo: ah we might need to ask sgordon to look again? 14:24:10 That one: https://review.openstack.org/#/c/96687/ 14:24:23 Andreas wrote (rightfully) that there was some redundancy. 14:24:30 And that I wrote 3 times the same thing. 14:24:40 zigo: he's good at spotting inefficiency :) 14:24:43 i think 97158 is pre-conclusion of that e-mail thread 14:24:44 I agree, though it was like that previously, it just shows more now ... 14:24:47 So I wonder how to fix. 14:25:00 Probably first remove the redundancy everywhere first? 14:25:24 Sam-I-Am: agreed on 97158 14:25:27 i'd need to look closer at the patch 14:25:51 zigo: for the redundant, is it really just the screenshot that's unique to debian? 14:25:53 zigo: my suggestion is, for the most common debian stuff, provide a 'flagship' patch that sets the tone for all other patches 14:26:15 then you can use it as a template for the other patches 14:26:16 annegentle: That's my point, I replaced something redundant by something else (redundant screenshots). 14:26:23 zigo: ah :) 14:27:06 And I'm really not sure how to remove the redundancy then ... 14:27:25 Create another section, and refer to it at the 3 places? 14:27:28 (with a link) 14:27:51 why not working with includes for the moment? 14:28:11 zigo: I'll comment in the patch itself 14:28:22 Thanks! :) 14:28:32 I don't need an answer right now... 14:28:40 berendt: zigo: includes might work, but basically you do the same thing on all three nodes? 14:29:03 (thing=same configuration of networking) 14:29:10 ah precision with language 14:29:15 the nodes are mostly the same 14:29:27 Ok maybe we can get to one more topic before I have to leave? Do comment in reviews. 14:29:34 at least for neutron.conf 14:29:37 sure 14:29:45 I think it was berendt who asked about how to make the Glossary alphabet headers list in a TOC? 14:29:53 oh, there was one thing before that 14:29:56 but we can hit that topic 14:29:58 oh yes 14:30:22 #topic how to make glossary alphabet headers list in a toc 14:30:23 Just going to say, I talked to David Cramer and yes it can be changed in the XSLT 14:30:51 berendt: I asked him to write back on the list, it's either webhelp.xsl or docbook.xsl that has the logic 14:31:01 and... I'd better go so I'm not late to the eye doc... thanks Sam-I-Am! 14:31:07 and thanks all for joining! 14:31:09 have fun! 14:31:16 I had a short look but not yet the time to work on the glossary 14:31:19 we'll hit the last topic here... 14:31:53 #topic review change options automation 14:31:59 #link https://review.openstack.org/#/c/97621/ 14:32:39 more eyes of this patch would be nice 14:32:41 i suspect we should take a look at that patch 14:33:21 Andreas suggested another way to deal with changed options but it will be more tricky to handle 14:33:23 https://review.openstack.org/#/c/97620/ is not yet merged 14:34:09 berendt: reviews on the output will help fix/modify the code 14:35:56 anything else here? 14:36:22 #topic open discussion 14:36:49 a few things going on here. i completed a havana-to-icehouse upgrade on rhel yesterday, so will be working on a patch to the ops guide 14:37:10 also, i'm moving and starting a new job so i might go dark for a bit starting in a couple of days 14:37:42 I have both linuxbrige working with OVS on different nodes and I see a couple of doc bugs that I need to file 14:37:44 congrats on the new job :) 14:37:56 We are happy to get him 14:38:09 oh, new job at rackspace? 14:38:11 yup 14:38:16 awesome! 14:38:40 gonna try to get these few install guide patches through before i disappear for a bit 14:38:45 @Sam-I-Am CONGRATS!! 14:38:54 the ops guide patch... maybe. 14:39:50 aight, anything else? 14:41:02 guess we're done here 14:41:06 thanks everyone 14:41:11 #endmeeting