14:01:41 #startmeeting docteam 14:01:42 Meeting started Wed Nov 12 14:01:41 2014 UTC and is due to finish in 60 minutes. The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:45 The meeting name has been set to 'docteam' 14:01:47 morning Sam-I-Am gpocentek! 14:01:59 Ok, seems like forever to look up the past action items 14:02:19 ha. 14:02:19 * annegentle annegentle to pull upgrade info from ops guide 14:02:26 o/ 14:02:26 my action is done and now undone. Double done. 14:02:30 he rromans 14:02:32 ;) 14:02:35 er that's a hey rromans 14:02:43 hiya :) 14:02:46 * annegentle annegentle to add a soft-freeze declaration to this week's What's Up Doc 14:02:49 Done 14:02:56 * annegentle annegentle to ask Gauvain when he wants to publish the HOT guides 14:03:07 done, it's part of the user guide now 14:03:16 that's all 14:03:16 you did ask me and it's published now 14:03:18 er 14:03:20 I should have 14:03:26 #topic action items from last week 14:03:28 ok 14:03:44 action items from last time done 14:03:50 #topic Summit wrap up 14:04:01 I sent a What's Up Doc for the Summmit 14:04:08 tooooo mannny mmmms 14:04:21 nice writeup, thanks annegentle 14:04:28 yes, thanks 14:04:34 thanks 14:04:36 #link http://lists.openstack.org/pipermail/openstack-docs/2014-November/005432.html 14:04:44 I think I wrote every night I was there. 14:05:20 any questions? I do have plenty of action items from the summit that I'm working through. 14:05:33 #action: annegentle set up bug triaging days 14:05:42 #action: annegentle set up video meetups 14:06:08 no questions anymore ;) 14:06:25 :) 14:07:22 I think I need to communicate the driver doc decision once your spec is ready for review, AJaeger_ 14:07:28 or you can start a thread 14:07:45 and I'll circle back on the design in another meeting topic 14:07:56 #topic Networking Guide latest 14:07:58 annegentle: I wrote already an email to all contributors to the config reference driver section that I could identitfy 14:08:04 AJaeger_: oh that's great 14:08:05 mmm, networking guide 14:08:16 i built a dvr environment and found it was broken 14:08:20 So Phil_h sent a draft to us yesterday (did it go to the list?) 14:08:22 #link https://review.openstack.org/#/c/133580 14:08:23 ahh 14:08:27 I saw it 14:08:32 haven't read it yet 14:08:35 but I saw it 14:08:36 me neither 14:08:39 gotta do that 14:08:41 and I spent some time with Elke on the phone before the summit 14:08:47 i spent last night testing that patch... and it works 14:08:54 awesome Sam-I-Am 14:08:55 so now we have a reason to document dvr again 14:09:01 good deal 14:09:04 And I spent some time with Elke since then 14:09:08 phil supposedly has an l3ha environment working 14:09:14 do they need to backport that 133580? 14:09:21 only if 133580 ends in Juno branch 14:09:23 nickchase: cool is she all set? 14:09:26 AJaeger_: right 14:09:29 I think we're almost there on getting her patching. Theoretically she has content. 14:09:33 She's almost set. 14:09:35 i hope it makes 2014.2.2? 14:09:43 nickchase: ok great 14:09:51 Sam-I-Am: okay yeah sure hope so. 14:09:56 I exported a working OVA for her to use while she works with Cisco to find out why her machine only gives her 32 bit options. 14:09:58 nickchase: i'll be looking through phil's stuff and seeing where the holes are (particularly diagrams) 14:10:03 great 14:10:04 so it's kind of good we pushed on install rather than networks at the end huh? 14:10:14 definitely. 14:10:15 Sam-I-Am: great 14:10:22 l3ha is sort of broken too :/ 14:10:41 nickchase: ok I was suspicious of the 32 v 64 myself 14:10:53 Sam-I-Am: huh. should we not doc it? 14:11:01 annegentle: we should 14:11:13 its bugs dont seem nearly as bad so far as dvr (which didnt work at all) 14:11:19 okay 14:11:33 funny how a one line patch fixed it 14:11:41 Sam-I-Am: seems we should change our mission from Docs to QA and docs ;/ 14:11:44 anyway, we should be getting some scenarios soon 14:11:57 general neutron, dvr, and l3ha 14:12:14 #info Networking guide in progress: dvr needs a code patch, layer 3 HA in testing 14:12:15 collins is supposedly working on a provider network scenario, but that was before the summit 14:12:28 well, he should be back now. 14:12:29 that gives us 4 scenarios to document 14:12:38 Sam-I-Am: would that change knowing our new driver decision? 14:12:39 next meeting is Friday, I'll see if he can have it before then. 14:12:42 plus the introductory stuff 14:12:55 as in, would we document a provider scenario in our docs, or just point to whatever Sean writes? 14:13:15 provider as in... neutron only provides bare pipes to VMs 14:13:24 all of the meat is handled by some upstream hardware 14:13:34 Sam-I-Am: right, vendor hardware right? 14:13:39 or virtual? 14:13:41 yeah, but we dont talk about the hardware 14:13:58 just trying to scope based on our current thinking 14:14:02 all the scenario covers is how to disable all of the neutron services except the L2 pipe 14:14:10 no dhcp, no routing, etc. 14:14:19 ok, so ML2? or no? 14:14:20 there's no third party plugins involved 14:14:39 i think he's still using ML2 14:14:44 since it talks to ovs 14:14:45 what's that equivalent to? Flat? 14:14:54 I can't spell 14:15:11 so it would be an ML2 using OVS, that's in scope 14:15:39 he's using vlan types. however, flat, vlan, and tunnel types can all have neutron services on top of them... or nothing. the nothing option seems to appeal to lots of people who dont want to deal with neutron performance and reliability issues. 14:16:13 the downside is less 'cloudy' capabilities for tenants, but not everyone wants those features. 14:16:19 I like "nothing" heh 14:16:26 yeah I think there's demand for that 14:16:28 ok 14:16:35 quite 14:16:41 see it often in #openstack 14:16:44 #info one more scenario coming, basically ML2 with OVS / vlan 14:16:50 also the idea of pulling networks directly to compute nodes 14:16:52 ^^ good enough for the minutes? 14:16:58 annegentle: yep 14:17:12 'provider network scenario' 14:17:24 yeah 14:17:28 #undo 14:17:29 Removing item from minutes: 14:17:45 #info one more provider network scenario coming, basically ML2 with OVS / vlan 14:17:46 hmm that looks like a bug 14:17:49 Ok moving on 14:17:56 #topic Install guide status 14:18:03 ah yes... about that. 14:18:04 Swift stuff is in! 14:18:19 yeah, so i took a stab at swift because i havent really looked at it thoroughly 14:18:23 lots of upstream package problems 14:18:43 i found a lot of issues, but intended to handle them a few lines at a time 14:18:54 yeah I think it's an improvement for sure 14:18:57 then it got late, alcohol was involved, things got blurry, and i woke up in a ditch next to a huge patch 14:18:59 heh 14:19:16 it's in tho 14:19:17 still not exactly sure what happened 14:19:22 so huge patches can even get in summit week. 14:19:26 we're pretty weird that way 14:19:29 Sam-I-Am: A miracle ;) 14:19:36 i was... totally shocked at the approval turnaround. 14:20:00 anyway, as promised, i'm working on revamping the example architecture diagrams to cover the cinder and swift nodes now. 14:20:06 cool 14:20:06 no longer shall those parts be different 14:20:13 i have 6-8 diagrams almost done 14:20:19 #info Object Storage updates complete 14:20:39 i'm having trouble finding a maintainer for the swift packages on ubuntu 14:20:47 its like... they're orphaned. 14:20:50 #info Sam-I-Am working on new architecture diagrams to include swift and cinder nodes 14:21:11 Sam-I-Am: yeah no one uses those packages they make their own so it's classic tragedy of the commons I guess 14:21:21 remaining items to test/patch include ceilometer, trove, and sahara (which has no packages?) 14:21:24 Anything else on install guide 14:21:48 i think we're good for now. still backporting everything since we ran out of time for juno. 14:22:17 try to avoid content shuffling patches unless you backport them too so we dont get a bunch of conflicts/rebase 14:22:28 okay, yes. 14:22:35 andreas' backport script makes it easy 14:22:39 right now the content is the same 14:22:44 #info Try to avoid moving install guide content around unless you're also willing to backport 14:23:00 ok, onward 14:23:01 thats it from me! 14:23:05 #topic Website design status 14:23:07 Sam-I-Am: just tell us once you're ready to do massive changes 14:23:13 annegentle: you're too fast for me ;) 14:23:18 :) sowwy 14:23:33 I sent Wes, the designer, the input from Friday's session, and he already turned the chagnes around. WOO 14:23:36 Sam-I-Am: I want to update for SLE 12 and openSUSE 13.2 before Kilo but can wait another month or two... 14:23:51 annegentle: no worries - I got my two lines out ;) 14:23:57 AJaeger_: i think we'll be good by then 14:23:59 #link http://openstack-homepage.bitballoon.com/docs 14:24:02 Main page 14:24:17 - increased size of icons 14:24:26 - increased size of arrows 14:24:43 looks pretty good 14:24:44 - indicates that indeed, the characters picture will rotate through 14:24:53 - updated placeholder text for search 14:25:08 - uses "Get OpenStack" instead of "Get Started" as label 14:25:14 size of text is not increased 14:25:34 AJaeger_: he said "Increased the size of the font and converted the size to em" 14:25:47 which browser? I can report it back. It is larger to me, but not by much 14:25:57 mmh, doesn't seem to be different for my firefox 33 or so 14:25:58 the font inside the blue box on the left 'release' is smallish 14:25:59 - changed the icon 14:26:16 here's his response for the footer 14:26:18 annegentle: then the page is not updated 14:26:23 is still there for me 14:26:45 AJaeger_: hit hard refresh. I see gears now 14:27:08 that's it for landing page 14:27:24 AJaeger_: did refresh get it? 14:27:27 hmm, not working for me - strange ;( 14:27:34 annegentle: still the same for me as well 14:27:45 #link http://openstack-homepage.bitballoon.com/docs 14:27:54 weirrrd. 14:28:00 i see the gears 14:28:10 wonder if it's not in europe yet? 14:28:16 hrmity. I'll ask Wes. 14:28:32 annegentle: bits took the slow boat 14:28:44 heh 14:29:00 ok what about this one? 14:29:02 might be that the bits are swimming ;) 14:29:02 #link http://openstack-homepage.bitballoon.com/docs/book 14:29:14 we have some questions to answer 14:29:31 for the mouseover for glossary 14:29:41 do we want popover or footnote-style? 14:30:00 i like mouseovers since they dont consume space 14:30:04 I'm for popover myself 14:30:05 me too 14:30:11 and scan read is easier 14:30:35 Redhat person suggested the foot notes, sorry can't recall name now! 14:31:00 I like the current solution of popover with ability to turn off highlighting 14:31:21 - RSS icon is now orange 14:31:34 that makes for a bit of a "rainbow" effect so he wasn't sure if that was good or bad 14:31:41 is there any way to determine which side of the word/phrase the glossdef pops up? 14:31:50 also I would prefer that suggest edits _not_ be iconized 14:32:00 things closer to the right edge get squished 14:32:19 Sam-I-Am: he's aware of the problem and says "we can work in an option to detect position of the popover and have it displayed where it's always visible" 14:32:29 cool 14:32:47 rainbow effect? 14:33:00 "We can easily color the rss icon and the download icon. My only worry was that this corner will look like a rainbow :) I colored both icons for you to review. Let me know which direction you want to go with." 14:33:02 * AJaeger_ likes rainbows ;) 14:33:03 originally they were mostly grey 14:33:11 I like the colors except when disabled, make it grey 14:33:22 kind of surprised we dont have a "shades of color X" scheme like rackspace does 14:33:27 like... shades of blue or red. 14:33:57 it's mostly navy and greys here 14:33:59 but yeah 14:34:08 we could limit the color choices 14:34:13 it's just that RSS is classically orange 14:34:26 who says we're classy? 14:34:30 oh wait you said classically :) 14:34:44 :) 14:34:52 he said " Is the suggestion to move all of the action icons (rss, print, definitions, and report bug) to the section below “suggest edits”? Any other input would be great!" 14:35:09 I think the placement is fine but someone did have a different suggestion in the etherpad 14:35:13 not sure who tho 14:35:41 I guess I wanted suggest edits to be different, not lost in the iconic 14:35:56 what does 'suggest edits' do? 14:36:00 since we can really stand out, not many other doc projects will have it 14:36:05 so for now it'll go to how to contribute 14:36:16 but once Gerrit is updated with a web-based interface, it can go to gerrit 14:36:59 one other change to note 14:37:01 - added a section to show release info next to the date, top and bottom. 14:37:06 I like that change 14:37:21 thats useful. people will still miss it :/ 14:37:32 ok so we'll have to decide about the icons - coloring placement and whether suggest edits is iconic 14:37:34 make it 36pt font and tag and they'll miss it 14:37:40 marquee 14:37:56 #action annegentle to follow up with Wes 14:38:17 #ink http://openstack-homepage.bitballoon.com/docs/search 14:38:17 not sure what sort of icon you would use to suggest edits 14:38:18 last one 14:38:38 Sam-I-Am: heh, a piece of tape as a "patch" 14:38:46 Let's see 14:38:55 - added date to Icehouse in the dropdown 14:38:59 and 14:39:01 annegentle: should search results contain the release if it pertains to the document? 14:39:08 - arrow next to the dropdown sends user to the landing page 14:39:23 Sam-I-Am: I think that's customizable in the Google Custom Search Engine. so yep. 14:39:37 - added a tooltip to the arrow that goes back to landing page 14:39:39 seems like something useful 14:39:51 that's all the changes on the search page. our other suggestions have to be handled in Google CSE 14:39:57 oh yeah 14:40:08 "We could replace the arrow with a home icon" <--- what do you think? 14:40:18 +1 14:40:37 I am still less than thrilled by the size of the arrow icons, because I am getting old and my vision is getting worse. 14:40:46 (also, hi, I’m late) 14:40:50 KLevenstein: I thnk they're a little small to me too 14:40:54 Hi KLevenstein ! 14:40:57 KLevenstein: and my eyesite sucks :) 14:40:57 they are small 14:41:02 as is the font next to it 14:41:04 I'll give Wes that input too 14:41:42 one other question, how many more people should we show it to? Devs? Ops? 14:41:57 I hate to slow it down, really just want to put it out there :) 14:41:59 Ops maybe? 14:42:04 dont ask devs, it'll end up like neutron :) 14:42:27 KLevenstein: we can probably find a few eyes inhouse, let's find someone Friday 14:42:35 cool cool 14:42:46 anything else on the design? Questions? I don't have a timeline but wow he turned that around fast. 14:42:53 annegentle: this might leat to lots of bike shedding, just show it too a few. 14:43:03 AJaeger_: my thinking also. 14:43:15 "the bike shed is red"! 14:43:18 :) 14:43:23 #topic HOT Template Guide latest 14:43:25 and if you present it to a large group, don't ask for input, just say this is it - if something is really bad, they'll speak up ;) 14:43:36 yeah agreed. so much agreed. :) 14:43:45 annegentle: will there be a period where its' up and working as something like beta.openstack.org ? 14:43:46 So the HOT Template Guide is within the User Guide 14:43:52 so we can test it with more real content 14:43:58 Sam-I-Am: we have to get it into RST 14:44:18 Sam-I-Am: so yeah that'll be a next interim, real content, real HTML/CSS/build parts 14:44:23 k 14:44:33 annegentle: do we have people to include the new design in RST? 14:44:34 Sam-I-Am: a little worried about that part, taking a long time, but we'll see 14:45:04 gpocentek: the designers have little knowledge of sphinx. so we may have to help a lot or a little. I'll clarify. 14:45:17 gpocentek: that is the tough step 14:45:23 well we can test on the HOT guide :) 14:46:06 gpocentek: yep, I want the user guide to go first 14:46:22 gpocentek: and yeah, the hot guide is rst 14:46:24 so yep 14:46:53 let's see 14:47:03 API docs and Doc tools 14:47:10 #topic API docs latest 14:47:24 I have a few specs patches still in review. Only Keystone has merged. 14:47:27 I'm working on neutron now. 14:47:47 also 14:47:49 #link https://wiki.openstack.org/wiki/API_Working_Group/API_Current_States 14:47:51 mmm neutron 14:47:56 for the API Working Group 14:48:09 yeah I'm cursing at ascii tables. guh 14:48:21 # topic Doc Tools status 14:48:36 nothing new on openstack-doc-tools... 14:48:39 I'd like to get another release of the clouddocs-maven-plugin to fix a bit of bad output in the Ops guide 14:48:49 just haven't pursued it since summit 14:48:55 ok then 14:49:00 #topic Open discussion 14:49:11 open discussion or we can conclude early 14:49:18 I have something 14:49:20 anything else I missed? 14:49:23 sure nickchase 14:49:28 about the doc-tools, I'll try to reduce the duplication with the oslo team during this cycle 14:49:37 (for the config-ref) 14:49:38 gpocentek: Great! 14:49:39 oo sounds good gpocentek 14:49:55 nothing from me 14:50:02 Regarding Xen bugs: I got a contact at Citrix 14:50:10 He's going to look at Xenapi state 14:50:12 I have approval to try and hire in some people specifically for docs. Need suggestions on how many we think we ultimately need and what skills they need. 14:50:42 AJaeger_: great! 14:50:50 * AJaeger_ will send a new version of the driver spec later today 14:50:52 nickchase: we alked about contract writers on Friday 14:51:12 nickchase: the sense from teh group is that we need more than one (heh, yeah) for the flex team to be useful to us 14:51:25 nickchase: so there's that. We talked about 3 maybe being a good number? 14:51:40 nickchase: for the balance between manageable and flexible 14:51:50 nickchase: Lana (loquacities on IRC) may have ideas as well. 14:52:03 nickchase: we could meet with her after 4 my time one day 14:52:25 OK, let's do that. Today or tomorrow? 14:52:29 nickchase: also I talked to Lew Tucker, and his budget is tight, so he's not sure about funding past March 2015. 14:52:45 nickchase: yeah today works great for me. Thursday, not so much 14:52:50 OK, that works. I might be able to pull Elke over. We'll see. 14:52:54 nickchase: I think she's back from travels. Let's try. 14:52:56 OK, if Lana can do it let's plan for today. 14:53:03 nickchase: ok sending invite now 14:53:05 thx 14:53:08 lana is out iirc 14:53:38 she got back to Australia yesterday morning (Australia Weds morning), and might be available, but jetlagged 14:53:44 she’s officially back in office on Monday, IIRC 14:54:06 ah ok 14:54:16 we'll see what we can do, Nick, we can meet for sure 14:54:35 ok 6 minutes back? 14:54:43 great! 14:54:44 going 14:54:45 going 14:54:49 gone! Thanks all! 14:54:51 #endmeeting