21:00:04 <loquacities> #startmeeting docteam
21:00:05 <openstack> Meeting started Thu Nov 17 21:00:04 2016 UTC and is due to finish in 60 minutes.  The chair is loquacities. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:06 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:08 <openstack> The meeting name has been set to 'docteam'
21:00:19 <loquacities> who do we have here?
21:00:25 <cathrichardson> o/
21:00:31 <iphutch> Good Morning
21:00:32 <loquacities> heya cathrichardson :)
21:00:35 <loquacities> hi iphutch
21:00:35 <rluethi> hi there
21:00:35 <alex_bash> o/
21:00:41 <loquacities> ooh, everyone is here!
21:00:46 <loquacities> hi rluethi and alex_bash
21:00:48 <lutz_> Hi Lana this is Lutz
21:00:54 <loquacities> hi lutz_
21:00:55 <bmoss> hey hey
21:00:59 <loquacities> hi bmoss
21:01:29 <loquacities> for the record ...
21:01:35 <loquacities> agenda is here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting
21:01:45 <loquacities> #topic Action items from the last meeting
21:01:59 <loquacities> since this is our first ocata meeting, i think we can safely assume there are none ;)
21:02:01 <loquacities> so moving on ...
21:02:07 <loquacities> #topic Specs in review #link https://review.openstack.org/#/q/status:open+project:openstack/docs-specs,n,z
21:02:24 <loquacities> we have five here
21:02:37 <loquacities> #link https://review.openstack.org/#/c/391548/
21:02:37 <loquacities> training-labs: Rewrite training-labs in python
21:03:01 <loquacities> doesn't look like  pranav is here, does anyone else have on opinion on this?
21:03:14 <loquacities> rluethi ^^ ?
21:03:28 <rluethi> sorry. is that the python port review?
21:03:33 <loquacities> yep
21:03:38 <JRobinson__> "Moving to a modern programming language addresses
21:03:38 <JRobinson__> many inherent limitations of Bash for the given use-cases"
21:03:57 <JRobinson__> that's a good argument.
21:04:22 <loquacities> ok, let's move on
21:04:29 <rluethi> Pranav and I have some things to clarify there. It will hopefully happen before the end of the weekend.
21:04:37 <loquacities> #link https://review.openstack.org/#/c/391786/ Proposed use case form
21:04:42 <loquacities> rluethi: ok, cool
21:05:09 <loquacities> so this one was discussed at summit
21:05:18 <loquacities> any ops people around can comment?
21:05:41 <loquacities> it's about using a web form to collect use case info from ops
21:05:50 <loquacities> just a way of collecting source data for the ops guide, basically
21:05:58 <darrenc> Shaun is going to post his thoughts on the docs ML
21:06:01 <loquacities> and reducing the amount of overhead for ops to get that to us
21:06:07 <loquacities> darrenc: ok, easy,  thanks :)
21:06:12 <loquacities> next up
21:06:23 <loquacities> #link https://review.openstack.org/#/c/392372/ [arch-design] Revise the Architecture Design Guide
21:06:34 <lutz_> +1 anything that makes it easier for ops to report issues in certain use cases should be worthwhile
21:06:48 <loquacities> lutz_: i agree!
21:07:11 <loquacities> darrenc: maybe you can talk to the arch guide spec?
21:07:28 <darrenc> yep, so this is basically the same spec last cycle
21:07:55 <darrenc> The only change is refining the use cases chapter
21:08:02 <loquacities> right
21:08:08 <loquacities> looks like it's about ready to be approved?
21:08:09 <darrenc> so I think we can push this one through
21:08:11 <darrenc> yep
21:08:22 <loquacities> ok, i'll put my +2 on, then we just need shilla to merge it
21:08:30 <darrenc> thanks :)
21:08:53 <loquacities> done
21:08:59 <loquacities> next up
21:09:06 <loquacities> #link https://review.openstack.org/#/c/394261/ [ops-guide] Add project upgrade notes
21:09:13 <loquacities> darrenc: i believe that's you again :P
21:09:20 <darrenc> yep :)
21:09:42 <darrenc> so the proposal is to migrate project upgrade notes to the Ops Guide
21:10:09 <darrenc> but I think there is some resistance from projects
21:10:24 <loquacities> yeah, seems that way
21:10:27 <loquacities> what do you need?
21:10:54 <darrenc> well, just finding a happy medium for ops and projects
21:11:00 <loquacities> right, ok
21:11:06 <loquacities> maybe bring it up on the ops ML?
21:11:10 <loquacities> cc the docs ML?
21:11:20 <darrenc> I think linking to the upgrade content might suffice
21:11:29 <darrenc> yep, I'll do that
21:11:32 <loquacities> ok
21:11:33 <loquacities> cool
21:11:45 <loquacities> and lucky last:
21:11:58 <loquacities> #link https://review.openstack.org/#/c/390324/ Changed the home-page link for docs-specs
21:12:32 <loquacities> oh, that's not a spec
21:12:34 <loquacities> my bad
21:12:47 <JRobinson__> Looks like devising a cookie cutter standard similar to the install guide for ops upgrade content - on a smaller scale -  might help address Michael D's concern. Maybe. Ml discussion will bring some attention.
21:13:05 <loquacities> JRobinson__: agreed
21:13:05 <JRobinson__> sorry, Michal D.
21:13:10 <loquacities> ok, let's move on
21:13:17 <loquacities> #topic Speciality teams reports:
21:13:28 <loquacities> #info API: Anne Gentle
21:13:36 <loquacities> anne can't be here, so let me copypaste
21:13:44 <loquacities> Karen Bradshaw has been working on updates to the openstackdocstheme that would fix this bug: https://launchpad.net/bugs/1583623. The review is up at https://review.openstack.org/#/c/393890/ and getting input from the affected teams who have recognized the need because of errors building when you have multiple API versions with very similar calls, so you end up with identical headings.
21:13:44 <openstack> Launchpad bug 1583623 in openstack-doc-tools "os-api-ref: duplicate labels for selectors" [Low,In progress] - Assigned to Karen Bradshaw (kbhawkey)
21:13:44 <loquacities> I've had a couple of inquiries on IRC about "where did the draft/swagger files go?" but to meet their stated end goals, those particular files wouldn't have worked any way due to inaccuracies in the content and incomplete content.
21:13:44 <loquacities> See the 100 api-ref doc patches up for review at: https://review.openstack.org/#/q/status:open+file:api-ref.
21:14:40 <loquacities> no questions on that?
21:14:49 <loquacities> #info Configuration Reference and CLI Reference: Tomoyuki Kato
21:15:12 <loquacities> i think katomo isn't here, but i don't have an update from him
21:15:23 <loquacities> any questions/issues on config & cli ref?
21:15:43 <JRobinson__> No questions at the moment.
21:15:59 <loquacities> #info High Availability Guide: Andrew Beekhof
21:16:09 <loquacities> i don't have an update from andrew, either
21:16:13 <loquacities> are  you here, andrew?
21:16:33 <loquacities> i'll take that as a no :P
21:16:42 <loquacities> #info Installation guides: Lana Brindley
21:16:48 <loquacities> that be me
21:17:02 <loquacities> so, no major updates to the guides themselves, but we are planning updates to the landing page
21:17:17 <loquacities> we're also working on getting our first deployment guide landed there
21:17:22 <loquacities> with openstack ansible
21:17:57 <loquacities> i've requested design resources from foundation, but haven't heard back yet
21:18:10 <loquacities> so if you have ideas/suggestions (or design skillz!) then please let me know :)
21:18:16 <loquacities> questions on the install guide?
21:18:44 <loquacities> #info Networking Guide: John Davidge
21:18:45 <JRobinson__> No questions, signal boosting the designer skills item though
21:18:51 <loquacities> thanks JRobinson__
21:18:59 <loquacities> ok, john isn't here, i have his report:
21:19:21 <loquacities> As for my update - not much to report. A couple of new articles are close to merging:
21:19:21 <loquacities> https://review.openstack.org/#/c/361776/ - VLAN Trunking
21:19:21 <loquacities> https://review.openstack.org/#/c/356013/ - Routed Provider Networks
21:19:21 <loquacities> Need to decide how best to track the work that�s going on for:
21:19:21 <loquacities> https://blueprints.launchpad.net/openstack-manuals/+spec/use-openstack-comm
21:19:22 <loquacities> Probably a google spreadsheet or ether pad with a list of all the network guide pages to be converted, and the person working on it would be best. That way we can hopefully avoid duplicating efforts.
21:20:11 <loquacities> ok, questions on networking?
21:20:31 <bmoss> loquacities, that blueprint link doesn't seem to work for me
21:20:32 <loquacities> #info Operations and Architecture Design guides: Shilla Saebi
21:20:52 <loquacities> bmoss: ah, one sec
21:21:01 <bmoss> oh, I see. Should be 'command' at the end
21:21:04 <loquacities> https://blueprints.launchpad.net/openstack-manuals/+spec/use-openstack-command
21:21:10 <loquacities> yep, copypasta on my behalf, sorry
21:21:20 <loquacities> my email client broke it
21:21:33 <bmoss> no worries. Got it now. :)
21:21:36 <loquacities> yay!
21:21:43 <loquacities> darrenc: are you acting as shilla's proxy today?
21:21:51 <loquacities> can you give us an  ops/arch update?
21:21:55 <darrenc> I guess so :)
21:21:59 <loquacities> :P
21:22:25 <darrenc> We're slowly making progress with the arch guide
21:22:34 <darrenc> and have cloudnull onboard to help
21:22:40 <loquacities> oh, great!
21:23:21 <darrenc> So the focus is completing the design chapter and migrating stuff from the ops guide
21:23:54 <darrenc> that's all :)
21:24:00 <loquacities> cool, thanks darrenc :)
21:24:06 <loquacities> any questions on ops/arch?
21:24:28 <loquacities> #info Security Guide: Nathaniel Dillon
21:24:43 <loquacities> doesn't look as though nathaniel is here
21:24:58 <loquacities> #info Training Guides: Matjaz Pancur
21:25:14 <loquacities> from matjaz:
21:25:16 <loquacities> - we changed our IRC meeting to every two weeks (on even weeks) on Tuesday at 1300 UTC in #openstack-meeting-3 - there will be an article published about BCN Upstream training in OpenStack�s Superuser magazine - BCN Upstream training retrospective https://etherpad.openstack.org/p/upstream-training-barcelona-retrospective
21:25:29 <loquacities> questions on training guides?
21:25:43 <loquacities> #info Training labs: Pranav Salunke, Roger Luethi
21:25:53 <loquacities> rluethi: do you have an update?
21:26:06 <rluethi> we have the python port already under review.
21:26:27 <rluethi> yes, the spec is not done yet, either.
21:26:34 <loquacities> heh, always the way :P
21:26:56 <rluethi> We hope to get them merged soonish and in the right order :)
21:27:07 <loquacities> awesome
21:27:10 <loquacities> thanks :)
21:27:15 <loquacities> and, last but not least:
21:27:21 <loquacities> #info User guides: Joseph Robinson
21:27:25 <loquacities> JRobinson__: what do you have for us?
21:27:28 <JRobinson__> #link https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides#Ocata_Tasks
21:27:41 <JRobinson__> This the current work on converting the legacy commands to OS commands
21:27:50 <loquacities> looks like it's well underway
21:27:57 <loquacities> i know i've seen a lot patches
21:28:18 <JRobinson__> Thanks to csatari and visnyei and allen, there's progress happening.
21:28:26 <loquacities> great :)
21:28:39 <JRobinson__> I need to finish adding the files affected to the checklist, and then also start making changes.
21:28:40 <darrenc> Is there a tracking page?
21:29:04 <JRobinson__> #link https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides#Legacy_to_OpenStack_command_conversion_table
21:29:07 <darrenc> ignore me
21:29:10 <JRobinson__> link to the specific table^
21:29:26 <JRobinson__> I had thought that it might have a bit too many details, but it seems to be clear so far.
21:29:58 <darrenc> Perhaps mention it on the mailing list?
21:30:02 <JRobinson__> Apart from this tasks, keeping track of any admin or user guide bugs is also a task.
21:30:05 <loquacities> yeah, that's a good ideea
21:30:14 <JRobinson__> Good idea, definitely.
21:30:14 <darrenc> Because I've seen a few duplicate patches
21:30:41 <JRobinson__> #action Send out another User Guides update email, with current conversion task list.
21:30:51 <loquacities> you need a person on the action
21:31:08 <loquacities> #action JRobinson__ Send out another User Guides update email, with current conversion task list.
21:31:14 <JRobinson__> Should be my nic there, thanks :)
21:31:19 <loquacities> np :)
21:31:28 <loquacities> ok, are we all done with speciality teams?
21:31:47 <loquacities> let's move on
21:31:51 <loquacities> #topic Countdown to release:
21:31:59 <loquacities> #info 96 days to go!
21:32:23 <loquacities> that's scary, because US thanksgiving is next week, followed by christmas, new year, etc
21:32:28 <loquacities> release day is 22 feb
21:32:43 <loquacities> our deliverables list is correspondingly short, though
21:32:49 <loquacities> #link https://wiki.openstack.org/wiki/Documentation/OcataDeliverables
21:33:12 <loquacities> does anyone have questions on release things or deliverables?
21:33:19 <ianychoi> Hi yep including generating PDFs
21:33:32 <loquacities> yep!
21:34:08 <ianychoi> For generating PDFs, I will update a spec: changing from rst2pdf to latex
21:34:10 <lutz_> at least for the install tutorial its already in the list
21:34:10 <ianychoi> #link http://specs.openstack.org/openstack/docs-specs/specs/ocata/build-pdf-from-rst-guides.html
21:34:17 <ianychoi> #link https://review.openstack.org/#/c/396943/
21:34:23 <lutz_> +1 for LaTeX from me!
21:34:35 <loquacities> <3 LaTeX :)
21:34:39 <ianychoi> since rst2pdf is not working well unfortunately
21:34:44 <loquacities> ah, ok
21:34:50 <loquacities> cool, i'm glad there's progress on this
21:35:09 <ianychoi> Thanks :)
21:35:11 <loquacities> really, generating PDFs is for all books, not just install, but that's ok
21:35:15 <loquacities> we need to start somewhere
21:35:20 <lutz_> if there are any problems with latex just shoot me an email or so
21:35:36 <loquacities> ok, let's move on
21:35:38 <lutz_> having done quit e abit with latex in the past
21:35:41 <ianychoi> lutz_, wow good thanks!
21:35:49 <loquacities> #topic PTG Atlanta Feb 20-24 2017
21:35:57 <loquacities> #link http://www.openstack.org/ptg Event info
21:36:02 <loquacities> #link https://pikeptg.eventbrite.com/ Tickets
21:36:09 <loquacities> #info Docs is on Monday/Tuesday
21:36:13 <loquacities> so, who's going?
21:36:25 <loquacities> or, who thinks they might go? ;)
21:36:49 <ianychoi> I will go there (as I18n)
21:36:51 <JRobinson__> Yes if possible.
21:36:55 <ianychoi> + Docs :)
21:36:55 <loquacities> awesome :)
21:37:01 <loquacities> :)
21:37:07 <skelso> Yes if approved. Request is in.
21:37:11 <bmoss> I'm hoping I'll be there.
21:37:24 <loquacities> cool!
21:37:44 <loquacities> ok, that's brings us around to ...
21:37:48 <loquacities> #topic Open discussion
21:38:02 <loquacities> anything else?
21:39:10 <loquacities> ok, i think that this was a successful first meeting under the new arrangement!
21:39:18 <loquacities> thanks everyone for coming and participating :)
21:39:29 <loquacities> i'll put out a newsletter this afternoon, with all these updates in it
21:39:48 <JRobinson__> Thanks loquacities :)
21:39:48 <ianychoi> I have just woke up it is now 6:40 am here but fine to me :)
21:39:54 <darrenc> thanks loquacities
21:39:56 <bmoss> thanks everyone
21:39:56 <ianychoi> Thanks loquacities !
21:40:01 <ianychoi> and everyone
21:40:07 <lutz_> thanks all
21:40:07 <iphutch> Thanks all
21:40:09 <loquacities> thanks for getting up early ianychoi (and everyone else who did!)
21:40:22 <loquacities> #endmeeting