Jump to: navigation, search

Difference between revisions of "Meetings/DocTeamMeeting"

(Agenda for next meeting)
 
(45 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.
** #action Darren C to send out arch-guide action plan to ML!
 
** #action Team to review reno patches for docs!
 
** #action jrobinson to write spec for the admin guide
 
** #action team to review arch guide spec
 
* #topic Countdown to release:
 
** 43 weeks, everyone chill!
 
** Schedule for next release
 
*** #link https://releases.openstack.org/pike/schedule.html
 
* #topic Install guide/branching
 
** #link https://review.openstack.org/#/c/438328/
 
** #link https://launchpad.net/bugs/1663485
 
* #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
 
** 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
 
** User guides: Joseph Robinson
 
* #topic Specs in review #link https://review.openstack.org/#/q/status:open+project:openstack/docs-specs,n,z
 
** Project-specific Administration Guide: https://review.openstack.org/#/c/439122/
 
* #topic Bug triaging
 
** Next week's triager is... Ianeta!
 
** #link https://docs.openstack.org/contributor-guide/doc-bugs.html
 
** Anyone else sign up to help out :)
 
** https://wiki.openstack.org/wiki/Documentation/SpecialityTeams#Bug_Triage_Team
 
* #topic Open discussion
 
  
== Apologies for absence ==
+
== Previous meetings ==
  
== Previous meetings ==
 
 
Previous meetings, with their notes and logs, can be found here: http://eavesdrop.openstack.org/meetings/docteam/
 
Previous meetings, with their notes and logs, can be found here: http://eavesdrop.openstack.org/meetings/docteam/
  
== Running Meetings ==
+
== Running IRC 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 62: 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