01:08:27 #startmeeting docteam 01:08:28 Meeting started Wed Apr 15 01:08:27 2015 UTC and is due to finish in 60 minutes. The chair is loquacities. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:08:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:08:32 The meeting name has been set to 'docteam' 01:08:39 right, who's here? 01:08:43 hi loquacities 01:08:49 hi deepti! 01:08:51 hey loquacities 01:08:54 I'm in the house 01:08:56 Morning! 01:08:57 moo 01:09:03 Here 01:09:07 hi everyone :) 01:09:23 asettle? 01:09:38 Sorry! Here! Slow day today 01:09:40 I cannot brain 01:09:43 I haz the dumb 01:09:50 np, disregard my other message :) 01:10:02 Thanks for hte ping JRobinson__ :) 01:10:24 asettle: know them feels 01:10:38 I don't know what it is, but I am out of my mind exhausted. 01:10:39 Annywya 01:10:40 #topic Action items from the last meeting 01:10:43 LET THE GAMES CONTINUE 01:10:57 the only action i can find is "asettle to book informal Brisbane meetup for 31 March, and send out invites" 01:11:02 which of course happened 01:11:12 so, thanks for coming out everyone, it was fun :) 01:11:33 It had a great turnout :) 01:11:38 Glad you could all make it :) 01:11:38 #topic PTL changes: Anne will complete Kilo, Lana is planning Liberty 01:11:53 that shouldn't be news to anyone, but does anyone have any questions? 01:12:24 Is there any further voting that needs to happen? sorry if obvious 01:12:30 no, it was uncontested 01:12:41 loquacities: it just means you're crazy 01:12:45 * JRobinson__ nods 01:12:52 so if you don't like me, you need to nominate yourself next time :P 01:12:57 i thought about trying for ptl 01:13:03 as it is, you're now stuck with me for the next six months 01:13:11 then realized that i'm crazy, but not quite insane. 01:13:14 (yet) 01:13:16 Sam-I-Am: apparently, i am 01:13:28 are you an alcoholic yet? 01:13:32 already was 01:13:38 it was what qualified me to run 01:13:38 relapse 01:13:42 ok, moving on ... 01:13:49 #topic Kilo tasks: 01:13:55 there's a few things here: 01:14:07 first of all, RST publishing is working OK at this stage, with one exception 01:14:21 there's been some issues with translation where a higher than expected number of strings have remained untranslated 01:14:45 i'm going to be going into the translation meeting on thursday to try and understand that issue better 01:14:53 (as anne's proxy, i might add) 01:15:11 the next topic on kilo is bug triaging 01:15:17 basically, we need to do some 01:15:32 i believe anne is setting up another bug triage day, but if you have spare time, that's a good task to do this week 01:15:35 So, um... what happens if RST doesn't work with translation? 01:15:49 Also, can I question why this wasn't discussed before the RST conversion began? Or was it, and a trial was successful? 01:16:06 the triage issue is fun... because its a lot of things thrown over the fence from devs expecting us to rtfc 01:16:12 asettle: we either delay publishing the translated copies, or publish translated copies with some english strings 01:16:20 Sam-I-Am: +1 01:16:23 Gothca 01:16:25 Gotcha* 01:16:41 asettle: and so, yes, there was a trial done, but we didn't realise that some of the markup wasn't going to work so well 01:16:47 there's an issue with backticks, apparently 01:16:49 That's a bit unfortunate 01:16:53 oh I see 01:16:58 So you couldn't see all the issues 01:17:00 Mer 01:17:00 anyway, my understand is still a bit patchy, which is why i'm going to the meeting 01:17:07 Okay :) 01:17:12 Please let us know the outcome :) 01:17:12 so hopefully i'll know more soon 01:17:15 will do 01:17:30 in bug triage, if we cant figure it out, maybe tag the developer of the patch on it? 01:17:47 that is sensible, i think 01:17:51 the rst thing is kind of messy. and now its all loq's mess to clean up :) 01:17:55 although a personal ping might be more successful, if possible 01:18:06 Sam-I-Am: no it's not, kilo is still anne's problem :P 01:18:07 well, either way... somehow get the dev involved. 01:18:14 loquacities: riiiiiiiight 01:18:14 +1 01:18:16 * Sam-I-Am grabs popcorn 01:18:24 (that's what i keep telling myself, anyway) 01:18:34 uh huhhh.... 01:18:41 ok, the only other topic on kilo tasks is that the networking guide is having a doc day on 23 april 01:19:00 i might ask Sam-I-Am to elaborate on that when we get to the specialty teams bit, though 01:19:05 which is also the day i have a dentist appointment :/ 01:19:06 if that's ok with you Sam-I-Am? 01:19:20 i... guess. it sort of happened while i was away. 01:19:37 oh! coding on anaesthetic! 01:19:40 \o/ 01:19:45 heh, ok 01:19:54 #topic Docs specs in review 01:20:02 the only one i'm aware of is the first app one: 01:20:08 #link https://review.openstack.org/#/c/170413/ 01:20:34 #topic Next migration project 01:20:48 so anne and i have been trying to work out which book to convert to RST next 01:20:59 there's been a good discussion on the ML about it over the past couple of weeks 01:21:12 and anne has put together a spreadsheet with the factors we want to consider 01:21:13 Yeah, it looks painful 01:21:18 #link https://docs.google.com/spreadsheets/d/10HD6iW1CtfB1qT2wVODYiHdC0ysr4xw392VCqHB-aaY/edit?usp=sharing 01:21:28 so the purpose of this is so we can reorder things how we want 01:21:42 there's no real decision yet, but it's an interesting exercise 01:21:56 any questions on that? 01:22:32 #topic Specialty teams 01:22:37 is there a lean toward the install guide and admin guide in particular? The large page views are attention grabbing. 01:22:55 JRobinson__: yeah, definitely 01:23:06 the install guide's holdup is mainly conditionals 01:23:12 but the install guide is hard because of conditionals 01:23:20 hopefully not duplicating a lot of stuff, only to have it diverge over time 01:23:36 +1 01:23:47 ok, just gonna run through the speciality teams real quick 01:23:52 HA Guide - Needs an updated spec 01:24:00 Training Guides - i don't have an update 01:24:05 Install Guides - RST conversion convo 01:24:33 User Guides - IA of guides (meetings resume this friday) 01:24:41 Security Guide - i don't have an update 01:24:53 API docs - i don't have an update 01:25:03 Networking Guide - Needs testing & review 01:25:13 and now would be a good time to mention that doc day again 01:25:16 Sam-I-Am: ^^ ? 01:25:41 yeah, apparently we need contributors... first, we need the existing scenarios converted to RST if they're not done yet 01:25:57 second, we need people to contribute to the non-scenario parts of the guide 01:25:57 can i sec an outreachy mentee on you? 01:26:00 or is that cruel? 01:26:06 sic* 01:26:10 a what? 01:26:21 an applicant in the outreachy mentor program 01:26:27 a manatee. Large, marine mammal found in Florida. 01:26:29 (previously the gnome OPW) 01:26:37 :) 01:26:37 bmoss: can they write? 01:26:45 boy, when you come into the middle of a conversation.... 01:26:52 Assign a bug and find out ;) 01:26:53 nickchase: hi! 01:26:55 nickchase: pays to be on time 01:26:57 hi. :) 01:27:00 loquacities, not sure, but they are technically excellent 01:27:10 bmoss: i'll consider hiring one 01:27:20 nickchase: can you elaborate more on the networking docs day? 01:27:39 yes 01:27:48 Edgar will rally the Neutron group troops to ... 01:28:04 basically fill in the gaps in the networking guide on the 23rd (I think) 01:28:06 i was sort of missing for that discussion 01:28:15 he's in there now... 01:28:30 cleaning up the index and making sure he understands how things work 01:28:37 and I'm finishing the other conversions 01:28:43 so it'll be obvious what's still missing 01:28:57 so is it worth asking the writers in this meeting to contribute during our 23rd? 01:29:16 do you have a wiki page or something where they can self-select tasks? 01:29:25 might need neutron knowledge 01:29:33 however, if devs write stuff, there will be plenty of -1s to fix 01:29:33 or general networking knowledge 01:29:35 sounds like a job for furface_ 01:29:36 :P 01:29:38 :) 01:29:49 :) 01:29:53 I think that... 01:29:56 it's worth showing up. 01:30:00 i suspect docs folks will make it look pretty (anne's not here, right?) 01:30:02 Edgar is making a etherpad 01:30:07 but I don't think he has done it yet 01:30:10 Oh my jesus god I looked away for five minutes 01:30:25 Hey, Alex 01:30:34 The TOC is here, though: https://wiki.openstack.org/wiki/NetworkingGuide/TOC 01:30:35 ok, so for the minutes: please consider getting involved in the networking guide doc day on the 23rd, watch the ML for an etherpad and more details 01:30:44 Hey nickchase :) 01:30:48 correct. we should have something on Friday 01:30:50 Sorry, all - I'm going to have to steal away the RHEL-OSP Red Hatters now I'm afraid 01:30:55 23.april? 01:30:57 awesome, thanks nickchase 01:31:04 We'll keep track 01:31:05 adahms: thanks man :) 01:31:12 can we move on? 01:31:15 loquacities: please check the date 01:31:23 have to go to another mtg... 01:31:26 i've got 23 april, is that wrong? 01:31:26 I'm not sure it's the 23rd. whatever I said it is, it is. 01:31:35 $dayofweek 01:31:35 that's what anne had in her update 01:31:40 then that's right 01:31:42 ok 01:31:54 slong_: so good to see you! 01:31:59 hello and goodbye :) 01:32:09 #topic Doc tools update 01:32:17 anne has "releasing next Sphinx theme and clouddocs-maven-plugin for Kilo" 01:32:22 but i don't actually have any further info on that 01:32:38 so, moving on 01:32:43 #topic Vancouver 01:32:50 Design summit sessions etherpad here: #link https://etherpad.openstack.org/p/Docs_Liberty_Design_Sessions 01:32:59 please add your suggestions there 01:33:14 any other questions/comments on summit? 01:33:40 looking forward to it 01:33:45 me too! 01:33:54 #topic APAC Meetup 01:33:59 Planning for an APAC OpenStack meet up in May, ping asettle 01:34:10 I love it when the thing I write comes back to me 01:34:11 Huzzah 01:34:16 :P 01:34:37 Basically, May, I was thinking mid to late may (closer to the swarm) for catch up 01:34:50 Thinking we might go closer to the RH office this time round so that furface_ doesn't exhaust himself 01:34:51 ;) 01:34:56 That wholeeeeee 2km each way 01:34:58 lol 01:34:59 remember that late May is summit 01:35:00 lol 01:35:04 bmoss I do indeed 01:35:07 I am delicate 01:35:14 more like mid-may, though; 18-22 01:35:15 it would be nice to have a summit debrief 01:35:21 i guess that's late (doh) 01:35:24 I think post summit is a good idea 01:35:29 nickchase lol you beautiful 01:35:33 i'm back on 25 may 01:35:50 Cool well, let's aim for something closer to the 30th... enough time for sleeps 01:35:58 that would work for me 01:36:00 sleep is optional 01:36:01 So the wednesday of the 27th > 30th, good plan 01:36:01 Then we can chill, chat about summit, discuss OS plans, and talk about nickchase when he's not around ;) 01:36:02 How about first week of June? 01:36:15 for selfish reasons, since I'm not back until June 1 01:36:28 bmoss ahuh, noted in my diary 01:36:31 #action asettle to investigate first week of june for another APAC openstack docs f2f 01:36:34 June 3 > June 5 then 01:36:37 "Dear Diary, Brian away. Quickly, steal his wife, and home" 01:36:46 oh, and from earlier, because i forgot to write it out: 01:36:55 #action Lana to report back on i18n RST issues 01:36:56 HA! She's with me in Canada. 01:37:19 And wher am I bmoss? 01:37:20 that should make it easier to steal your home... :) 01:37:23 ok, that's all i had 01:37:33 nickchase is with me! 01:37:33 #topic Open discussion 01:37:47 yep. :) 01:37:48 * bmoss invests in a security system 01:37:50 have at it! 01:38:07 Docs swarm... 01:38:10 What about it? 01:38:16 Oh yeah, actually, I need you for that nickchase 01:38:20 yeah, that should have been in the agenda 01:38:28 While i've got his attention 01:38:33 I've booked Opera House for Aug 13-14, 9am to 5pm. 01:38:39 excellent 01:39:11 But since I will not be at RH at that point, Suyog has agreed to take over the booking. 01:39:13 nickchase I'll be sending an email out shortly. We're going to be conducting a swarm to reboot the arch guide. I will be requiring some SME's. Are you able to help us? I will be providing plenty of warning. I just need you to be available to reply to questions in emails one particular evening/day 01:39:42 bmoss: ok, cool. thanks to suyog :) 01:39:43 So in other words, as of Monday Suyog is the RH contact for the docs swarm. 01:39:51 cool beans, thank you 01:39:53 I don't know that I will be the right person but I know someone who will likely be able/willing to help. 01:40:00 define "reboot"? 01:40:01 nickchase I would love that. Who do you have in mind? 01:40:17 His name is Christopher Aedo. 01:40:19 nickchase revamp more like. There's some technical inaccuracies currently, and mostly just consistency within the writing. 01:40:34 Send me an email and we'll coordinate 01:40:35 I've spent the last few months changing it from passive to active voice. Which has ben a task. 01:40:40 You're a gem, thanks nickchase :) 01:40:44 np 01:40:44 been* 01:41:22 asettle, bmoss: anything else that needs doing on the swarm at this stage? 01:41:48 loquacities, I don't think so. We've got a location and dates. 01:41:50 Currently, no. SME emails will be send out later. I have a plan in motion. Nearly done with the passive stuff. I think we're rolling. 01:42:03 excellent, thanks :) 01:42:05 Other than I need to know exact numbers at some stage to be able to allocate chapters/sections 01:42:07 ok, i think we're done here 01:42:10 But I think we can discuss that in June 01:42:11 thanks for your patience 01:42:14 Please put a note for the June meeting? 01:42:31 sure :) 01:42:35 oh, actually 01:42:37 one more thing 01:42:50 Yus? 01:43:01 loquacities: when did you become steve jobs? 01:43:06 one of the RCBAU guys mentioned that our *official* docs meeting schedule is 1-3 and 2-4 wednesdays 01:43:16 Sam-I-Am: i've had tendencies all my life 01:43:25 when we really should be on alternating weeks 01:43:32 yes 01:43:33 does anyone have any issue with me changing that? 01:43:36 no 01:43:39 nope. 01:43:40 do the things 01:43:43 cool 01:43:45 i can fix that 01:43:55 #action Lana to change meeting schedule to alternating weeks 01:44:00 ok, now i'm really done 01:44:01 no worries there. 01:44:03 thanks everyone :) 01:44:09 this way i can actually make it a calendar thing 01:44:09 thanks loquacities 01:44:17 because calendars dont do "2 and 4" or "1 and 3" 01:44:26 #endmeeting