14:04:39 #startmeeting docteam 14:04:39 Meeting started Wed Jul 23 14:04:39 2014 UTC and is due to finish in 60 minutes. The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:04:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:04:41 hey! 14:04:44 The meeting name has been set to 'docteam' 14:04:45 Agenda is here: 14:04:46 Hey, annegentle 14:04:47 #link https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting 14:05:00 Let's see, action items from last meeting. It has been a while. 14:05:02 i noticed the date wasnt updated on the wiki 14:05:24 we didn't have a meeting last two weeks ago 14:05:26 so we already reviewed 14:05:35 ah 14:05:39 #topic Action items from last meeting 14:05:41 #info none 14:06:03 well I'll check to see if there were any in apac 14:06:43 nope nothing 14:06:59 #topic Architecture and Design Guide progress 14:07:33 #info It's Alive! The Architecture Design Guide has been merged 14:07:35 #link http://docs.openstack.org/arch-design/content/ 14:07:37 yay 14:07:47 still needs some docbook fixerations? 14:07:54 Lots to do still, like get the glossary items integrated into common, make sure some tables came over 14:07:59 Sam-I-Am: if you see something say something 14:08:08 Sam-I-Am: it won't build unless it's docbook 14:08:28 I'm working on uploading print-ready PDF to lulu.com so we can order printed copies 14:08:29 well, yeah. thinking more like things that just didnt port well. 14:08:32 for the curious, it is 178 pages 14:08:37 Sam-I-Am: that's what took last week 14:09:27 I'll make sure the tables are in before the lulu upload 14:09:36 anything else that needs work, log a doc bug 14:09:50 #info Congrats to the writers! They worked hard and it shows. 14:10:08 I'll send 2 printed copies to the authors 14:10:09 thats a lot of writing in a week 14:10:19 I'll ask for their mailing addresses separately 14:10:24 wish we could get that around the network guide 14:10:25 The scary thing is that the writing was only 2 days. 14:10:43 ha, nice. 14:10:45 the rest was editing and polishing. 14:10:55 also thanks to nickchase for help getting it building! And for proofing the cover 14:10:59 Maybe the next sprint should be on Networking, what do you think, Anne? 14:11:02 I should have the cover edits back today 14:11:03 YW. 14:11:09 nickchase: there's a swarm for networking 14:11:17 its a 1-day thing 14:11:18 nickchase: but I really really don't want another sprint this year 14:11:33 nickchase: and the facilitation costs went way up (like tripled) so I don't know if we'll get funding again for a while 14:11:37 wow 14:11:53 might have had something to do with Adam bringing 2 people instead of 1 14:11:56 nickchase: so yes let's not have another sprint until at least fall 2015 and even then it should be on content we already have :) 14:11:58 he was training Faith. 14:11:59 nickchase: well 14:12:06 moo 14:12:12 nickchase: yes I'm aware of that :) 14:12:15 Yah know, I wonder if we could do one ourselves. 14:12:27 I mean, it's not rocket science. 14:12:39 when is the networking swarm aimed at? 14:12:41 not this year, I know 14:12:47 Just thinking out loud. 14:12:55 nickchase: it's.... facilitation is a special talent that really needs to be an outsider, but I could be swayed otherwise 14:13:01 regXboi: august, in australia 14:13:07 nickchase: there is evidence that sprint books don't bring in maintainers 14:13:11 nickchase: we've seen it 14:13:23 docs dont bring in maintainers :/ 14:13:27 Sam-I-Am: well... that's not going to be travel, but will there be a virtual swarm? 14:13:27 nickchase: so I'd love to discuss further but I have pretty strong opinions on the sprints 14:13:35 annegentle: I completely get that; that's why they need to be good tos tart with. 14:13:37 regXboi: i dont know how thats going to work 14:13:46 nickchase: yah 14:14:00 regXboi: hey you like regex? :) 14:14:04 annegentle: we can talk about it another time, didn't mean to monopolize. :) 14:14:11 Let's talk about the networking guide, seems like a good segue 14:14:16 nickchase: sure no prob! 14:14:23 annegentle: it's an old handle from days of writing production OSS in perl :) 14:14:36 fits with our next topic anyway 14:14:37 #topic Review docs-specs: shared glossary and HOT template chapter in user guide 14:14:49 I'll take them one at a time but start with the networking one 14:15:10 Sam-I-Am, phil__ (that's phil hopkins) are working on an outline 14:15:17 Sam-I-Am: I'd be interested in the day/times to see if I could virtually drop in and help out.... but in US CDT, it might get tricky :( 14:15:20 Lana (loquacities) is organizing the swarm 14:15:28 regXboi: i'm in us/cdt too 14:15:34 so, regXboi you could certainly help in some capacity 14:15:34 we'll figure it out 14:15:44 Sam-I-Am: where's that outline? Did you decide whether to move it into a spec? 14:15:49 regXboi: just work a swing swift 14:15:54 sounds good - I've got some definite opinions on the networking specs :) 14:16:10 regXboi: so these are docs-specs we're discussing now 14:16:17 annegentle: i didn't decide on that yet. kind of underwater. 14:16:25 annegentle: yes - s/specs/doc-specs/ 14:16:41 #link https://blueprints.launchpad.net/openstack-manuals/+spec/create-networking-guide 14:16:54 #link https://wiki.openstack.org/wiki/NetworkingGuide/TOC 14:17:01 annegentle: i like the idea of the doc spec 14:17:13 That ^^ is the TOC they're working on, that can be then made into a doc spec in the docs-spec repo 14:17:26 The swarm aims to fill in some of that 14:17:35 but a spec would be nice to state the problem statement and solution clearly 14:17:45 annegentle: you know, I like this - there are a bunch of neutron doc bugs that I've looked at that could concievably fit in here 14:18:06 regXboi: yep, absolutely 14:18:22 It'd be great to fit known doc bugs into the spec too, hm. 14:18:30 Ok, let's also talk about the two in the review queue 14:18:44 #link https://blueprints.launchpad.net/openstack-manuals/+spec/common-glossary-setup 14:19:04 #link https://review.openstack.org/#/c/104781/ 14:19:05 well that's all goodness 14:19:59 I like where the common glossary one is going 14:20:04 I think I'm going to +1 the git submodule idea 14:20:10 Ok, the other one is the HOT template chapter in the user guide 14:20:15 regXboi: Gerrit doesn't support submodules 14:20:26 yeah - that's the rub :( 14:20:38 #link https://blueprints.launchpad.net/openstack-manuals/+spec/heat-templates 14:20:56 #link https://wiki.openstack.org/wiki/Documentation/blueprints/heat-templates 14:20:57 and 14:21:07 #link https://review.openstack.org/#/c/108133/ 14:21:37 I'll work on your comments later today annegentle 14:21:48 gpocentek: I had wondered on the review if the automation of the reference info is in the scope of this blueprint mainly... thanks a bunch for writing it up 14:22:19 annegentle: this bp could be some kind of master bp 14:22:24 also, just as a general note, the specs aren't published anywhere yet, but we want them all to go to specs.openstack.org 14:22:33 that way, they're not "docs" 14:22:46 annegentle: I'll do a readthrough of both gerrits today and add some comments 14:23:21 regXboi: thanks! 14:23:42 gpocentek: I really like how you're thinking about and planning for advanced topics, they're really needed 14:24:10 I haven't had any further movement on the redesign or python client docs 14:24:19 so that's it for blueprints we know we're doing, any questions? 14:24:32 know we're doing specs for 14:24:35 I mean 14:24:44 there's plenty approved without assignees 14:24:56 need more warm bodies :) 14:24:59 oh and please do review Ildiko's latest work on adding ceilometer/Telemetry to the admin guide 14:25:01 annegentle: were you going to take a spin at fit known doc bugs into the net guide spec? 14:25:02 always a problem with docs 14:25:05 annegentle: should we start migrating all the approved LS blueprints? 14:25:09 s/LS/LP/ 14:25:16 regXboi: do you have time to? You sound like you know them well :) 14:25:28 annegentle: I was taking the action :) 14:25:38 Sam-I-Am: we had 195 contributors last time, I don't want to hear negativity when we're growing based on the data, please 14:25:47 regXboi: sweet! 14:26:09 #action regXboi to add list of existing neutron doc bugs to the blueprint wiki page 14:26:39 Ok, the next topic is a public service announcement :) 14:26:41 #topic Summit proposals due 7/28/14 14:26:56 These are the proposals for the business side of the summit, not for the doc track itself 14:27:23 I'm thinking about data mining support cases around app devs 14:27:41 and slicing it with docs GA data 14:27:51 I know the Arch Design team is proposing a talk 14:27:57 anyone else with ideas? 14:28:37 annegentle: I'd think the data mining sprinkled with real case issues should work 14:28:48 I still haven't implemented the "template" talk decisions from Atlanta. 14:28:49 regXboi: yeah 14:28:57 I've come to the docs side based on the delta between docs and the SC :) 14:28:58 nickchase: oo remind me 14:29:06 nickchase: oh right the template for commit messages? 14:29:14 regXboi: nice! 14:29:51 annegentle: yes 14:30:13 Need to get with you to figure out exactly what I need to do, as in what format file and who to send it to 14:30:23 speaking of not-done-things, i'm still trying to get the review guide up. 14:30:32 nickchase: yeah I think it's in the -infra area 14:31:09 Sam-I-Am: awesome, I heard Andreas had a start at the revising style guide? But not sure. Need to follow up. 14:31:42 annegentle: it was a dependency of re-organizing the conventions/style guide... so thats why i think it kind of went forgotten. but its very important. 14:32:12 annegentle: I figured. I'll get with you offline and we'll push it forward 14:32:17 so, a process question comes to mind... does the doc team have links to cores in the various projects? 14:32:24 Sam-I-Am: yeah and it's possible Andreas has a start at the dependency, let's check wtih him 14:32:28 too bad he's not here 14:32:32 regXboi: yes, let me find a link 14:32:57 #link https://wiki.openstack.org/wiki/Documentation/ProjectDocLeads 14:33:05 regXboi: so if you get stuck, ask any one of those listed 14:33:15 annegentle: thanks - I'm thinking ahead in cases where a doc bug actually involves changing project code 14:33:16 regXboi: Edgar Magana especially for networking 14:33:24 regXboi: yep, precisely 14:33:30 Edgar and I have already been consulting :) 14:33:52 regXboi: good! 14:34:08 Edgar is coming to the ops meetup and we were gonna talk docs there, are you coming to that? 14:34:09 I don't know if folks have seen this: 14:34:22 annegentle: no travel budget here :( 14:34:27 regXboi: ah ok 14:34:28 I can only drop in virtually 14:34:38 #link https://wiki.openstack.org/wiki/Network/Meetings#Docs_.28emagana.29 14:34:43 Sam-I-Am: are you coming to the ops meetup? 14:34:52 regXboi: NICE. 14:35:03 I put in a bunch of initial comments on neutron doc bugs as part of the neutron mid-cycle sprint 14:35:14 does anyone think we need a docs proposal for the summit? I think loquacities is working on one. 14:35:35 annegentle: i thought so 14:35:35 regXboi: cool, I edited the etherpad with deeper links 14:35:47 I think we always need a docs proposal, just to remind people we exist 14:35:56 But honestly, nothing's coming to me. 14:36:03 Sam-I-Am: ok cool, we'll definitely work with Edgar there 14:36:10 do we have a troubleshooting guide? 14:36:16 nickchase: okay good to know. I'd hate to have a bunch when we could get one approved, ya know? 14:36:21 that's the obvious thing to ask for an ops summit :) 14:36:24 regXboi: no, troubleshooting chapters 14:36:34 ok... *should* we have a troubleshooting guide ;) 14:37:05 regXboi: you'll find I get a lot of requests for new "books" and usually tell people to write chapters, BUT, after networking guide troubleshooting guide COULD be a candidate. 14:37:36 annegentle: understood - my thought is that if I'm going to do a proposal for an ops session, it should be ops related 14:37:42 and troubleshooting is the obvious candidate 14:37:54 especially as I think (if done well) it goes way beyond a chapter 14:38:04 regXboi: oh I see, yeah, have you added it to the ops meetup etherpad? 14:38:18 annegentle: no - just thinking out loud here 14:38:24 #link https://etherpad.openstack.org/p/SAT-ops-meetup 14:38:26 great idea 14:38:58 somebody is beating me to it :) 14:39:11 heh 14:39:14 "Would a troubleshooting guide be a good "next" deliverable after ML2 is properly documented?" 14:39:19 works for me 14:39:23 because honestly ml2 isn't properly documented :) 14:39:35 ok 14:39:36 um: I'd argue neutron isn't properly documented :) 14:39:37 #topic Doc tools updates 14:39:49 regXboi: yes I just put things into buckets :) 14:39:56 +1 14:40:10 I don't have a lot to report on doc tools, just keep an eye on the mailing list about the training guide xi:includes 14:40:17 any training teammates here? 14:40:22 maybe that's the big thing: we need to get some help for Sam-I-Am and Phil 14:40:31 annegentle: is there any complaints if (as a newbie) I take a pass through the doc tools wiki and make it more clear? 14:40:47 regXboi: I'd be fine with that, which page? 14:41:02 annegentle: I was going to start at the beginning and ... 14:41:17 i.e. walk through the set up steps and make notes where things do and don't work 14:41:58 regXboi: sure 14:42:05 regXboi: do i know you from anywhere? 14:42:32 Sam-I-Am: not sure :) - I'm a complete ludite when it comes to thinks like linked in, etc. :) 14:42:44 but I do have an RFC or three to my name 14:42:47 regXboi: ever get to the summits? 14:42:56 Oh I'll just open it up 14:43:01 #topic Open discussion 14:43:15 regXboi: not new to neutron, but new to docs 14:43:16 ? 14:43:18 annegentle: not to date - may be in Paris - it depends on presentation proposals, etc. 14:43:37 Sam-I-Am: (a) sorta (b) not really 14:43:57 * regXboi has about 25 years in networking and has worn *many* hats in that time :) 14:44:17 cool. most people who work on openstack don't have much networking background. 14:44:23 nice 14:44:27 more networking docs people = yay 14:44:45 thanks regXboi! (love the handle still, hahaha) 14:44:53 I still need a better casual friday nick 14:44:56 yes - I came here because the existing neutron docs don't quite cover what RTSC tells you :) 14:45:19 regXboi: we should chat a bit in #openstack-doc 14:45:27 i'll introduce you to phil 14:45:29 RTSC = read the source code? 14:45:34 Sam-I-Am: I'll add it to my channels I drop in on 14:45:38 annegentle: yes 14:45:49 ok, I'm such a good acronym translator :) 14:45:52 regXboi: also #openstack is good if you like helping people. lots of networking problems. 14:46:01 alrightly let's get back 15 mins and move it over to #openstack-doc 14:46:05 #endmeeting