Jump to: navigation, search

Difference between revisions of "Meetings/DocTeamMeeting"

 
(308 intermediate revisions by 18 users not shown)
Line 1: Line 1:
 +
{{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>, every Tuesday at alternating times for different timezones:
 
  
* 1st Tuesday, 03:00:00 UTC
+
Provided there is an agenda to discuss, we hold docs team meetings every week.
* 2nd Tuesday, 14:00:00 UTC
 
* 3rd Tuesday, 03:00:00 UTC
 
* 4th Tuesday, 14:00:00 UTC
 
  
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 Tuesday Nov 26, 2013, 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.
* Announcement: Google Hangout Monday, December 2, 2013 at 03:00:00 (that's 7:00 PM PST, 9:00 PM CST, 10:00 PM EST)
 
* Educating devs on what goes where
 
* Onboarding doc contributors
 
* Cancel regular office hours now that we meet weekly
 
* Doc Boot Camp?
 
* Operations Guide workflow
 
* Doc tools updates
 
* 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 Monday, December 2, 2013 at 03:00:00 UTC
 
  
https://www.youtube.com/watch?v=92sCHInrwYg
+
== Running IRC meetings ==
  
* Guides
+
Public meetings are run in IRC; we use MeetBot syntax to note what happens during the meeting.
** Creating new CLI Reference listing commands and subcommands (also came in on Twitter, a request for a Quick Start, example http://docs.splunk.com/images/a/a3/Splunk_4.x_cheatsheet.pdf - laminated cheat sheets are highly requested)
+
http://meetbot.debian.net/Manual.html
** Creating OpenStack API Guide
 
** Maintaining and revising Cloud Administrator Guide (HowTos from Config Reference Guide moving into Cloud Admin Guide)
 
** Maintaining Install Guide
 
** Using RST to XML automation could result in a 'Getting Started with OS Development' guide.
 
** Updating End User and Admin User Guidesː look at possible automation of user workflow/screenshots
 
** Updating Operations Guide - Havana and O'Reilly
 
  
* Admin work
+
When starting the meeting, use <code><nowiki>#startmeeting docteam</nowiki></code> to provide consistency.
** Moving API specs into project repos
 
** Documenting what types of content goes into each book
 
** Prioritizing docs - integrated projects, training guides, DocImpact, reviews
 
** Updating Doc Project web page - ensuring that release types, released and continuous integration, are made obvious.
 
** developer.openstack.org - Getting resources out to the app development community
 
  
* Anything else? Add here.
+
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 ==
+
----
If you'd like to walk through documentation processes, learn about the tools, report a doc bug, feel free to come by the IRC channel at #openstack-doc on Mondays starting at 16:00 UTC. Drop-ins are welcome, or set up an appointment ahead of time by emailing the openstack-docs@lists.openstack.org mailing list.
+
[[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