16:00:25 #startmeeting docteam 16:00:25 Meeting started Thu May 18 16:00:25 2017 UTC and is due to finish in 60 minutes. The chair is asettle. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:30 The meeting name has been set to 'docteam' 16:00:39 o/ 16:00:42 Hey ianychoi :) 16:00:45 hey 16:00:52 asettle, rluethi: hello! 16:01:03 rluethi: hooray! Glad you made it :) 16:01:12 so am I :) 16:01:39 AJaeger: hey pal! 16:01:58 * AJaeger is just lurking, need to cycle home and want to read backscroll 16:02:10 Okay AJaeger :) 16:02:18 Haha 16:02:19 welcome all lurkers! 16:02:22 We'll wait until 5 past for quorum :) 16:02:22 ;) 16:03:42 I know annegentle is around, but double booked 16:04:19 o/ 16:04:33 annegentle, hello! 16:04:36 hi! 16:05:22 Okay we're at 5 past 16:05:27 Should we continue? 16:05:31 The agenda is pretty short anyway :) 16:05:44 go for it! 16:05:54 +1 Let's go 16:06:00 Okay. 16:06:08 #link https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting 16:06:14 #topic Action items from the last meeting 16:06:42 I don't believe we had any again \o/ 16:06:43 So, nice! 16:06:51 #topic Summit recap 16:07:00 #link https://etherpad.openstack.org/p/docs-summit 16:07:11 This is our etherpad from the summit - linked to all other etherpads! 16:07:13 Universe of pad 16:07:23 There was a lot going on at the summit, a full on week, as always. 16:07:37 I'm currently writing up my summit recap email which has some more indepth information 16:07:46 But we'll be looking at some fairly radical changes with how the doc team is structured. 16:07:54 As it stands, the group has been going up and up and up, which is great. 16:08:04 But now we're at a stage where we are unable to maintain the content that we have 16:08:16 * AJaeger thanks asettle for driving all these discussions! 16:08:27 dhellmann has been working with me to come up with new action items for the future. 16:08:29 You can view them here 16:08:31 #link https://etherpad.openstack.org/p/doc-planning 16:08:35 thanks AJaeger :) I appreciate your support 16:09:03 * dhellmann checks his calendar 16:09:05 wow, that's a lot of action items. 16:09:09 One of the biggest concerns at the moment (and always has been, who am I kidding) is the Installation Guide 16:09:13 rluethi: sure is :( we have a *lot* of stuff 16:09:33 dhellmann: meeting time change ;) 16:09:45 If anyone has any questions about that, please ping me 16:09:50 I'm happy to walk it through with you all 16:10:40 asettle : ah, I guess I missed the notice of that. I'll talk to you later about how to keep up to date on these things :-) 16:10:48 I am glad to see that we haven't got any items :). 16:10:48 dhellmann: meeting minutes? 16:10:57 rluethi: none so far 16:11:00 But, It would be good to talk about that 16:11:09 And figure out where you want to take the training-labs and guides 16:11:14 asettle : well, I thought I'd try to attend until this transition is completed 16:11:26 * AJaeger adds some action items for rluethi ;) 16:11:27 asettle: was that with a threatening voice? 16:11:33 rluethi: hahahhaa not at all 16:11:59 I'll phrase with more smileys next time - I'm sorry. I do genuinely think we should chat about what you are thinking for the future :) 16:12:02 asettle, I want to follow the changes regarding some changes on translation (I18n) activities 16:12:06 no, ajaeger, stay good. 16:12:15 * AJaeger will 16:12:19 ianychoi: of course. Definitely a prioritiy 16:12:21 priority* 16:12:48 thanks dhellmann 16:12:48 asettle: sure, no problem. (maybe _I_ should have used more smileys) 16:13:08 Hahhaha perfect :) we'll sync up sometime soon 16:13:09 more smileys all around! 16:13:18 #action asettle to chat to rluethi about training-labs and guides future 16:13:31 #action asettle and ianychoi to discuss planning changes with translation activities 16:14:21 asettle, please try to reach out matjazp for training-guides :) If no, then I would like to propose it as an agenda for next IRC meeting (May 30). 16:14:55 ianychoi: good point! Please update the agenda for next week :) 16:15:33 :) 16:16:06 Okay, sorry, distracted all over hte hsop 16:16:07 the shop* 16:16:32 hop, shop, all good :) 16:16:35 * AJaeger will enjoy the sunshine with his bike now - bbl 16:16:42 cya! 16:16:45 I will be sending out an email to the dev ML regarding my concerns with the installation guide 16:16:48 cya AJaeger ! 16:16:53 cya AJaeger :) 16:16:54 Please everyone keep your eyes out for that 16:16:57 I would love your support and thoughts 16:17:47 asettle still need more context on discussions, need to read read read 16:18:02 annegentle: yep. there's more coming out too. After this meeting I will be sending out my summary email :0 16:18:03 :) * 16:18:09 Hopefully that'll add some more context, and we can go further 16:18:12 I'm always happy to answer questions 16:18:19 ok, good 16:18:45 It is hard to communicate everything when it all happens so fast! But hopefully I'll clarify evrything 16:18:58 annegentle, aha that's how to increase English - good writing is based on more more reading 16:19:26 so true! 16:19:31 :) 16:19:40 Hahaha 16:19:48 Well, annegentle you're going to love this reading :p 16:19:51 Anyway. MOving along :) 16:19:59 #topic Specialty team reports 16:20:09 annegentle: API :) 16:20:25 asettle on it! 16:20:55 #info Looking for better ways to indicate "nesting" on request parameters 16:21:10 #link https://review.openstack.org/#/c/464255/ 16:21:54 Looking :) 16:21:56 And then also saw that bug report on the developer landing page that the CLI section wraps badly, thanks dhellmann for reporting 16:22:10 otherwise, mostly looking for info on what came out of the Forum 16:22:15 that's all I have 16:22:46 Awesome :) thanks annegentle 16:22:52 Do you have any more reports on the theme, btw? 16:22:58 Lots of people are really interested in it 16:23:24 asettle interested in it how? I had hoped to get help with it at Write the Docs, I can't quite figure out how to bring in inherited pieces. 16:23:33 asettle any input on what they can't live without? 16:24:30 annegentle: none so far. Mostly that people are just mega excited for consistency. 16:24:34 and it's what we had identified before, that the openstackdocstheme doesn't "inhereit" 16:24:35 That's a sentence I never htought I'd say 16:24:41 asettle oh that's encouraging, yay 16:24:51 Very encouraging :D 16:25:07 I do need to make a 1.9.0 release for the header breakage (404s in links in drop-down menus) 16:25:25 #info Working on a 1.9.0 release of openstackdocstheme for bug fixing 16:25:30 annegentle : it looks like sphinx 1.6.1 breaks the oslosphinx theme inheritance, so keep an eye out for that in the work you're doing. 16:25:46 dhellmann ok, thanks 16:25:56 I just hit that yesterday, and we've been blocking 1.6.1 until we have a fix 16:26:03 that release broke builds all over the internet :- 16:26:05 asettle any input from infra team about their deliverables specifically or shall I reach out individually? 16:26:06 :-/ 16:26:10 dhellmann boo 16:26:26 annegentle: I've had no specifics, I"m sorry :( 16:26:38 asettle no worries, I'll reach out 16:26:39 I'll reach out and try and get some more info for you annegentle 16:26:49 At least, people that are putting in requests, I'll ask what they want ;) 16:27:27 asettle I'm sure consistency is a huge win :) 16:27:42 Hhahaha well, it was pretty exciting considering all I'd ever herad before was 'grumble grumble i hate change' 16:27:58 asettle ha! 16:28:07 Anyway! 16:28:08 consolidate for the win 16:28:12 Hahhaha yes 16:28:19 Okay, I don't see Matjaz? 16:28:22 Pranav? 16:29:27 It seems that matjazp is offline 16:29:39 Okay :) 16:29:46 Well, rluethi up to you then for Training labs 16:29:50 Anything happy-happening? 16:29:58 We have started development work for Pike. Small bug fixes, refactoring, ramping up for a few new features that we hope to introduce during this cycle. 16:30:03 Oh neato :) 16:30:17 This will give you a rough idea: #link https://review.openstack.org/#/q/status:open+project:openstack/training-labs 16:30:41 Cool 16:30:57 rluethi: do you need a second core on any of those? 16:31:22 I think I will first try to wack one of those that we have :). 16:31:50 Hahha okay :) 16:32:24 But yeah, we are spread thin as well. 16:33:12 rluethi: definitely worth us having that conversation then :) 16:33:24 sure 16:33:48 I want to make sure we're all coming together as a team, rather than being so silo'd. It definitely worked in the past, but as rluethi said, we're all spread pretty thin 16:33:56 o/ 16:34:00 sorry for being late 16:34:00 mpranjic: yo yo 16:34:02 That's okay :) 16:34:04 hey mpranjic 16:34:06 Thanks for joining 16:34:13 thanks for having me :) 16:34:19 No worries, we're just at the end here 16:34:20 mpranjic, hello! 16:34:28 #topic Bug triaging 16:34:37 #link https://wiki.openstack.org/wiki/Documentation/SpecialityTeams#Bug_Triage_Team 16:34:41 Olena is our current bug triage liaison (I am stepping in while she is PTO). Nothing notable. 16:34:45 Thanks to Chason to filling in the remaining slot! 16:34:54 Next up is bsilverman for the 22 May - 5 Jun 16:35:50 Aha... Olena triaged my recent bug submission - https://bugs.launchpad.net/openstack-manuals/+bug/1691058 :) 16:35:52 Launchpad bug 1691058 in openstack-manuals "Old EOL-ed release landing pages have master (up-to-date) document links" [Low,Confirmed] 16:36:22 ianychoi: ahhh jeez, good catch 16:37:06 #topic Open discussion 16:37:12 Alright, that's the end of this one folks! 16:37:23 Good 16:38:04 Any questions, concerns, comments, feelings? 16:38:17 During Docs/I18n project onboarding session, one tempest contributor applied openstackdocstheme by changing from oslosphinx: https://docs.openstack.org/developer/tempest/ 16:38:32 Ah, was that Matt? 16:38:40 huzzah 16:38:41 asettle, Masayuki :) 16:38:42 I know a lot of people were like 'why are we still using oslo.sphinx?!' 16:38:48 And I was like 'uhhhh, cause you choose to?' 16:38:57 And I18n team also now uses openstackdocstheme: https://docs.openstack.org/developer/i18n/ 16:38:59 :) 16:39:24 look at that cool parrot 16:39:46 oh I sat next to a tech writer at Pivotal who LOVES and I mean LOVES our fox mascot! 16:39:57 Hhahahaha that's cute 16:40:04 annegentle, haha thanks! :) I also love FOX mascot! 16:40:06 definitely nearly took my fox sticker off my laptop (not really) 16:40:22 I'll mail her one if I can find one! 16:40:35 annegentle: I have about forty billion, no joke 16:40:39 Let me send you some 16:40:44 I don't know what to do with them 16:40:51 also, there's a writer at F5 who presented about treating docs like code who has some OpenStack patches to do, so that's cool. 16:41:05 presented at Write the Docs in Portland Tuesday, I mean 16:41:26 Oh wonderful :D 16:41:29 i also attempted to onboard six people at once on Sunday! 16:41:33 I'm glad there's people still out there paying attention to us 16:41:37 Hence my patches over the weeeknd. 16:41:37 How'd that go annegentle ? :) 16:41:41 I got your email late, I'm so sorry! 16:41:49 grateful to you all helping me merge those :) 16:41:55 also how I found the broken links in the header 16:41:59 so yeah, went really well 16:42:20 annegentle, great! I sometimes see you on "Write the Docs" slack :) 16:42:23 all the usual onboarding headaches with identities and ssh keys 16:42:26 ianychoi yeah! 16:43:41 annegentle: ugh noooo. One day we'll have to make that better 16:43:46 Guess that isn't going to happen tomorrow :P 16:43:51 heh, nope 16:44:38 Alright, well, I think we're pretty much done here 16:44:41 ANything else folkks? 16:44:47 Pass on the word that this is the new improved meeting time 16:44:52 How does this work for people? 16:44:57 improved indeed. 16:46:09 asettle: thanks for the review :) 16:46:19 great except for double (was triple) booking... heh 16:46:20 Not a problem :) made sense! 16:46:25 Hahaha :) 16:46:50 I can sleep now haha 16:47:43 ALright 16:47:44 BYE GUYS 16:47:48 #endmeeting