Jump to: navigation, search

Difference between revisions of "Meetings/DocTeamMeeting"

(Apologies for absence)
 
(42 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{OpenStack_Documentation_Navbar}}
 
{{OpenStack_Documentation_Navbar}}
  
= Documentation team meeting =
+
= Docs team meetings =
  
Every two weeks (on even weeks) on Thursday at 2100 UTC in <code><nowiki>#openstack-meeting-alt</nowiki></code> https://www.timeanddate.com/countdown/newyear?p0=24&msg=Pike+release&ud=1&font=slab
+
Provided there is an agenda to discuss, we hold docs team meetings every week.  
  
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.
+
On even weeks on Thursday at 0730 UTC in <code><nowiki>#openstack-meeting</nowiki></code>.
 +
On odd weeks on Thursday at 1630 UTC in <code><nowiki>#openstack-meeting</nowiki></code>.
  
Please feel free to add items to the agenda below and we'll cover them.
+
These IRC meetings are used to discuss general docs-related agenda. If you're looking to get started with documentation, or need to discuss work on a particular document, this is the place to do that.
  
== Agenda for next meeting ==
+
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 <code><nowiki>#openstack-doc</nowiki></code> at any time. You can also open discussions by emailing the <code><nowiki>openstack-discuss@lists.openstack.org</nowiki></code> mailing list and using the [docs] tag in subject.
  
When starting the meeting, use #startmeeting docteam to provide consistency.
+
== Agenda for the next meting ==
  
* #topic Action items from the last meeting
+
Please tell us about your agenda items at the start of office hours.
** None on the meeting minutes.
 
  
* #topic Countdown to summit:
+
== Previous meetings ==
** 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:
+
Previous meetings, with their notes and logs, can be found here: http://eavesdrop.openstack.org/meetings/docteam/
** 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 Bug triaging
 
** 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
 
** Lana has been doing a great job this week, thank you Lana!
 
** 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
+
== Running IRC meetings ==
  
== Apologies for absence ==
 
 
* Alex (asettle) - second week in a row! So unreliable... 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.
 
Public meetings are run in IRC; we use MeetBot syntax to note what happens during the meeting.
 
http://meetbot.debian.net/Manual.html
 
http://meetbot.debian.net/Manual.html
 +
 +
When starting the meeting, use <code><nowiki>#startmeeting docteam</nowiki></code> to provide consistency.
  
 
Useː
 
Useː
Line 71: Line 34:
 
* #action <item>, to note tasks for a specific person
 
* #action <item>, to note tasks for a specific person
 
* #endmeeting
 
* #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.
 
  
 
----
 
----
 
[[Category:Documentation]]
 
[[Category:Documentation]]

Latest revision as of 18:11, 12 December 2018

Docs team meetings

Provided there is an agenda to discuss, we hold docs team meetings every week.

On even weeks on Thursday at 0730 UTC in #openstack-meeting. On odd weeks on Thursday at 1630 UTC in #openstack-meeting.

These IRC meetings are used to discuss general docs-related agenda. If you're looking to get started with documentation, or need to discuss work on a particular document, this is the place to do that.

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-discuss@lists.openstack.org mailing list and using the [docs] tag in subject.

Agenda for the next meting

Please tell us about your agenda items at the start of office hours.

Previous meetings

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

Running IRC meetings

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

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

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