Jump to: navigation, search

Difference between revisions of "Meetings/DocTeamMeeting"

(Agenda for next meeting)
Line 14: Line 14:
  
 
* #topic Action items from the last meeting
 
* #topic Action items from the last meeting
** #action Review admin guide spec
+
** None on the meeting minutes.
*** #link https://review.openstack.org/#/c/439122/
 
  
 
* #topic Countdown to summit:  
 
* #topic Countdown to summit:  
 +
** Keep an eye out for the docs and I18n have a project onboarding room at the summit.
 +
** Melvin Hillsman (mrhillsman) of the User Committee submitted a forum topic for the Ops Guide to get operator feedback
 +
** David Flanders from the Foundation has also proposed a forum topic for developer.openstack.org (which currently houses our API, SDK, and other dev stuff). We'll be discussing major changes to that and would like to see some feedback from people here. Any questions on that, shoot it my way. My main objective for this forum topic is to reduce our current technical debt that lives on this site.
 +
** For more information on forum topics:
 +
** #link https://wiki.openstack.org/wiki/Forum
 
** Schedule has been released: https://www.openstack.org/summit/boston-2017/summit-schedule/
 
** Schedule has been released: https://www.openstack.org/summit/boston-2017/summit-schedule/
** Docs and I18n have a project onboarding room at the summit, keep an eye out on the dev ML for more information. Kendall will inform us when the time comes. Anyone around to help me (asettle) with that?
 
** #link http://lists.openstack.org/pipermail/openstack-dev/2017-March/114149.html
 
** Docs project update will be delivered by me (asettle) on Mon 8 , 3:40pm-4:20pm.
 
** #link https://www.openstack.org/summit/boston-2017/summit-schedule/global-search?t=Alexandra+Settle
 
  
 
* #topic PTL report:
 
* #topic PTL report:
** I am (asettle) in the process of drafting a governance tag for our install guides. Would be great for everyone to review and understand what the process will involve.
+
** I (asettle) still in the process of drafting a governance tag for our guides called "docs:follows-policy". I have been working with Doug Hellmann (dhellmann) in the last week to change to draft dramatically, so it would be good for docs people to review again. We are trying to make this a more broad tag now, so it can be applied for other guides too.
 
** #link https://review.openstack.org/#/c/445536/
 
** #link https://review.openstack.org/#/c/445536/
 +
** I am also in the process of documenting guidelines in our Contrib Guide - which would also benefit from doc reviews.
 +
** #link https://review.openstack.org/#/c/453642/
  
 
* #topic Speciality teams reports:
 
* #topic Speciality teams reports:
Line 33: Line 35:
 
** High Availability Guide: Ianeta Hutchinson
 
** High Availability Guide: Ianeta Hutchinson
 
** Hypervisor Tuning Guide: Blair Bethwaite
 
** Hypervisor Tuning Guide: Blair Bethwaite
** Installation guides: Lana Brindley
+
** Installation guides: Lana Brindley - We have now branched, so please remember to backport if you have edits to the Ocata guide now. Big thanks to all the testers who have been working hard over the past month or two (that Nova cells bug was *tough*!), and to Brian and Mariia for doing the heavy lifting. Noticed a bunch links to draft versions of the guide in Newton/Ocata branches, backports for that have been merged, and the Contributor Guide updated so we don't miss it in the future (https://docs.openstack.org/contributor guide/release/taskdetail.html#update-links-in-all-books).
 
** Networking Guide: John Davidge
 
** Networking Guide: John Davidge
 
** Operations and Architecture Design guides: Darren Chan
 
** Operations and Architecture Design guides: Darren Chan
Line 43: Line 45:
  
 
* #topic Bug triaging
 
* #topic Bug triaging
** Two more volunteers required to fill out the schedule for the entire release. Thanks everyone for getting on board.
+
** One more volunteer required (14 Aug - 28 Aug) to fill out the schedule for the entire release. Thanks everyone for getting on board.
 
** #link https://wiki.openstack.org/wiki/Documentation/SpecialityTeams#Bug_Triage_Team
 
** #link https://wiki.openstack.org/wiki/Documentation/SpecialityTeams#Bug_Triage_Team
** Ianeta has been doing a great job this week, thank you Ianeta!
+
** Lana has been doing a great job this week, thank you Lana!
** Next up is Lana from the 10th of April :)
+
** Lana's report: Overall, went well. Zero new bugs on Wednesday (before I went on PTO). I would like to get some eyeballs on https://bugs.launchpad.net/openstack-manuals/+bug/1676875 (re: Block Storage in the Install Guide), I've got a WIP patch here: https://review.openstack.org/452581 Jay Bryant from cinder is taking a look while Sean McGinnis is on holidays.
 +
** Next up is Alex for the 10 Apr - 24 Apr
  
 
* #topic Open discussion
 
* #topic Open discussion

Revision as of 10:55, 6 April 2017

Documentation team meeting

Every two weeks (on even weeks) on Thursday at 2100 UTC in #openstack-meeting-alt https://www.timeanddate.com/countdown/newyear?p0=24&msg=Pike+release&ud=1&font=slab

This meeting is used to discuss the status of the various docs speciality teams, as well as general docs updates. If you're looking to get started with documentation, or need to discuss work on a particular book, this is the place to do that.

Please feel free to add items to the agenda below and we'll cover them.

Agenda for next meeting

When starting the meeting, use #startmeeting docteam to provide consistency.

  • #topic Action items from the last meeting
    • None on the meeting minutes.
  • #topic Countdown to summit:
    • Keep an eye out for the docs and I18n have a project onboarding room at the summit.
    • Melvin Hillsman (mrhillsman) of the User Committee submitted a forum topic for the Ops Guide to get operator feedback
    • David Flanders from the Foundation has also proposed a forum topic for developer.openstack.org (which currently houses our API, SDK, and other dev stuff). We'll be discussing major changes to that and would like to see some feedback from people here. Any questions on that, shoot it my way. My main objective for this forum topic is to reduce our current technical debt that lives on this site.
    • For more information on forum topics:
    • #link https://wiki.openstack.org/wiki/Forum
    • Schedule has been released: https://www.openstack.org/summit/boston-2017/summit-schedule/
  • #topic PTL report:
    • I (asettle) still in the process of drafting a governance tag for our guides called "docs:follows-policy". I have been working with Doug Hellmann (dhellmann) in the last week to change to draft dramatically, so it would be good for docs people to review again. We are trying to make this a more broad tag now, so it can be applied for other guides too.
    • #link https://review.openstack.org/#/c/445536/
    • I am also in the process of documenting guidelines in our Contrib Guide - which would also benefit from doc reviews.
    • #link https://review.openstack.org/#/c/453642/
  • #topic Speciality teams reports:
    • API: Anne Gentle
    • Configuration Reference and CLI Reference: Tomoyuki Kato
    • High Availability Guide: Ianeta Hutchinson
    • Hypervisor Tuning Guide: Blair Bethwaite
    • Installation guides: Lana Brindley - We have now branched, so please remember to backport if you have edits to the Ocata guide now. Big thanks to all the testers who have been working hard over the past month or two (that Nova cells bug was *tough*!), and to Brian and Mariia for doing the heavy lifting. Noticed a bunch links to draft versions of the guide in Newton/Ocata branches, backports for that have been merged, and the Contributor Guide updated so we don't miss it in the future (https://docs.openstack.org/contributor guide/release/taskdetail.html#update-links-in-all-books).
    • Networking Guide: John Davidge
    • Operations and Architecture Design guides: Darren Chan
    • Security Guide: Nathaniel Dillon
    • Training Guides: Matjaz Pancur
    • Training labs: Pranav Salunke, Roger Luethi
    • Admin and User guides: Joseph Robinson
    • Docs theme and tools: Brian Moss
  • #topic Open discussion

Apologies for absence

  • Alex (asettle) - busy pretending OpenStack doesn't exist in Italy :P The above agenda has been pre-updated by me.

Previous meetings

Previous meetings, with their notes and logs, can be found here: http://eavesdrop.openstack.org/meetings/docteam/

Running Meetings

Public meetings are run in IRC; we use MeetBot syntax to note what happens during the meeting. http://meetbot.debian.net/Manual.html

Useː

  • #startmeeting docteam
  • #topic <item>, for each agenda item that is being addressed
  • #link <url>, for relevant meeting URLs
  • #info <info> for important notes that need to be added to the minutes
  • #action <item>, to note tasks for a specific person
  • #endmeeting

Office hours

We no longer hold formal office hours, but if you would like to walk through documentation processes, learn about the tools, or report a doc bug, feel free to come by the IRC channel at #openstack-doc at any time. You can also open discussions by emailing the openstack-docs@lists.openstack.org mailing list.