Jump to: navigation, search

Difference between revisions of "Meetings/DocTeamMeeting"

(Agenda for next meeting)
 
(279 intermediate revisions by 17 users not shown)
Line 1: Line 1:
 
{{OpenStack_Documentation_Navbar}}
 
{{OpenStack_Documentation_Navbar}}
  
= Monthly doc/web team meeting =
+
= Docs team meetings =
If you're interested in documentation and the web content for OpenStack, we hold public meetings monthly in <code><nowiki>#openstack-meeting</nowiki></code> or <code><nowiki>#openstack-meeting-alt</nowiki></code>, every Wednesday at alternating times for different timezones:
 
  
* 1st Wednesday, 03:00:00 UTC <code><nowiki>#openstack-meeting</nowiki></code> (APAC)
+
Provided there is an agenda to discuss, we hold docs team meetings every week.
* 2nd Wednesday, 14:00:00 UTC <code><nowiki>#openstack-meeting-alt</nowiki></code> (US)
 
* 3rd Wednesday, 03:00:00 UTC <code><nowiki>#openstack-meeting</nowiki></code> (APAC)
 
* 4th Wednesday, 14:00:00 UTC <code><nowiki>#openstack-meeting-alt</nowiki></code> (US)
 
  
Please feel free to add items to the agenda below and we'll cover them.
+
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>.
  
== Agenda for next 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.
Scheduled for Wednesday Feb 12, 2014, 1400 UTC.
 
  
* Action items from the last 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.
* Doc tools update - 0.6 release of openstack-doc-tools
 
* Style Guide for config strings going into HACKING.rst
 
* Next APAC docs meeting f2f in Brisbane
 
* Operations Guide edits from O'Reilly, master and feature/edits branches
 
* Proposals for OpenStack Summit due 2/14, Design Summit tracks will be set in April
 
* API Docs blueprint updated: https://wiki.openstack.org/wiki/Blueprint-os-api-docs
 
* Giveaways: Oxygen licenses are available, Travel Program for Summit, and Write the Docs in Budapest
 
* Installation guide updates for Icehouse
 
* Open discussion
 
  
== Apologies for absence ==
+
== Agenda for the next meting ==
 +
 
 +
Please tell us about your agenda items at the start of office hours.
  
 
== Previous meetings ==
 
== Previous meetings ==
Previous meetings, with their notes and logs, can be found in under [[Documentation/MeetingLogs]]
 
  
== Google Hangout for Docs ==
+
Previous meetings, with their notes and logs, can be found here: http://eavesdrop.openstack.org/meetings/docteam/
Scheduled for Wednesday, January 29, 2014 at 20:00:00 UTC
 
Look for Hangouts On Air invitation on Google Plus.
 
  
* Guides
+
== Running IRC meetings ==
** Cloud Administrator Guide (HowTos from Config Reference Guide moving into Cloud Admin Guide)
 
** CLI Reference
 
** Creating OpenStack API Guide
 
** Maintaining Install Guide
 
** Updating End User and Admin User Guidesː look at possible automation of user workflow/screenshots
 
** Updating Operations Guide - Havana and O'Reilly, report from mini sprint
 
  
* Admin and Tools work
+
Public meetings are run in IRC; we use MeetBot syntax to note what happens during the meeting.
** Gating enabled on multiple repositories
+
http://meetbot.debian.net/Manual.html
** Translations enabled
 
  
* Anything else? Add here.
+
When starting the meeting, use <code><nowiki>#startmeeting docteam</nowiki></code> to provide consistency.
** HA guide update for Neutron (emagana)
 
  
== Office hours ==
+
Useː
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.
+
* #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
  
 
----
 
----
 
[[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