13:10:32 #startmeeting Doc Team Meeting 13:10:33 Meeting started Tue Aug 13 13:10:32 2013 UTC and is due to finish in 60 minutes. The chair is fifieldt_. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:10:34 yeah 13:10:34 ah. good to see RH putting folks for doc too :) 13:10:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:10:38 The meeting name has been set to 'doc_team_meeting' 13:10:46 yes, koolhead17 it's super awesome 13:10:49 hi also to dcramer_ 13:11:09 #topic Action Items from the last meeting 13:11:19 let's get the boring stuff out of the way 13:11:27 these can be found at 13:11:28 #link http://eavesdrop.openstack.org/meetings/doc_team_meeting/2013/doc_team_meeting.2013-07-09-13.01.html 13:11:38 #1 cyeoh to study openstack/compute-api for the v2 docs 13:11:46 cyeoh, did you have a chance to look into that? 13:12:08 cyeoh: so Kersten Richter has been looking at what is needed 13:12:24 I've been spending some time trying to work out how we can automate the process from test_api_samples in nova 13:12:50 #info Kersten Richter has been looking into api v2 docs 13:12:53 to produce enough information so we can generate what is needed for openstack/compute-api through a script (mostly) 13:13:13 #info cyeoh is still looking at automatically generating openstack/compute-api through a script 13:13:15 ceyoh, I didn't have a chance to get with you before I went out for shoulder surgery, do you still need to get with me for WADL help on that? 13:13:16 cool, that's great 13:13:53 roadnick: I think Kersten could probably do with a hand getting up to speed with things 13:14:06 hey sorry I'm late! 13:14:09 #action roadnick to meet with Kersten to help through the WADL journey 13:14:10 The nova side review is here: https://review.openstack.org/#/c/40169/ 13:14:13 hi annegentle 13:14:14 annegentle, np :) 13:14:20 we're just looking at action items 13:14:22 'just at number 1 13:14:29 Hi, annegentle 13:14:29 you have the con! 13:14:38 hi annegentle :) 13:14:40 ha 13:14:48 had to call for a dr appt for a kiddo, online now 13:14:56 Ceyoh, can you have her email me to set up a meeting, and do you have my email? 13:14:57 roadnick: still at the stage of trying to work out if we can do it, but in the meantime generating api samples anyway for V3 as we'll need them in the end. 13:14:59 annegentle: good morning :) 13:15:15 roadnick: how's your shoulder? 13:15:21 roadnick: no, what's your email address? I'll forward it on to her 13:15:38 nchase@mirantis.com 13:15:39 #topic Action items from last meeting 13:15:45 roadnick: thx! 13:16:05 painful, thanks, annegentle; at the "sick of being sick, have to be careful not to overdo it" stage :( 13:16:20 roadnick: oh I bet! 13:16:36 Ok, cyeoh to study openstack/compute-api for the v2 docs was from last month, how'd that go? 13:16:53 annegentle: I've passed most of it off to Kersten 13:17:19 heh ok old news, reading scrollback more carefully 13:17:31 I'm doing a bit on the Nova side to generate the api samples, and experimenting with also generating some metadata files which is (hopefully) enough to get a script to generate most of the doc 13:17:41 sarob's not around I guess? He was going to get cyeoh in touch with someone 13:18:15 I had asked Kersten to come to a Monday office hours and/or the boot camp, haven't heard from her though. 13:18:42 annegentle: unfortunately I think it's pretty unlikely she'd be able to get travel approval for the boot camp :-( But she is trying 13:18:42 cyeoh: does it make sense for her to work with someone else or continue to work with me? 13:18:52 cyeoh: ok, good to know 13:19:29 annegentle: she's still getting up to speed with it all. I'm meeting with her in a couple of days so will get an update then 13:19:38 cyeoh: ok 13:19:48 cyeoh: it's kind of a steep onramp 13:20:07 cyeoh: so I'm happy to help, and Diane's emailed her too 13:20:15 cyeoh: just don't want her to get mixed messaging from a bunch of us 13:20:25 Thanks for all the help! yea, I very much doubt we're going to make Havana, but hopefully not too long after... 13:20:56 cyeoh: well, I think the doc should come as soon as possible 13:21:31 annegentle: yea, its definitely a priority for us. Getting everything merged on the Nova side (api samples) is already looking pretty tight though 13:22:13 cyeoh: okay, good. Just didn't want to de-emphasize it even if v3 is "experimental" folks will be trying it out. It's what they do. :) 13:22:15 ok, next action was for me to find if maven plugin supports sets. It "Just Works" (tm) so that's good. 13:22:26 :D 13:22:31 great news 13:22:39 another action was anne to draft a Mission Statement for Documentation and send to docs mailing list. Done. 13:23:00 I haven't yet floated the Project Doc Lead idea... I have identified some people though so I might just reach out to individuals. Thoughts? 13:23:22 * fifieldt_ would like to see what that is written down :) 13:23:31 :P 13:23:49 fifieldt_: yeah we need a matrix of projects and peeps 13:24:01 agreed 13:24:02 koolhead17: you up for starting a wiki page with candidates for doc leads? 13:24:09 that would be good. 13:24:18 annegentle, as in what a "project doc lead" is 13:24:28 annegentle, sure. do we have many candidates in race? :) 13:24:33 fifieldt_: it was sarob's idea, let me dig up 13:24:48 i thougth we already selected you for that :D 13:25:01 The project doc lead was ... 13:25:17 the idea that each project will have one person who's a "liasion" for the docs for that project 13:25:37 #link https://wiki.openstack.org/wiki/Documentation/ProjectDocLeads 13:25:37 for example we'd have one person at Mirantis who's the "go-to" person for info on Savanna docs 13:25:40 roadnick, ahaan. makes sense 13:25:45 happy to see its happening 13:25:53 annegentle, hi5 13:26:05 I like the liaison idea for bug triage etc 13:26:14 was asking the same longtime back if you remember :D 13:26:39 I think that page needs a bunch more clarity before titles are handed out 13:27:03 I'm all for the idea, just don't want to see it fall down due to a lack of planning/definition 13:27:11 +1 13:27:21 fifieldt_: yeah I'm with you. the projects are quite disparate so I want some sort of matrix for more analysis 13:27:43 matrix still sounds like the line of thinking is more about people than what they do :) 13:28:03 haha 13:28:10 hi AJaeger :) 13:28:21 mostly I've told Sean that I'd rather we have overarching book owners 13:28:28 +1 13:28:31 sure 13:28:31 that's the direction we're taking the openstack-manuals repo too 13:28:32 Hi everyone, sorry for beeing late. Only just say the note on -doc. 13:28:36 AJaeger: welcome 13:28:40 but what does that 'mean' :) 13:29:02 don't feel the need to answer in this meeting (time is short) 13:29:06 but that's just where I'm thinking 13:29:07 so, you can see why I haven't finished this action item 13:29:08 right 13:29:11 indeed 13:29:19 last action: fifieldt to see design resources for the docs.openstack.org landing page for 1. translation 2. releases 13:29:35 fifieldt_: I talked to Todd Morey last week, he doesn't have a redesign though for us 13:29:38 I believe you made more progress with this than I did annegentle 13:29:41 fifieldt_: he has one for www though 13:29:49 yeah, I grabbed him on skype too ... same result 13:30:03 it's unlikely to happen within the "soon" timeframe :) 13:30:03 so I'll call this in progress, and necessary before Oct 17, but ongoing 13:30:16 #topic Docs Boot Camp - https://wiki.openstack.org/wiki/Docs_Bootcamp_2013 13:30:25 welcome boris-42 13:30:40 annegetnle HI 13:30:42 Boot camp is shaping up, thanks fifieldt_ roadnick and shaunm for the help 13:30:45 :) 13:30:52 Hello, boris-42 13:31:00 any questions about boot camp? roadnick needs to sign up :) 13:31:08 annegentle, i will be there too. 13:31:13 Ha! Yes, I will. :) 13:31:20 I also need to book travel, I realized yesterday 13:31:25 koolhead17: yeah I saw you signed up, woo 13:31:26 Me and Nermina 13:31:28 Could somebody say about what we are speaking now?) 13:31:29 sorry=) 13:31:32 i added some info to the wiki about obtaining/installing Publican 13:31:35 #topic Boot Camp 13:31:41 boris-42: sure, sorry forgot to change the topic 13:31:49 annegentle, thanks to my employer for this :) 13:31:55 im planning a pretty basic overview/tutorial though as it's not really an openstack-manuals tool 13:32:02 we're talking about boot camp, going through https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting 13:32:07 more of a "this is some other docbook stuff that is out there" exercise 13:32:17 sgordon: I think that's helpful 13:32:34 the idea is to share as much info to spread the knowledge 13:33:11 I also need to know if I'm speaking and on what; do you want me to do up a version of the "how to contribute" doc I'm finishing as a presentation? 13:33:11 and get to know each other 13:33:20 annegentle Ah nice 13:33:48 We've got 18 signed up so far with four more expected (like roadnick and Nermina who haven't signed up yet) :) 13:33:56 * slong is envious 13:34:04 we'll record sessions (with speaker's permissions) 13:34:12 annegentle so and todays goal is?) 13:34:15 slong: if your employer would give you the time, we can ask the Foundation for funding for you 13:34:25 boris-42: this is our usual monthly doc team meeting 13:34:29 boris-42: we go through the agenda 13:34:30 seriously? 13:34:35 slong: yes 13:34:40 slong, :) 13:34:45 I wil ask! 13:34:49 :) 13:35:03 fifieldt_: you want to help slong with that? 13:35:05 You do realise I'm in Australia?? 13:35:09 slong: yeah 13:35:09 :) 13:35:14 :) 13:35:25 for Monday's nights outing, what are people interested in? 13:35:29 annegentle, let's smash some email back and forth 13:35:34 fifieldt_: sounds good, thanks 13:35:34 annegentle And as I know I wasn't member of this team, so I am glad to help, but at this moment it is not so clear for me how can I help?) could you explain?) 13:36:11 boris-42: ah you can just listen in then, sorry I thought you were another boris I guess 13:36:46 ideas for Monday: computer museum is close by, go to the Village, go to the Academy of Science, or Exploratorium 13:36:47 annegentle I am Boris Pavlovic from Mirantis 13:36:59 annegentle, me2 :D 13:37:25 Hi, Boris, this is Nick. :) 13:37:30 boris-42, i thought the other Boris from mirantis :) you are close 13:37:35 boris-42: ok, I thought you were from Mirantis. If you work in the Mountain View office you might have ideas for us for an outing 13:38:02 I also like this old book store in old Mountain View. 13:38:15 let me see if I can get some quick ideas from David, he's online 13:38:19 so, book stores? museums? video games? 13:38:25 roadnick: I've been emailing him and Anne Friend 13:38:31 roadnick: with the ideas I'm listing 13:38:33 ah, ok 13:38:45 want to get input 13:38:57 the computer museum is about 2 miles from where we'll be 13:39:02 annegentle: how many are we expecting? 13:39:05 the book store is less than 5 miles 13:39:09 Unfortunately I'm on the other end of the country, so I have no idea. 13:39:10 shaunm: 20+ 13:39:13 i would be +1 on the computer museum but i have never been to san fran 13:39:18 so anywhere is new 13:39:29 sgordon: yeah I've never been to that computer museum but I hear its cool 13:39:40 computer museum sounds fun 13:39:54 ok I'll work on transportation and dinner plans 13:39:57 it does sound fun, but will it be open in the evening? 13:39:57 it's hard to keep a group of more than about a dozen together 13:40:28 but it's probably no big deal if people split into some smaller groups 13:40:55 shaunm: ok that makes sense 13:41:06 annegentle, pleia2 will be our local guide. I remember she did that for us last time in UDS :) 13:41:06 ok any more questions on boot camp? 13:41:14 the museum is closed monday and tuesday 13:41:15 :( 13:41:22 roadnick: NOooo... 13:41:24 bummer 13:41:29 well that's good to find out now :) 13:41:34 koolhead17: I'll reach out to pleia2 13:41:34 yep, bummer 13:41:44 annegentle, i have not received any ack for my participation 13:41:45 we should set up a separate meeting to plan the presos 13:41:51 koolhead17: you're signed up. 13:41:54 koolhead17: there you go :) 13:42:00 cool. thanks :D 13:42:11 roadnick: yeah good idea 13:42:22 roadnick: you want to do that? You have emails for all the speakers right 13:42:37 annegentle, speakers? o.0 13:42:47 ok we already talked about the v3 Compute API doc plan so let's go on to 13:42:53 #topic Bug report, DocImpact state 13:43:12 fifieldt_: you have any comments? 13:43:26 just the stuff from the recent email 13:43:36 progress is being made 13:43:38 Okay. Automation is working great for DocImpact, I have to say! 13:43:43 indeed 13:43:59 noticable in: http://webnumbr.com/untouched-bugs-in-openstack-manuals- 13:44:03 shaunm, how are we doing with the deployment guide 13:44:10 #link https://launchpad.net/openstack-manuals/+milestone/havana 13:44:18 api is basically waiting for the nova v3 things for a lot of the bugs 13:44:39 manuals - managed to tick off a lot of them thanks to openstack-config ref :) 13:44:50 fifieldt_: did the Xen doc bugs get targeted or collected? That would help the numbers 13:44:55 koolhead17: progress is slow at the moment, unfortunately 13:45:02 the blueprint links all the bugs 13:45:14 shaunm, we are meeting next month right? 13:45:15 xen blueprint that is 13:45:16 moment 13:45:28 #link https://blueprints.launchpad.net/openstack-manuals/+spec/redocument-xen 13:45:30 fifieldt_: okay so it gathers them, that's good. 13:46:00 also went through a bunch of blueprints that had been sitting there 13:46:02 and triaged them 13:46:08 so check that out if you get a moment 13:46:28 I did notice that you changed the Admin Manual Modularization from "new" to "discuss" 13:46:49 indeed 13:46:59 well I just tried to make the virtual world reflect reality 13:47:04 We had kind of stalled on that dicussion trying to decide whether to move foreward 13:47:09 forward* 13:47:10 koolhead17: at the boot camp you mean? 13:47:24 Diane knocked out 20 bugs in a few weeks, at least 24 went in with the autodoc patch, are we just not keeping up with coders? 13:47:28 what's your sense of it? 13:47:38 shaunm, ya 13:47:48 yup 13:47:53 cool. 13:47:53 roadnick: yeah I think we are still discussing admin manuals 13:47:59 annegentle, we're doing better than we ever have :) 13:48:07 fifieldt_: for SURE! 13:48:12 fifieldt, did you do work on the config ref blueprint? 13:48:29 slong, I put in a patch for the neutrons 13:48:37 to show the kind of breakdown we were talking about 13:48:42 oh got there are multiple neutrons? 13:48:43 ;p 13:48:45 and tried to look at the filenames 13:48:47 annegentle, do you want me to shoot a mail to the dev list regarding this https://wiki.openstack.org/wiki/Documentation/ProjectDocLeads 13:48:51 roadnick: did you follow the -dev list post for the havana doc plan? 13:48:58 ask the PTL to get us some one from there team 13:49:07 nice, fifieldt 13:49:24 take a look at http://docs.openstack.org/trunk/openstack-config/content/networking-options-reference.html 13:49:32 koolhead17: it probably has to come from me? What do others think? I'm not a huge fan of the idea in the current form, instead I want book owners. But I would like liaisons and some PTLs have identified those. 13:49:34 annegentle: peripherally; I need to go back and review now that I'm more conscious :) 13:49:35 just stub sections 13:49:42 but with a paragraph in there for each block 13:49:44 roadnick: conciousness is good :) 13:49:44 could become something good 13:49:51 but yeah, still got the filename problem 13:50:12 annegentle, sounds good. lets modify it & then reach out to the PTL 13:50:16 koolhead17: add candidate people to the wiki page but I will communicate 13:50:28 annegentle, my concern is it probably needs to be driven via the TC 13:50:41 by the way - we have an icehouse series and milestone 13:50:46 sgordon: I'm on the TC so that's why I should communicate the idea. 13:50:48 (and/or the PTLs obviously) 13:50:51 so feel free to target blueprints into the future :) 13:50:51 right 13:50:53 sgordon: exactly 13:50:55 :) 13:51:09 ok, let's move to open discussion 13:51:16 #topic Open Discussion 13:51:27 annegentle: hey 13:51:29 I think I should have had fifieldt_ do the topic changes 13:51:32 oh well 13:51:35 https://blueprints.launchpad.net/openstack-manuals/+spec/improve-high-availability-support 13:51:36 EmilienM: hey 13:51:36 sorry annegentle 13:51:40 #topic open discussion 13:51:42 I want to know who's going to HK? 13:51:48 o/ 13:51:49 * fifieldt_ is :D 13:52:07 I'd like to call attention to this review, for slong and sgordon: https://review.openstack.org/#/c/41623/ :) 13:52:12 fifieldt_, :P 13:52:15 roadnick and I still work on https://blueprints.launchpad.net/openstack-manuals/+spec/improve-high-availability-support 13:52:16 NOT me 13:52:25 (for HK, that is) 13:52:30 annegentle, i am actually just reworking our travel request 13:52:31 awww man 13:52:50 so at the moment cant really confirm 13:53:10 right on, fifieldt! 13:53:38 sgordon: cool 13:53:58 if it helps with travel plans, it looks like docs will be afternoon Tues. 13:54:06 four slots, same as Portland 13:54:07 roadnick: do you want to talk about https://blueprints.launchpad.net/openstack-manuals/+spec/improve-high-availability-support ? 13:54:15 fifieldt, I have no problems with the current state. What caused me mild frustration was the patch going in since it touched so many files. 13:54:25 I am still noodling on whether to get rid of Admin Guides 13:54:31 I've been doing some Google Analytics work. 13:54:45 ooh :D 13:54:45 annegentle, i think admin guide is needed :) 13:54:49 For sure the analytics back up the idea that we CAN go to continuous publishing for many many guides. 13:55:00 koolhead17: there will be a new Admin User Guide. 13:55:11 koolhead17: so it's possible to get rid of the Compute Admin Manual for example. 13:55:18 annegentle, ooh okey 13:55:28 koolhead17: and possibly the Object Storage Admin guide, by moving the config info out, such as S3 13:55:35 I think we could do a lot of purging safely 13:55:42 so I wanted to give a heads up that's a possiblity 13:56:03 annegentle, will talk in few weeks on the same. 13:56:06 I still don't know where to put Block Storage other than in the Config Guide (since it's mostly about configuring different storage backends) 13:56:16 and the Networking Admin Guide, just makes me worry. 13:56:28 annegentle, i have verbal approval for at least one of us im just updating the costs 13:56:30 shaunm: I also worry a lot about the install guide 13:56:34 plan is for attendance at all 4 days 13:56:37 a worried annegentle is not a good thing :( 13:56:38 sgordon, coool 13:56:42 sgordon: yeah if you can get there go all the time! :) 13:56:48 fifieldt_: oh it's all the time :) 13:56:53 fifieldt_, :) 13:56:55 emilienm: since I've been out, why don't you take that for today; you have a better handle right now. 13:57:10 ok 13:57:20 we still have some work to do. 13:57:28 annegentle: well, I do too 13:57:28 what I would like first, is to finish main sections 13:57:44 shaunm: oh yes not saying otherwise :) Just sharing concerns 13:57:44 and then fix subsections with more precisions 13:58:03 I also wanted to say something about review policies -- 13:58:05 #link http://docs.openstack.org/trunk/openstack-ha/content/ha-using-active-active.html 13:58:16 I know it has been hard to get stuff merged lately with all the markup changes, sorry about that. 13:58:20 but we're getting into a good state 13:58:22 annegentle: next release is in october? 13:58:27 for welcoming all the contributors :) 13:58:34 shaunm: Oct 17 is go live 13:58:43 that's feeling less and less like plenty of time 13:58:45 shaunm: feature freeze is coming up a month sooner 13:58:48 shaunm: yes 13:59:06 #link https://wiki.openstack.org/wiki/Havana_Release_Schedule 13:59:19 annashen, regarding markup changes: Let's keep in mind to record our policies on the conventions page. 13:59:21 I expect we'll see lots of doc interest come Setp. 5th 13:59:30 AJaeger: yes, good idea. 14:00:00 * AJaeger was surprised what he learned from (great!) reviews that wasn't really codified and where I had to guess what it means... 14:00:01 So here's a draft policy - get at least one +2 before merging when 2 or more files are changed, but if it's small changes, a core can just push it through. 14:00:25 AJaeger: yeah I was thinking the same thing about new people wondering "well what do I have to do to get this merged?" :) 14:00:38 fifieldt_: can you record an action for me to codify our reviewing policies 14:00:49 and we're on the hour, again I apologize for being late 14:00:51 #action annegentle codify our reviewing policies 14:01:01 annegentle, or: If it touches more than one book? 14:01:05 fifieldt_: oh anyone can do actions :) sorry 14:01:15 no worries :) 14:01:16 AJaeger: yeah if it touches more than one book definitely want 2 cores to look 14:01:41 AJaeger: but if I want to get patches moving I'll +2 on my own if I'm confident 14:01:49 AJaeger: so that's sort of out of policy I suppose :) 14:02:11 AJaeger: though I do want other cores to have that same confidence and push 14:02:33 AJaeger: we're a small enough team that we can move things through as needed without waiting for others 14:02:34 I take it everyone has also seen 14:02:35 #link http://russellbryant.net/openstack-stats/docs-openreviews.html 14:02:40 annegentle, let's not be too strict... 14:02:43 sgordon: fifieldt_: does that sound about right? 14:02:54 aye, annegentle 14:02:57 fifieldt_: ohhh that's handy 14:03:04 Longest waiting reviews (based on latest revision): 14:03:05 74 days, 17 hours, 33 minutes https://review.openstack.org/31119 (Add os-instance_usage_log_audit extension) 14:03:06 :D 14:03:20 fifieldt_: LOL wow 14:03:34 the page helps me remember to check not just openstack-manuals 14:03:35 Ok, let's end it and always feel free to talk on openstack-doc all! 14:03:38 but also places like operations-guide 14:03:38 Gotta get a kiddo to the docs 14:03:41 annegentle, i am a little hesitant at the moment but yes with time 14:03:41 cool 14:03:44 I might sleep instead 14:03:48 sgordon: sure 14:03:56 i had one more thing actually 14:04:00 sgordon: sure 14:04:00 ya? 14:04:08 Anybody wants to ask Diane what to do with 31119? 14:04:11 i was wondering if people think meeting monthly is enough, or perhaps we could move to fortnightly 14:04:13 just a though 14:04:24 AJaeger, it needs samples 14:04:28 which may not be in the code 14:04:30 my feeling is that touching base like this 6 times a release may be underdoing it 14:04:34 just my 2c though 14:04:35 sgordon: hehe I had to look up forthnightly 14:04:38 wondering what others think 14:04:44 sgordon: yeah I'm with you 14:04:50 +1 14:04:54 sorry, despite my geographic disposition i still speak 'strayan 14:04:55 +1 14:04:57 We can go to weekly even 14:05:10 hehe 14:05:12 weekly? Every other? twice a month? 14:05:15 =1 14:05:20 +1 for fortnightly 14:05:21 i would move to every other to start with imo 14:05:27 sgordon: wanna propose it to the mailing list? 14:05:30 sure 14:05:42 #action sgordon propose more often meetings on -docs Mailing List 14:05:50 I agree 14:05:59 sgordon: yeah every other for starters sounds good 14:06:05 i think the fact the last couple we have run the full hour and then some 14:06:12 is an indication we could meet more often :) 14:06:17 heh yeah 14:06:19 sgordon, thanks for reminding us about meetup today :) 14:06:22 ok let's end it 14:06:25 yup 14:06:28 yay 14:06:29 thanks all! 14:06:39 #endmeeting Doc Team Meeting