Difference between revisions of "Meetings/DocTeamMeeting"
Petr Kovar (talk | contribs) |
Petr Kovar (talk | contribs) |
||
| Line 12: | Line 12: | ||
When starting the meeting, use <code><nowiki>#startmeeting docteam</nowiki></code> to provide consistency. | When starting the meeting, use <code><nowiki>#startmeeting docteam</nowiki></code> to provide consistency. | ||
| + | |||
| + | * #topic Ops docs discussion | ||
| + | ** #link http://lists.openstack.org/pipermail/openstack-operators/2018-May/015318.html | ||
| + | ** #info Ops community plans to take ownership of the ops, ha and architecture guides | ||
| + | |||
| + | * #topic Contributor Guide lead | ||
| + | ** #info After Mike P's departure, Kendall N is the new lead | ||
| + | |||
| + | * #topic Default warning-is-error to True for non-legacy Sphinx projects | ||
| + | ** #link https://review.openstack.org/#/c/559348/ | ||
| + | ** #info Ready to be merged | ||
* #topic Vancouver Summit | * #topic Vancouver Summit | ||
| − | ** #info | + | ** #info Docs-i18N - Project Update recording available online, thanks to everybody involved! |
| + | ** #link https://www.youtube.com/watch?v=FIGErKqXAy8 | ||
* #topic Bug Triage Team | * #topic Bug Triage Team | ||
** #link https://wiki.openstack.org/wiki/Documentation/SpecialityTeams | ** #link https://wiki.openstack.org/wiki/Documentation/SpecialityTeams | ||
| − | + | ** #info Backlog stable, number of unresolved bugs started to decrease recently | |
| − | |||
| − | |||
| − | ** #info | ||
* #topic Open discussion | * #topic Open discussion | ||
Revision as of 14:15, 30 May 2018
Contents
Documentation team meeting
Every two weeks (on even weeks) on Wednesday at 1600 UTC in #openstack-doc.
This meeting is used to discuss the status of the docs team and 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 Ops docs discussion
- #link http://lists.openstack.org/pipermail/openstack-operators/2018-May/015318.html
- #info Ops community plans to take ownership of the ops, ha and architecture guides
- #topic Contributor Guide lead
- #info After Mike P's departure, Kendall N is the new lead
- #topic Default warning-is-error to True for non-legacy Sphinx projects
- #link https://review.openstack.org/#/c/559348/
- #info Ready to be merged
- #topic Vancouver Summit
- #info Docs-i18N - Project Update recording available online, thanks to everybody involved!
- #link https://www.youtube.com/watch?v=FIGErKqXAy8
- #topic Bug Triage Team
- #link https://wiki.openstack.org/wiki/Documentation/SpecialityTeams
- #info Backlog stable, number of unresolved bugs started to decrease recently
- #topic Open discussion
Apologies for absence
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-dev@lists.openstack.org mailing list and using the [docs] tag in subject.
