14:01:41 <annegentle> #startmeeting DocTeamMeeting
14:01:42 <openstack> Meeting started Wed Jan 15 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 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:46 <openstack> The meeting name has been set to 'docteammeeting'
14:01:50 <annegentle> boy I haven't done these in a while
14:01:59 <annegentle> Ok, action items from last meeting
14:02:07 <annegentle> #topic Action items from last meeting
14:02:07 <EmilienM> good morning :)
14:02:27 <annegentle> I have one where slong was going to add WIP info to the HowTo page
14:03:29 <annegentle> Just did a search for "work in progress" and wip on that page but dont' see it
14:03:56 <annegentle> But also chandankumar has it as an action item from the previous meeting
14:04:27 <annegentle> I'd just do it but I'm not sure what people are seeking
14:04:33 <annegentle> Leaving it as a continuing action item
14:04:41 <annegentle> #action slong or chandankumar add WIP info to https://wiki.openstack.org/wiki/Documentation/HowTo#Reviewing_Documentation
14:05:06 <annegentle> #topic Report from Doc Bug Day Dec 20
14:05:08 <dianefleming> yeah, i'm not sure what that's about
14:05:17 <annegentle> We definitely closed at least 80 bugs, that is FAN TAS TIC.
14:05:31 <Sam-I-Am> it was euphoric :)
14:05:46 <annegentle> hee
14:05:55 <annegentle> I also had the API site repo added to http://status.openstack.org/bugday/
14:06:49 <dianefleming> api site doesn't look so good!
14:06:51 <dianefleming> ha
14:07:19 <annegentle> heh, well that shows 24  hours
14:07:25 <annegentle> so it only looked good the day of :)
14:07:31 <dianefleming> i see
14:07:43 <AJaeger> Hi, sorry being late ;(
14:08:07 <Sam-I-Am> hi andreas
14:08:26 <annegentle> morning!
14:08:28 <Sam-I-Am> AJaeger: dont worry, you got all the action items we already covered :)
14:08:40 <AJaeger> Yeah!
14:08:41 <annegentle> there was a nice graph in activity.openstack.org I was going to post but I can't seem to find it, sigh
14:08:47 * AJaeger plans to ignore them ;)
14:09:02 <annegentle> it was a great effort
14:09:52 <AJaeger> it was indeed!
14:10:06 <annegentle> the graph is like this one http://activity.openstack.org/data/display/OPNSTK2/All+Projects+Activity+Dashboard+-+Last+30+Days?src=contextnavchildmode but individual repos could be tracked. anywho.
14:10:18 <annegentle> #topic Schedule January Monthly Google Hangout
14:10:40 <annegentle> Looking at next Monday evening my time, 1/20
14:10:41 <AJaeger> annegentle, http://activity.openstack.org/data/plugins/zfacts/renderpage.action?template=Project%20Activity&title=openstack-manuals%20-%20Activity%20Dashboard&repositoryID=SCM%2Crepository55dc94de-6597-4420-8e0b-09963819aade ?
14:10:57 <annegentle> AJaeger: YES! Thank you!
14:11:14 <annegentle> #link http://bit.ly/1b32JM0
14:11:35 <annegentle> Look at that spike! Woo.
14:11:42 <Sam-I-Am> annegentle: that time works for me. who all can join this?
14:12:00 <annegentle> Sam-I-Am: anyone can join, first 10 get mics
14:12:16 <Sam-I-Am> will it go on youtube?
14:12:19 <annegentle> I don't think there's another way with Google Hangouts, 10's the limit
14:12:28 <annegentle> yeah we will do "On Air" again which will go on youtube
14:12:35 <AJaeger> I'm 6 (or 7) hours ahead of you - what time do you plan for the meeting?
14:12:42 <annegentle> There's also going to be a webinar the first week of Feb with QA, Docs, and Infra
14:13:08 <annegentle> AJaeger: I'm thinking of evening but you had to miss the last one because of that, right? We can try another time
14:13:22 <AJaeger> Whatever works for most...
14:13:24 <annegentle> Let's play with http://www.timeanddate.com/worldclock/meeting.html
14:13:39 <annegentle> AJaeger: I wouldn't mind playing with times a bit
14:13:44 <dianefleming> what is the purpose of the google hangout?
14:13:46 <nermina> sorry i'm late
14:14:01 <Sam-I-Am> hi nermina
14:14:07 <nermina> hi sam-i-am
14:14:16 <NickChase> Hey, sorry I'm late, I was in the wrong room. :)
14:14:18 <carlp> morning Sam-I-Am
14:14:19 <annegentle> dianefleming: Lana likes them for getting to know each other and real-time chat
14:14:26 <annegentle> heh sorry NickChase we lost that one
14:14:38 <annegentle> though no one's in there, oh well
14:14:45 <NickChase> that's life
14:14:50 <annegentle> all, do you think there's still value in the video chat?
14:14:51 <NickChase> as long as we know where to go. :)
14:15:17 <dianefleming> okay - sounds good -
14:15:17 <NickChase> I'm torn; it's nice to see face to face, but it's nice to have everything recorded, too.
14:15:48 <annegentle> You know, looking at http://www.timeanddate.com/worldclock/meetingtime.html?iso=20140115&p1=24&p2=37&p3=57 it seems like your 9:00PM might work AJaeger
14:15:50 <NickChase> or do you mean the sunday night thing in addition to this meeting?
14:16:09 <AJaeger> annashen, my 9pm works for sure
14:16:24 <Sam-I-Am> carlp: hi
14:16:29 <annegentle> NickChase: two meetings: google hangout and a webinar
14:16:42 <NickChase> right, sorry,it's early. :)
14:16:42 <Sam-I-Am> i did my first hangout with tom the other day and it was really cool to see face to face
14:16:46 <annegentle> NickChase: no worries :)
14:16:47 <Sam-I-Am> so i think there's value in it
14:16:52 <annegentle> Sam-I-Am: yeah I like it too
14:16:56 <Sam-I-Am> plus it is recorded...
14:16:58 <AJaeger> Yeah, there's value to it
14:17:06 <annegentle> ok cool
14:17:14 <NickChase> I do think it's good to see face to face, but let's keep it out of the weekends. :)
14:17:18 <annegentle> I'll set it up, this time more geared towards EU
14:17:26 <annegentle> NickChase: sure makes sense :)
14:17:34 <annegentle> For next week, look for an invite like last time
14:17:36 <annegentle> #topic Webinar in February (date tbd) to update Icehouse doc/qa/infra plans
14:17:53 <annegentle> Just letting you all know I'm prepping a 10-slide deck to share with anyone who comes to the webinar
14:17:57 <NickChase> I don't mind working at 9 or 10 pm, but weekends are off limits unless I want a divorce.
14:18:00 <annegentle> these are the same format as for all the PTLs
14:18:07 <annegentle> NickChase: heh, no one wants that!
14:18:13 <NickChase> which webinar?
14:18:21 <dianefleming> not exactly true (divorce)
14:18:25 <annegentle> NickChase: a to be scheduled one similar to the ones the other PTLs have done
14:18:31 <NickChase> ah!
14:18:32 <NickChase> great!
14:18:39 <annegentle> this summit, HK, they stopped having the PTLs give an update for plans during the Summit itself
14:18:48 <annegentle> so, they're doing webinars after
14:18:52 <annegentle> this is docs turn
14:18:56 <annegentle> should be first week of Feb.
14:19:05 <annegentle> #topic Done with backports to stable/havana
14:19:09 <annegentle> ding, dong, done!
14:19:13 <AJaeger> annegentle, is there anything you need help with for the webinar?
14:19:14 * Sam-I-Am faints
14:19:16 <annegentle> AJaeger: any comments there, are there more lurking?
14:19:37 <annegentle> Really the cutoff was going to be last week but without a meeting we didn't finalize
14:19:43 <AJaeger> I always thing we're done - and in comes another one...
14:19:45 <AJaeger> ;(
14:19:52 <Sam-I-Am> annegentle: i think we can kill major updates... but there might be serious things that come up
14:20:00 <annegentle> AJaeger: If you could put your wanted bullets into an email for the slides that would be awesome, how much focus on tools, also?
14:20:14 <chandankumar> hey here i came, i just woke up!
14:20:22 <annegentle> chandankumar: welcome!
14:20:31 <AJaeger> Yeah, there might be serious ones, let's backport those - but not anything minor or cosmetic
14:20:35 <NickChase> good morning, chandankumar. :)
14:20:47 <AJaeger> annegentle, ok, can provide a slide or two for the tools as input
14:20:48 <annegentle> chandankumar: say, can you update the https://wiki.openstack.org/wiki/Documentation/HowTo page with WIP info? We weren't sure what needs to be added and it was an action item for you
14:20:54 <annegentle> AJaeger: perfect, thanks
14:21:06 <annegentle> AJaeger: any generic slide template (open office is fine too) would do
14:21:09 * Sam-I-Am needed to WIP something the other day :/
14:21:16 <chandankumar> NickChase, good morning
14:21:31 <chandankumar> annegentle, doing that right now !
14:21:33 <AJaeger> annegentle, ok
14:21:40 <annegentle> Sam-I-Am: you can tell we are pretty easy to negotiate with
14:21:51 <annegentle> but what I want to communicate is that we're done backporting
14:21:57 <Sam-I-Am> yup
14:22:07 <annegentle> cool
14:22:08 <Sam-I-Am> the good news is we're leaving the havana install docs in a pretty good state
14:22:30 <annegentle> Sam-I-Am: they are really well off, and commenters are helping each other every day, which is so awesome
14:22:38 <annegentle> So let's get to it,
14:22:47 <annegentle> #topic Discuss any installation guide changes for Icehouse
14:23:07 <annegentle> At the Summit, we said we would continue in Icehouse with the manual install. That seems to be all fine and good.
14:23:08 <NickChase> Networking guide?
14:23:08 <AJaeger> Just one wish: Rewrite Networking chapter ;)
14:23:16 <Sam-I-Am> AJaeger: yeah, about that...
14:23:18 <NickChase> :)
14:23:18 <Sam-I-Am> but first
14:23:28 <annegentle> One thing we are waiting for is a decision at i2 about whether we continue to doc nova-network with neutron
14:23:35 <Sam-I-Am> i'm installing icehouse now using trunk and so far so good
14:23:37 <NickChase> +1 on continuing manual install
14:23:50 <chandankumar> +1
14:23:54 <Sam-I-Am> +1
14:24:01 <AJaeger> annegentle, nova-network will be in Icehouse AFAIU the discussion
14:24:09 <annegentle> AJaeger: tha'ts my sense of it too
14:24:28 <NickChase> From the development discussions around nova-network and making changes to it it looks like it will still be there
14:24:30 <AJaeger> http://lists.openstack.org/pipermail/openstack-dev/2014-January/024175.html
14:24:36 <annegentle> NickChase: agreed
14:24:37 <NickChase> they are talking about using nova-conductor, etc.
14:24:42 <NickChase> so I think it needs to stay
14:24:54 <Sam-I-Am> yeah i dont think nova-net is going anywhere just yetr
14:24:58 <annegentle> So, I like that we get to maintain the current guide as-is
14:25:01 <Sam-I-Am> neutron still lacks a few important features
14:25:10 <annegentle> I know Sam-I-Am has good ideas for neutron too
14:25:16 <annegentle> and we'll ahve to add ml2 plugin explanations
14:25:23 <Sam-I-Am> annegentle: well, sort of.  i'm wondering about putting all the networking stuff together
14:25:23 <carlp> Sam-I-Am: This is true, but the goal is to have all those features in place for Icehouse
14:25:37 <annegentle> Sam-I-Am: tell me more, separate guide kinda stuff?
14:25:57 <AJaeger> ML2 instead of current OVS I guess
14:25:57 <Sam-I-Am> it seems to me that the installation guide is where a lot of people end up first
14:25:58 <annegentle> I still like the choose your own adventure
14:25:59 <carlp> The goal is to officially deprecate nova-network in Icehouse if possible
14:26:21 <NickChase> choose-your-own-adventure is of course best -- for some things.
14:26:24 <AJaeger> And change the neutron chapter so that there is no jumping around - and the Use-cases section follows the rest
14:26:31 <annegentle> carlp: yes, and the sprint is still going on I think, so hence my lack of a final statement :)
14:26:32 <Sam-I-Am> so i'm thinking about offering configurations for a couple of common configurations... one or two with neutron, and of course nova if it still exists
14:27:00 <annegentle> Sam-I-Am: ok, that sounds ok (common configs for neutron)
14:27:02 <Sam-I-Am> for more advanced stuff, maybe consult the book on networking?
14:27:30 <Sam-I-Am> just dont want to overload people
14:27:50 <NickChase> Let's talk about "the book on networking".  Right now there's a book for the networking API, and a monster chapter on networking in the Cloud Admin Guide.
14:27:57 <annegentle> Sam-I-Am: yeah that's what I'm thinking too, but we didn't really plan for a networking guide in icehouse and haven't found a real owner. Doesn't mean it's unpossible but we've got cleanup of cloud admin guide so I'm hesitant
14:28:16 <NickChase> Even so, it doesn't provide a lot of the context and concepts it needs.
14:28:16 <annegentle> NickChase: yeah talk more to it.
14:28:26 <NickChase> I would very much like to see us do the following:
14:28:58 <NickChase> 1)  Take the networking chapter and break it out into a stand-alone book that is ALSO included (via includes) in the Cloud Admin Guide.
14:29:24 <NickChase> 2)  Add contextual/introductory material that gives people the background that they need on important concepts.
14:29:43 <NickChase> 3)  Reorganize if necessary.  (Not sure how much re-org will be necessary.  Maybe not that much.)
14:29:55 <NickChase> I went through the structure in prep for this meeting
14:29:56 <annegentle> NickChase: do you have a writer in mind for 2)?
14:29:59 <Sam-I-Am> so... remove the networking chapter from the install guide?
14:30:01 <dianefleming> is networking a post-installation (configuration) task? is that why you want it in the cloud admin guide?
14:30:10 <annegentle> NickChase: yeah I think that's fine maybe woudl question the duplication though
14:30:34 <annegentle> dianefleming: networking decisions do have to be made upfront, but people are not making good ones due to not having the background in networking
14:30:38 <NickChase> anngentle: I think that me and nermina can handle #2.
14:30:48 <NickChase> unless someone else wants it
14:30:56 <NickChase> Lorin will probably also be willing to assist in some way
14:31:11 <nermina> he definitely was offering
14:31:13 <annegentle> NickChase: Yeah I don't think there's infighting for it :) Lorin started a new job and won't be working on OpenStack but might be swayed to help
14:31:27 <NickChase> re: the duplication, I'm not sure that there IS duplication.  we're just making it possible to get networking on its own if you want it
14:31:31 <annegentle> Sam-I-Am: how interested are you in the networking guide? esp. the educational portions
14:31:34 <NickChase> we can make that clear right in the book
14:31:40 <carlp> I would dis-agree that networking is a post installation task. Choosing neutron vs nova-networking is definitely an installation task. Having a very basic neutron config also makes sense as an install task, and then go into more advanced stuff later
14:31:44 <Sam-I-Am> NickChase: i was also hoping we would offer 2 arch options in the install guide... one for nova-net, one for neutron... then make sure we create detailed diagrams and background into for them... and follow the theme throughout the guide
14:32:06 <Sam-I-Am> carlp: particularly because your arch changes (e.g, addition of network node)
14:32:08 <annegentle> Thing is, I would prefer we point to other places to learn the complexities of networking rather than write our own... is there a way to keep the context in OpenStack or is the topic not like that?
14:32:10 <NickChase> carlp:  I agree with you.  But you can't put all of that in the install guide. :)
14:32:25 <annegentle> Sam-I-Am: now you're talkin' == sold!
14:32:32 <nermina> i bet you that training guides have a lot of conceptual stuff
14:32:35 <NickChase> Sam-I-Am:  Agreed, though I wouldn't kill ourselves on nova-net
14:32:38 <Sam-I-Am> NickChase: it seems to me that most people using the install guide just want it Just Work when they're done... THEN go figure out why it works :)
14:32:57 <annegentle> carlp: yeah the install guide needs to do one happy path then get people to really think about their deployment
14:33:33 <NickChase> annegentle: I agree to a certain extent, but it's difficult to find resources that really provide the context that we need.  I'm all for linking out for topics where it exists, though.
14:33:34 <carlp> annegentle: agreed, when I said "more advanced stuff later" that doesn't need to be in the install guide
14:33:35 <Sam-I-Am> thats why i was thinking about covering a couple of options well... provide a little background, but make them work.  then provide the details and advanced config in a book somewhere... or some existing place
14:33:58 <Sam-I-Am> annegentle: yeah i can help with any networking stuff we put elsewhere
14:34:09 <nermina> sam-i-am, have you seen the cloud admin guide's networking chapter?
14:34:14 <NickChase> Sam-I-Am:  I agree that they want to just make it work.  But usually, it won't, and there's no simple answer as to why.
14:34:17 <Sam-I-Am> nermina: briefly
14:34:28 <annegentle> NickChase: +1
14:34:42 <nermina> i just recently moved quite a few config scenarios to it
14:34:45 <NickChase> The reality is that networking in OpenStack is just really, really complicated, and there's no getting around it.
14:34:59 <Sam-I-Am> NickChase: i think if we document the prereqs first, its not bad. i'm seeing plenty of people have success with neutron using the guide now.
14:35:19 <NickChase> Sam-I-Am:  that's great, and I agree.
14:35:26 <carlp> NickChase: using the ML2 driver with OVS and GRE "just works" in most cases these days. It's much simpler to debug over the older OVS code and is the forward path for the Neutron team anyway
14:35:31 <annegentle> NickChase: Sam-I-Am: can you also engage the neutron team after this week? They have a doc lead, Edgar Magana
14:35:43 <Sam-I-Am> annegentle: sure
14:35:43 <annegentle> I mentioned it at their team meeting week before last and they are interested
14:35:55 <NickChase> carlp:  that's great.  I'd love your feedback on this.
14:35:56 <annegentle> carlp: that is GREAT to hear
14:36:05 <chandankumar> annegentle, while writing networking book, these two videos might be  helpful http://www.youtube.com/watch?v=afImoFeuDnY and  http://www.youtube.com/watch?v=wEa_8ESxPAY
14:36:07 <annegentle> carlp: makes the doc job that much easier
14:36:17 <NickChase> that's fantastic, Anne.  I'd LOVE to get with Edgar.
14:36:21 <NickChase> Contact info?
14:36:23 <Sam-I-Am> one thing i think we can all agree on... lets break up the huge xml file covering neutron into per-node files like we do everywhere else :)
14:36:26 <annegentle> carlp: how much interest do you have in the networking vs install guide?
14:36:36 <annegentle> carlp: cuz you can probably tell we want to write this with a few people
14:36:36 <NickChase> Sam-I-Am:  +`
14:36:41 <Sam-I-Am> that thing is a pain in the butt to edit
14:36:42 <NickChase> +1, even .:)
14:36:46 <annegentle> Sam-I-Am: oh good thinking
14:36:48 <Sam-I-Am> more like +100000 :)
14:36:54 <NickChase> very much so.
14:36:59 <annegentle> Sam-I-Am: make it so!
14:37:17 <Sam-I-Am> then we need to figure out if we keep the format supporting multiple plug-ins
14:37:19 <annegentle> I really appreciate how much thought people are putting into thise
14:37:22 <annegentle> these
14:37:32 <Sam-I-Am> or just go with ML2 and make the guide less jumpy
14:37:42 <NickChase> Sam-I-Am:  Maybe we can get together later to discuss details?
14:37:44 <annegentle> Sam-I-Am: yeah, might play with it some and see what reviewers say, but I think ML2's the way
14:37:51 <Sam-I-Am> NickChase: yes! ... and carlp
14:38:09 <carlp> annegentle: I have a lot of interest in making the documentation for networking better everywhere. Most of the customers I deal with are using blogs because the docs are not up-to-date enough or simply don't cover enough and it gets complicated because the blogs people find are not clear on what versions of OpenStack or the code, etc
14:38:10 <Sam-I-Am> annegentle: i might need some help breaking the big file up
14:38:24 <nermina> i can help, sam-i-am
14:38:25 <NickChase> Sam-I-Am:  I will help you with that
14:38:28 <NickChase> :)
14:38:34 <nermina> high five
14:38:37 <NickChase> Opening a side channel to set a time...
14:38:42 <Sam-I-Am> carlp: we do see a lot of third-party guides... and i think those will go away if we make this guide work
14:38:51 <carlp> Sam-I-Am: agreed
14:39:09 <Sam-I-Am> nermina/nick thanks... i'm not a docbook guru yet
14:39:29 <nermina> you'll be one by the time you're done with this guide, sam-i-am :)
14:39:32 <Sam-I-Am> ha
14:39:32 <annegentle> Sam-I-Am: you're certainly doing a great job
14:39:33 <carlp> Sam-I-Am: at least for the OpenSource stuff (OVS, LinuxBridge, etc). There will always be third-party guides for the proprietary plug-ins but that's unavoidable
14:39:45 <annegentle> carlp: are there already?
14:39:51 <Sam-I-Am> oh, sure...
14:40:19 <carlp> annegentle: yes. Most of the third-party plugins from commercial vendors ship their own documentation to customers (nicira, etc)
14:40:38 <annegentle> carlp: ah ok, that's not stuff we see. Wonder if we can just make a list to links to their sites then?
14:40:48 <annegentle> carlp: that'd be a huge debt load off docs
14:40:54 <NickChase> +1
14:41:00 <Sam-I-Am> so far, i havent seen many people using the install guide with special plug-ins
14:41:07 <Sam-I-Am> its always been a very basic architecture
14:41:09 <NickChase> At the very least, WE can go there to get information. :)
14:41:14 <annegentle> funny thing is, block storage tends to write theirs upstream
14:41:17 <carlp> annegentle: Maybe. Not all of them are publicly available. It's a mixed bag.
14:41:26 <annegentle> carlp: got it. good to know
14:42:12 <annegentle> woo mixed bag. not :)
14:42:28 <annegentle> ok, I'm definitely going to talk about install guide for that webinar
14:42:35 <annegentle> note to self
14:42:42 <Sam-I-Am> cool
14:42:45 <annegentle> anything else on install guide? networking guide?
14:42:55 <NickChase> nope.
14:43:03 <Sam-I-Am> i think we have a plan
14:43:07 <annegentle> I'm going to put up some actions then. cool.
14:43:08 <NickChase> except carlp, let me know when you can meet
14:43:22 <annegentle> #action NickChase and carlp and Sam-I-Am to meet
14:43:23 <Sam-I-Am> i'm installing icehouse where i can... should know soon how that's turning out
14:43:42 <annegentle> NickChase: can you share on the Mailing list about the networking guide pull out
14:43:47 <carlp> NickChase: I'm flexible :)
14:43:48 <annegentle> NickChase: and contact Edgar?
14:43:57 <NickChase> Need his info.
14:43:59 <nermina> annegentle, what is still left to do on the install guide?
14:44:01 <NickChase> and yes, I will.
14:44:07 <annegentle> #action NickChase to contact Edgar Magana on the neutron team to let him know the networking guide plan
14:44:19 <annegentle> #action annegentle to email Nick and Edgar
14:44:30 <Sam-I-Am> nermina: there's plenty of phrasing/formatting cleanup
14:44:32 <annegentle> #action NickChase to email openstack-docs mailing list with plan for networking guide
14:44:41 <annegentle> anything I missed?
14:44:49 <Sam-I-Am> nermina: lots of inconsistency between sections
14:44:56 <annegentle> #topic Doc tools update
14:45:12 <nermina> sam-i-am, could you send me a msg with details?
14:45:20 <annegentle> The openstack-doc-tools release 0.3 went out Monday and release notes are now available
14:45:41 <annegentle> #link https://github.com/openstack/openstack-doc-tools
14:46:05 <annegentle> AJaeger: great story, I had an email from a cloud architect at Rackspace who found that missing div and your patch was already in the review queue! Winning.
14:46:27 <AJaeger> ;)
14:46:36 <Sam-I-Am> nermina: e-mail?
14:47:02 <AJaeger> There were many bugs in the api project sites where some never build - e.g. database-api was unbuildable
14:47:03 <nermina> nmiller@mirantis.com
14:47:08 <Sam-I-Am> nermina: k
14:47:13 <nermina> thanks, sam-i-am
14:47:31 <annegentle> AJaeger: wow that's blarg. Makes me want to go yell at people. Sigh.
14:47:39 <annegentle> AJaeger: good work here.
14:48:17 <AJaeger> annegentle, there's wasn't a patch for 6 months at least for the repo - and the bug was using clouddocs-plugin 1.7-SNAPSHOT...
14:48:31 <AJaeger> We really need those gates everywhere - I'm working on that
14:48:38 <AJaeger> And dianefleming helped a lot debugging
14:48:46 <annegentle> AJaeger: yeah I know the peeps working on it (or not working currently) and it's a problem, thanks for the help
14:49:01 <annegentle> AJaeger: and, getting Japanese translation automated will be very exciting
14:49:27 <AJaeger> YEah - but something I cannot handle right now - others have to help on that...
14:49:45 <annegentle> AJaeger: yeah I dont' think that's yours at all other than having the tool on pypi
14:50:03 <dianefleming> i could help with database-api - let me know
14:50:11 <dianefleming> or any other api that's not building
14:50:17 <annegentle> Let's see, nothing on the horizon for clouddocs maven plugin, though if you haven't pulled up api.openstack.org/api-ref.html you should!
14:50:20 <annegentle> #link api.openstack.org/api-ref.html
14:50:28 <annegentle> full refresh so that it works on mobile
14:50:44 <annegentle> A guy on me and Diane's team did it in like 4 hours on a Friday afternoon. He's that good.
14:51:07 <NickChase> annegentle: that's great!
14:51:09 <annegentle> dianefleming: cool thanks
14:51:22 <annegentle> #info openstack-doc-tools 0.3 released this week
14:51:43 <annegentle> #info clouddocs-maven-plugin released 1.12.2 refreshing http://api.openstack.org/api-ref.html
14:51:49 <annegentle> Anything else on tools?
14:51:54 <annegentle> # Open discussion
14:52:00 <annegentle> #topic Open discussion
14:52:16 <annegentle> sorry didn't mean to rush anyone but we've got 9 mins left
14:53:16 <AJaeger> annegentle, nothing else on tools - hope to have the gates working quickly - but waiting for infra
14:53:38 <annegentle> AJaeger: fine work you're doing
14:53:40 <AJaeger> What about glossary: Did you read my email? Is that something we should try for one guide - like Install Guide
14:53:49 <annegentle> AJaeger: I seriously was so happy about that caught div :)
14:54:04 <annegentle> AJaeger: oh yeah! GLossary
14:54:16 <annegentle> so during the book sprint the Ops guide peeps said the large glossary was tooooo big
14:54:32 <annegentle> dianefleming: didn't you try to do conditional output for it or some such? What was the story there? My memory fails me
14:54:59 <AJaeger> You can either add the whole glossary - or just the entries used in the guide. I would go for the later for now....
14:56:05 <AJaeger> The security guide already has that glossary with just the entries used in it - have a look at my email for the link
14:56:08 <annegentle> AJaeger: dianefleming: okay maybe that's what I was thinking of,that there's an automated way to have a smaller glossary?
14:56:18 <annegentle> AJaeger: and the security guide does this already somehow?
14:56:34 <AJaeger> http://docs.openstack.org/security-guide/content/go01.html
14:56:48 <annegentle> AJaeger: also is Tom accurate in his assessment that the glossary is not specially treated in translation? Not even sure how to research taht myself.
14:56:57 <AJaeger> Yeah, it does it - really short one
14:57:23 <AJaeger> The translators can just remove the few lines to include the glossary ;)
14:57:42 <annegentle> AJaeger: there's a bug already, it says See access control list. but access control list isn't an entry
14:57:44 <AJaeger> It's easy to add the glossary in a way similar to the install guide.
14:57:50 <annegentle> AJaeger: ok
14:58:29 <annegentle> colinmcnamara: or sean roberts, any report for training? I saw your notes from the last meeting
14:58:31 <AJaeger> annegentle, yeah - that one needs extra handling
14:59:01 <annegentle> AJaeger: ok, I'll file a doc bug
14:59:16 <AJaeger> annegentle, assign it to me, I'll take care of it
14:59:37 <annegentle> AJaeger: thanks!
14:59:47 <AJaeger> the hard part is adding all the <glossterm> entries to the guide....
14:59:53 <AJaeger> but not much...
15:00:26 <annegentle> AJaeger: yeah I see it as better than index entries but still work like that
15:01:26 <annegentle> Ok, outta time, not sure who has this room next.
15:01:31 <annegentle> Thanks everyone!! Great work, I mean that.
15:01:33 <Sam-I-Am> good meeting
15:01:34 <annegentle> #endmeeting