22:10:25 <JRobinson__> #startmeeting docsuserguides
22:10:26 <openstack> Meeting started Wed Feb 10 22:10:25 2016 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:10:27 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:10:29 <openstack> The meeting name has been set to 'docsuserguides'
22:10:43 <JRobinson__> Morning all o/ , or afternoon
22:10:50 <JRobinson__> Great that this worked.
22:10:55 <JRobinson__> First agenda item
22:11:21 <JRobinson__> #Action JRobinson__ to update the User Guide meeting times to reserve this earlier space
22:11:28 <gmolson> Hi Joseph!
22:11:45 <JRobinson__> #action JRobinson__ to update the User Guide meeting times to reserve this earlier space
22:11:51 <JRobinson__> There, fixed^
22:11:58 <JRobinson__> gmolson, o/ hello!
22:12:00 <gmolson> sweet!
22:13:34 <JRobinson__> #topic High priority items
22:14:05 <JRobinson__> gmolson, I mentioned the high priority item was looking for places in the Cloud Admin doc for Admin User Guide content
22:14:16 <JRobinson__> Since the overall goal is to merge the two into one Administrator Guide
22:14:23 <gmolson> Yes, I saw you mentioned that in your note
22:14:57 <gmolson> right
22:15:07 <JRobinson__> Okay, so I started doing that in my patches, however I don't have a file list set up
22:15:58 <gmolson> so, are the patches that you've done it in noted in the blueprint?
22:16:05 <JRobinson__> ^with the sub goal being to go through each file in the repo, and cross it off when there's a place for it in Cloud admin guide.
22:17:02 <JRobinson__> gmolson, the patches done so far should be referenced on the blueprint page since it tracks patches that reference it.
22:17:07 <JRobinson__> I'll post the link
22:17:32 <gmolson> JRobinson__, ok
22:19:13 <JRobinson__> #link https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorganised
22:19:29 <JRobinson__> The whiteboard heading contains all the patches done so far I beleive
22:19:38 <JRobinson__> s/believe
22:20:47 <gmolson> JRobinson__, thanks! Ok. Good to know.
22:21:19 <JRobinson__> I think this is a decent example:
22:21:22 <JRobinson__> #link https://review.openstack.org/#/c/258772/
22:21:39 <JRobinson__> I moved compute chapter content from the Admin guide to the Cloud admin in this one.
22:22:07 <JRobinson__> So an action for me this week,
22:22:10 <gmolson> cool - thanks for the example
22:22:29 <rocky_g> question:  There is work being done to generate each project's config options int RST via oslo.sphynx  Is this something that would help here?
22:22:44 <JRobinson__> #action add file names to the task list, and suggestions of where they can fit into the Cloud Admin.
22:24:05 <JRobinson__> rocky_g, that's a good question, I'm not sure. I think that affects the config reference. The User Guides only have specific references to project command line items
22:25:14 <rocky_g> Yeah.  I know I need to ping the config ref team.  But I saw some LBAAS config references in the list of reviews in the BP you just posted.  That's why I asked, but just spreading some info.
22:25:44 <gmolson> JRobinson__, so it looks like you are putting each dashboard task into the related service area, rather than creating a new topic under Dashboard with all of the topics, something like Managing with the Dashboard...
22:26:16 <JRobinson__> rocky_g, good point, thanks for checking the link.
22:26:51 <rocky_g> I'll just lurk now :-)
22:27:30 <JRobinson__> gmolson, yes I started organising it that way so far. My Information Architecture insight is not too strong here.
22:28:06 <JRobinson__> rocky_g, np, I'll look into though, it may be a helpful thing :)
22:29:52 <gmolson> Ok, yeah. I am still getting to know the guides. It might be an easy way to consolidate the Dashboard tasks...
22:29:54 <JRobinson__> gmolson, glancing at the contents page, moving the Admin Guide dashboard items to the Cloud admin dashboard chapter would save a lot of time.
22:30:21 <gmolson> right, and a user could find all of the tasks in one spot
22:31:23 <JRobinson__> ^Yes, definitely:
22:31:55 <JRobinson__> #info Dashboard related content in the Admin User Guide can move to the Cloud Admin Dashboard chapter to create one place for users.
22:32:14 <gmolson> I like it
22:32:32 <JRobinson__> Okay, so I'll add that to the task list on the page, and start adding a list of files so we can check them off once they are moved.
22:32:49 <gmolson> ok
22:33:03 <gmolson> do you add / and delete the file in one commit? How does that work?
22:34:22 <JRobinson__> The process I followed so far is; copy the admin file contents of one specific topic/service (compute and images for example)
22:34:36 <JRobinson__> Then add it to the Cloud Admin document.
22:34:43 <JRobinson__> And leave the original in place for now.
22:34:58 <gmolson> ok
22:35:15 <JRobinson__> An future item is to deactivate the Admin user guide once everything has a place in the Cloud admin  document.
22:35:24 <gmolson> sure
22:35:34 <JRobinson__> Then the Cloud admin guide has a title change.
22:35:42 <gmolson> ok
22:36:05 <JRobinson__> Most likely links will need an update, which happened after the rst conversion.
22:36:42 <JRobinson__> I should record that procedure so others can see what the plan is
22:36:56 <JRobinson__> #action add procedure for combining the docs to the team page
22:37:17 <gmolson> great - yes, that sounds helpful
22:37:50 <JRobinson__> Anything else for High priority items? I think that covers all the points I had.
22:38:10 <gmolson> I don't have other high priority items...
22:38:33 <gmolson> You'd like to get this conversion done first, and then complete the other content items that are listed in the blueprint, correct?
22:39:03 <JRobinson__> gmolson, yes that's right.
22:39:08 <gmolson> ok
22:40:49 <JRobinson__> I hope it doesn't confuse too much, but if new contributors what to make small change, then addressing the typos/passive voice/ task list items is okay as well.
22:41:25 <gmolson> ok
22:41:34 <JRobinson__> ^That's just a 'what if new contributors are looking for a place to start' for instance
22:41:43 <gmolson> sure
22:42:59 <JRobinson__> Anyway, next action item was on exemplars, but I'm taking that down, and skipping directly to the collaboration point
22:43:36 <JRobinson__> #topic Check in with Murano, Trove, Sahara, Magneto, and other services
22:44:11 <JRobinson__> Late last year I contacted the docs liasons for these teams asking about new User Guide content from their services.
22:44:45 <JRobinson__> I had some feedback, and I need to follow up with the liaisons.
22:45:09 <JRobinson__> Sitting in on their speciality team IRC meetings might be needed.
22:45:20 <gmolson> ok
22:45:24 <JRobinson__> That's all I had for that though.
22:45:33 <gmolson> ok
22:45:49 <JRobinson__> #action check in with docs liaisons for other projects not currently in the User Guides
22:46:36 <JRobinson__> gmolson, that was all for this meeting. Any questions or comments ?
22:46:45 <rocky_g> So, the config opts is an Oslo thing.  Definitely check in with Oslo as they are corralling multiple projects into consistent directions/tools/libraries.  Also, Nova is doing lots of cleanup work that will impact docs.
22:48:10 <gmolson> JRobinson__, no more questions / comments from me. Thanks for rearranging the mtg time today!
22:48:31 <JRobinson__> rocky_g, I think Oslo came up as a team to ask about re: checking in with docs liaisons for User Guide content. Thanks for the heads up here on the incoming changes :)
22:48:55 <JRobinson__> gmolson, thanks very much for joining :) No worries.
22:49:07 <rocky_g> Yup. NP.  hard to keep up on everything and actually get work done;-)  Especially docs work.
22:49:08 <gmolson> o/
22:49:16 <JRobinson__> #topic open discussion
22:49:43 <JRobinson__> #action contact Oslo team, contact Nova team - clean up work and consistent directions/tools/libraries
22:49:50 <JRobinson__> okay, I'll call it there
22:49:53 <JRobinson__> #endmeeting