21:00:13 #startmeeting docteam 21:00:14 Meeting started Thu Apr 20 21:00:13 2017 UTC and is due to finish in 60 minutes. The chair is asettle. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:17 The meeting name has been set to 'docteam' 21:00:22 #topic Roll call 21:00:27 Yo o/ 21:00:31 o/ 21:00:43 o/ 21:00:47 o/ 21:01:13 howdy 21:01:20 As always, I will wait till 5 past for attendees to appear :) 21:01:21 * annegentle waves 21:01:27 HEy everyone :) 21:02:36 How's everyone on this fine THursday evening? 21:03:37 Here is Friday morning - fine :) 21:03:45 ianychoi: did you even sleep dude? 21:04:11 ha, who needs sleep ianychoi ? 21:04:54 Alright, in case anyone needs it... 21:04:56 #link https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting 21:04:58 Agenda 21:05:06 Let's roll 21:05:08 #topic Action items from the last meeting 21:05:16 asettle, annegentle: I slept with setting many alarm rings :) 21:05:16 Drum roll please 21:05:33 ianychoi nice 21:05:38 No action items. 21:05:41 :) 21:05:51 Right, little bit of summit housekeeping out of hte way first 21:05:53 #topic Countdown to summit 21:06:02 We have a few sessions up, let me list them for you all 21:06:05 Keep them in mind please 21:06:08 Project Update - Documentation: Mon 8, 3:40pm-4:20pm 21:06:12 App Developer Enablement WG BoF: Wed 10, 11:50am-12:30pm 21:06:16 Operations and Administration Guides: Tue 9, 4:40pm-5:20pm 21:06:22 Onboarding Room: Mon 8, 2:00pm-3:30pm with ianychoi and myself 21:06:31 To see the schedule 21:06:32 #link https://www.openstack.org/summit/boston-2017/summit-schedule/ 21:06:42 Now, that's the major stuff happening this time around 21:06:53 ianychoi and I will be planning onboarding probably tomorrow (today) 21:07:02 Olga and Alexander from MIrantis are helping me with the Project Update 21:07:17 App Dev - annegentle it would be helpful if you are able to attend 21:07:30 Flanders would liek to discuss the future of the developer site 21:07:35 asettle oh yeah, I'm not going to Boston after all 21:07:43 Oh nooooo :( 21:07:53 asettle I'll see if I can catch up with Flanders before then though 21:07:58 annegentle, oh noooo :( 21:08:12 annegentle: that would be great. Let me sync you up with some emails and get your thoughts in there. We definitely need you from afar then :) 21:08:19 oh, it's all good... 14 Summits is a lot of them... 21:08:27 Jeez wow 21:08:42 right, so it's nice to have gotten a lot planned out at the PTG 21:08:53 Makes sense :) 21:08:54 Does anyone have any questions about the summit or the forum? 21:09:34 Nope from me 21:09:41 Cool :) well, ping me if you do 21:09:43 do we need onboarding materials done ahead of time? 21:09:52 I saw a few training materials patches going through. 21:09:56 annegentle: yes, we do. If you're able to help or have some ideas... that'd be excellent. 21:10:26 annegentle: I think the onboarding is meant to be designed more for the 'what' of hte project, less of the 'how to contribute' side of things. The upstream university stuff is still around. 21:10:35 Is that still applicable? 21:11:25 #link http://lists.openstack.org/pipermail/openstack-dev/2017-March/114703.html 21:11:30 asettle ah, ok, would it help if I write up "what are app dev docs?" or is the contrib guide enough? 21:11:44 My understanding of onboarding rooms is to help new contributors 21:12:06 annegentle: you know, a little something of a 'what is the app dev docs, and how to contribute' would genuinely be helpful. Something I can say on your behalf. 21:12:07 based on that description, app dev doesn't really have a project per se. Hm, I'll check in with Flanders. 21:12:19 annegentle: app dev kinda comes under us. 21:12:26 Well, Flanders thinks it does. So. So it be. 21:12:35 asettle I can make sure that project teams know what API docs are. And I'll check with Flanders. :) 21:12:48 Because yeah, that needs some finesse 21:12:56 annegentle: that'd be great. Can you loop me in? I'd like to learn and see for myself also. 21:13:01 asettle yep! 21:13:08 Thank you :) I appreciate htat annegentle 21:13:36 So, now... onto the less fun part 21:13:43 #topic OSIC news 21:13:53 I am a member of the Rackspace OSIC team. At the moment, my job is on uncertain grounds. I will update when I know more on my own behalf. I will continue to work as the PTL for the remainder of the Pike release however I would be remiss to say that this hasn't affected us in a big way. 21:14:19 Unfortunately, we have now lost Ianeta who is our HA guide specialty team lead. Anyone interested in stepping up? 21:15:00 On that note, I pass on to loquacities and bmoss :( 21:15:07 oh hi 21:15:22 so, the rackspace OSIC team in australia has been made redundant 21:15:57 that's going to severely impact our ability to achieve things in the docs team for the foreseeable future 21:16:19 of course, we don't know what jobs we will end up getting, so there is a reasonable chance we will find ways to contribute once we have new roles 21:16:39 and obviously we will all be doing our best to contribute as much as possible in the meantime 21:16:52 This means that our Networking, Install, User and Admin, Ops and Arch, and tools leads are all impacted. 21:16:59 yep 21:17:08 I'm so sorry loquacities this is really awful :( 21:17:09 loquacities I know you all are super valuable wherever you land. 21:17:15 thanks annegentle 21:17:28 :( 21:17:34 feel free to retweet in your timezone: https://twitter.com/Loquacities/status/854823222197473280 21:17:44 You've all been such an amazing team - Joseph, Lana, Brian, and Darren 21:17:51 Without all of you, we wouldn't be in the place we are today 21:17:59 thanks asettle 21:18:00 asettle +++ 21:18:07 it was a pleasure to be able to hand the PTL baton to you 21:18:13 loquacities your guidance as PTL and now ex-PTL has been invaluable. 21:18:15 and you're doing in awesome job in trying circumstances 21:18:33 Unfortunately, that does mean that there is going to be some seriously dramatic changes around here :( 21:18:35 THank you, loquacities 21:18:56 i'll send a more detailed note to the ML probably early next week 21:19:02 Thank you loquacities 21:19:11 with some more info about the Install Guide team, and my intentions over the next little while 21:19:21 well, we don't need dramatic, but we will need practical :) 21:19:38 To that, for the record of this meeting, I have emailed loquacities and the Australian's with a proposed ramp down plan. Which loquacities already has covered. 21:20:05 :) 21:20:18 Thank you, loquacities 21:20:34 annegentle: completely right. A practical plan will need to be enacted. I will be working on this in the following week. 21:20:47 We still have 6 months till release. We have time at the very least. 21:21:28 asettle yep, thanks for planning and replanning... 21:21:30 Does anyone have any questions for us? 21:22:38 Okay, well, back to business as usual :( 21:22:39 #topic Speciality teams reports 21:22:48 API with annegentle 21:23:06 So, API -- two things to report 21:23:35 One is, the Foundation web dev team is putting together a framework to map API versions to OpenStack versions in the project navigator 21:23:44 #info Foundation web dev team is putting together a framework to map API versions to OpenStack versions in the project navigator 21:24:23 #info JSON files being collected in https://review.openstack.org/#/c/454691 21:24:25 #link https://review.openstack.org/#/c/454691 21:25:01 Patches are up for cinder, glance, heat, keystone, magnum, manila, nova, swift, though I should probably list the ones that aren't up for ping purposes, ha ha. 21:25:12 That's great annegentle :D 21:25:18 Hahha yeah maybe ;) 21:25:22 That merged, so the webdev team can start testing. 21:25:51 Then the other API project team request is to make sure the teams have active API liaisons 21:26:13 annegentle: should the doc liaison not already be the API liaison? 21:26:18 Didn't see a patch up for that one yet, though. 21:26:41 No definitely needs to be a project contributor / core who can speak to API updates and changes going on. 21:27:10 Liaison to the API working group in this case. Who also often serves as API info expert 21:27:21 annegentle: let's sync up about it? we should definitely be talking about this a little more. Especially in light of the news, we need to be getting them more involved. 21:28:06 asettle sure, they really already are though. 21:28:20 asettle so, not much more optimization needed :) 21:28:43 Okay :) you let me know what i can do 21:29:25 asettle keep communicating across projects! 21:29:34 annegentle: on it boss *salutes* 21:29:57 which you do quite well! :) 21:30:14 I'm just very bossy, mostly. 21:30:26 Okay, sorry, gotta move on :( 21:30:31 So, next up is CLI ref and Config Ref 21:30:34 Which is Kato-san 21:30:47 I have not heard from Kato-san in weeks. Since hte PTG, actually. I've emailed several times. 21:30:49 ANyone know anything? 21:31:16 asettle I was wondering the same, hope all is ok! 21:31:27 I hope so too :( 21:31:37 If anyone hears something from him, please let me know. 21:31:38 i haven't heard anything 21:32:02 Next up is Blair and the Hypervisor Tuning Guide. 21:32:07 Blair's working on this with the science group. 21:32:18 Although in light of recent events, I'm tempted to drop this from our agenda and leave this up to the ops groups. 21:32:57 yeah that makes sense 21:33:00 +1 21:33:15 Okay, I will reach out to Blair and make him aware of recent events. 21:33:31 The responsibility is already his, so, this is just letting it go off our agenda. 21:33:41 Also, on that note, I'm going backwards a little because my brain is backwards today 21:33:59 happens when you live in the northern hemisphere 21:34:00 But if anyone sees sfinucan around, give that guy a massive gold star. He's been doing a *lot* of our config ref updates. 21:34:06 bmoss: ugh mate you have no idea 21:34:12 sweet 21:34:23 yeah, he's been awesome 21:34:25 Which remidns me, bmoss I believe he filed a bug. There's something going wrong with the config updates if you have a chance to look 21:34:44 yep, will do. :) 21:34:46 Thanks bmoss :) 21:34:50 Okay, loquacities install guides 21:34:51 hit me 21:34:58 nothing to report, really 21:35:03 i've been a bit preoccupied ;) 21:35:14 What! How dare you not have Installations on the forefront of your mind at all times. 21:35:32 loquacities understandable! :) 21:35:46 annegentle: I see you're the good cop here 21:35:55 If someone wants to take the Placement API out back and put it out of my misery... 21:35:55 lol 21:36:13 Okay 21:36:23 bmoss: I'll chat to the nova guys in the morning 21:36:24 What's up? 21:36:37 heh is that for cells bmoss ? 21:36:49 oh, just that I can't believe I'm still working on it. 21:36:56 bmoss: ugh neither. 21:37:07 just re: that port vs name bug 21:37:17 Yeah, I should maybe get cdent to look at it 21:37:32 eh, it's cool. I just wanted a moment to moan. ;) 21:37:36 carry on 21:37:39 The floor is yourrsss 21:37:43 It's a safe space 21:37:46 lol 21:37:47 lol 21:37:56 Alright 21:38:03 Networkign Guide - John Davidge 21:38:06 Who isn't here 21:38:11 But is also a part of OSIC 21:38:21 I don't konw what his future is, tbh. He's here with me in the UK and life is pretty uncertain 21:38:32 I've asked him a few days ago to check in with the neutron team on getting another lead for this position 21:38:38 asettle, it seems that Kato-san is busy. I also sent an e-mail to you for asking I18n things. Let's wait for his replies.. 21:38:47 s/you/kato-san 21:38:57 Regardless of the centralisation of the guides, we still need a neutron expert 21:39:02 ianychoi: yes I figured as much. 21:39:33 If anyone knows someone that just absolutely adores neutron and has the time, let me know 21:39:38 Okay, ops and arch darrenc 21:39:53 hiya 21:40:23 darrenc: wassup :) 21:41:05 mornin' darrenc 21:41:14 monring 21:41:18 morning even 21:41:19 Morning :) 21:41:29 darrenc: anything to report? :) 21:41:46 Not a huge amount to report. Ben has updated the storage design section in the Arch Guide 21:42:07 I saw! 21:42:09 and despite the circumstances, I will still be around to work on the guide 21:42:26 darrenc: you are a gem. Thank you. I appreciate that so much. 21:42:36 we slowly plugging away on the guide 21:42:44 no worries :) 21:42:52 we're* 21:43:14 darrenc: appreciate that :) 21:43:20 darrenc thanks 21:43:25 Okay, whoops, gotta got a bit faster 21:43:27 darrenc good on ya 21:43:38 Security Guide - Nathaniel Dillon 21:43:41 I can say that I"m doing update 21:43:44 updates 21:43:53 hyakuhei and I will be working on an action plan in light of recent events 21:44:02 OSIC impacted the security team too 21:44:11 On a new action plan* I should say 21:44:26 Train Guides - Matjaz 21:44:29 Doesn't appear to be here either 21:44:31 Training* 21:44:51 Training labs 21:45:03 I heard from Pranav most recently 21:45:19 He's settled in in Berlin, and is working closely with Roger. But unfortunately does not have hte time to dedicate to OpenStack that he used to :( 21:45:21 oh yeah, i got an email from him a little while ago too 21:45:26 loquacities: yeah? :) 21:45:36 just that he's still trying to work on the parser 21:45:50 Yep, that's what I got too :) 21:45:58 So, hopefully we'll see more of them around. 21:46:03 yep 21:46:04 For a little while yet, anyway 21:46:09 sorry, i have to drop off 21:46:14 cya around everyone o/ 21:46:18 loquacities, have a good Friday! 21:46:18 o/ 21:46:22 loquacities o/ 21:46:23 loquacities: adios! Thanks for coming :) 21:46:35 Admin and User Guides - jrobinson 21:46:37 Any updates? 21:46:47 User Guides - The Glance documentation efforts for the admin guide reached 21:46:48 a good stage, and I've merged the patch. 21:46:48 I have an audit of remaing legacy commands to create, which I can do despite 21:46:48 the circumstances. I can also assist with the ongoing Admin Guide migration. 21:47:11 Thank you for your dedication jrobinson :) 21:47:13 I really appreciate that 21:47:30 jrobinson thanks Joe! 21:47:35 jrobinson I do like how it is shaping up 21:48:13 I'm predicting I should be okay to continue, even if in a reduced capacity somewhat. 21:48:22 That's really great :) 21:48:23 That's all from me today :). 21:48:31 Last, but not least, bmoss and tools 21:48:40 The main thing to report from the last couple of weeks is that we now have a Pike spec up for the doc-tools and theme to support Python 3.5: 21:48:40 #link https://blueprints.launchpad.net/openstack-doc-tools/+spec/support-python3.5 21:49:09 nice bmoss 21:49:12 Cool 21:49:30 the future is here! 21:49:31 What do we need to be doing, bmoss ? 21:50:03 basically we need to make sure that our code works under Python 3.5 21:50:17 It shouldn't require any major changes 21:50:21 Coolio hoolio :) 21:50:36 at the same time, I will probably try to enhance the test suite 21:50:48 That would be great, bmoss :) 21:50:48 since that is the easiest way to catch version-related issues 21:51:27 Great 21:51:30 bmoss thanks for working on the sitemap tests too 21:51:35 Thank you :) 21:51:40 no worries :) 21:51:50 Okay, we have a little time left 21:51:53 Just want to quickly talk about 21:51:54 bmoss one thing I'm not sure of is releasing the theme? 21:51:58 Oops 21:51:59 Sorry annegentle 21:52:00 openstackdocstheme I mean 21:52:08 asettle no worries, was typing as fast as I could :) 21:52:16 bmoss I can ask olga too 21:52:51 annegentle, do you mean what is the process for releasing it? 21:53:15 bmoss more like, are you and Mariia still up for releasing stuff? 21:53:54 I think our official Ocata duties are probably done, but I'm totally happy to release the theme. 21:54:10 or the tools, for that matter. 21:54:21 bmoss if you're up for it, that would be super helpful to get work going on that spec 21:54:25 though I don't know if the spec landed yet? 21:54:39 #link https://review.openstack.org/#/c/454346/ 21:55:06 I can fix the bullets, good catch bmoss 21:55:12 Weird. I haven't seen this. 21:55:26 ah yes, let's get that spec merged. It would be great to move forward with the unification of the themes. 21:55:47 annegentle: on board. Ping me when you want that +2 (or if you want it) 21:55:52 asettle ok thanks! 21:56:07 asettle yeah I meant to bring it up during the spec review agenda item today anyway 21:56:08 Sorry for not seeing that sooner 21:56:16 Speaking of 21:56:20 We have 4 minutes left 21:56:25 #topic Open Discussion 21:56:27 annegentle, just on the earlier point - checking through my notes, I can go create the blueprint to start the migration. 21:56:33 Sorry, I have to skip. But if anyone has any specs, or news, please let's chat now 21:56:34 annegentle, so just let me know when the theme should go out and we'll make it happen. 21:56:58 bmoss cool, thanks 21:57:03 And thanks, as well :). 21:57:27 +2 annegentle 21:57:33 Also, for those that haven't seen 21:57:35 #link https://governance.openstack.org/tc/reference/tags/docs_follows-policy.html 21:57:38 bmoss ok, merged https://review.openstack.org/#/c/454448 21:57:48 asettle nice work there! governance, indeed! 21:57:58 We are to govern the people! 21:58:00 Well 21:58:01 :) 21:58:02 Not really 21:58:18 sweet, thanks annegentle! 21:58:21 Would be cool for people to review the guidelines 21:58:23 #link https://review.openstack.org/#/c/453642/ 21:58:26 Great with an official tag! 21:59:32 Okay, one minute 21:59:35 ANything else people? :) 22:00:10 nope 22:00:18 Nothing further from me. 22:00:19 Nope 22:00:28 nothing from me 22:00:38 You're an amazing team, and I appreciate all the wonderful work you're all doing 22:00:41 I hope you all know that 22:00:45 +2 22:00:46 Let me know what I can do to support you al 22:00:50 We'll get through this <3 22:00:53 +1 :) 22:00:57 why does al get all the love? 22:01:14 Your'e the worst :p 22:01:21 ;) 22:01:22 Piss of, the lot of ya <3 :P 22:01:26 #endmeeting