Docs Project meetings

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(18 February 2013)
(18 February 2013)
Line 23: Line 23:
  
 
{{Anchor|agenda}} <!-- leave that in place so it *always* works -->
 
{{Anchor|agenda}} <!-- leave that in place so it *always* works -->
=== 18 February 2013 ===
+
=== 11 March 2013 ===
  
 
{{admon/note|Before you change the agenda...|To keep the meeting schedule under control and to promote openness, please bring any proposed agenda item to the {{fplist|docs}} mailing list for discussion before adding it to the agenda.}}
 
{{admon/note|Before you change the agenda...|To keep the meeting schedule under control and to promote openness, please bring any proposed agenda item to the {{fplist|docs}} mailing list for discussion before adding it to the agenda.}}
Line 37: Line 37:
  
 
* #topic Beat Assignments
 
* #topic Beat Assignments
 
+
* #topic F19 Schedule is out
 +
** #link http://fedorapeople.org/groups/schedule/f-19/
 
* #topic Outstanding BZ Tickets (5 minutes)
 
* #topic Outstanding BZ Tickets (5 minutes)
 
** All Bugs
 
** All Bugs

Revision as of 14:00, 11 March 2013

DocsProject Header docTeam1.png


The Fedora Documentation Project holds weekly IRC meetings. All members of the Fedora Project are welcome to participate.

Information about past meetings can be found on the Category:Docs Project meetings page.

Contents

Meeting Details

WikiElements meetingL.png

The Docs Project meets in channel #fedora-meeting[?] on freenode.net . All members of the community are welcome to attend and participate in our meetings.

  • Day: Monday
  • Time: 14:00 UTC (See the UTC Howto for instructions to convert UTC to your local time)
  • Location: #fedora-meeting[?] on freenode.net

For more information and to discuss any of the agenda items, be sure to click on the links to read the threads on the docs list.

A meeting reminder should be sent at the beginning of the meeting day.

Agenda for Next Meeting

This is the agenda for the next meeting for Docs Project. Please write down your topic suggestions so that we have an idea on what will be discussed in the meeting. Pointers to emails which expand on the idea are always welcome!

11 March 2013

Note.png
Before you change the agenda...
To keep the meeting schedule under control and to promote openness, please bring any proposed agenda item to the docs mailing list for discussion before adding it to the agenda.
  • #topic Roll Call
    • #info Participants are reminded to make liberal use of #info #link #help in order to make the minutes "more better"
  • #topic Follow up on last week's action items (10 minutes )
    • Informal action items:
      • randomuser to work on bug assignee list
  • #topic Docs Infrastructure
  • #topic Open floor discussion (5 minutes)

Task table

This table may be transcluded in other locations, but originates at Docs_Project_admin_tasks_for_experienced_contributors#Task_table.

Task Assignee Due date Next milestone Status
Update helping-hand docs quaid, stickster, jsmith Overdue  ? Review, organize, rewrite, simplify, and categorize Docs team helper docs -- waiting on page renaming and categorization

Guides

This table discusses who owns which documentation guide. All of these guides are a work in progress. F indicates next version planned; which in turn becomes the last published. Join the fun by contacting the guide owner or adopting an orphaned guide. Have an idea for a guide not yet in this list? Bring it up on the docs project list.

Guide Name F Guide Lead QA Contact Wiki Repo L10N Priority In translation RPM HTML (docs.fp.o)
docbook-locales - rudi sign up! No Fedora Git; Upstream SVN 1 Yes Yes Used to produce all guides on d.fp.o
Common_Content for Publican - rudi anross No SVN 2 Yes Yes Used to produce all guides on d.fp.o
Publican branding for Fedora - rudi anross No SVN 3 Yes Yes Used to produce all guides on d.fp.o
Documentation website - rudi anross No Git 4 Yes No Welcome and explanatory text for docs.fp.o
 
Accessibility Guide F16 Sparks sign up! No [1] 9 Yes No Yes
Amateur Radio Guide F16 jjmcd, Sparks sign up! Wishlist [2] Yes No Yes
Burning ISOs F18 bcotton sign up! No [3]| * Yes No Yes
Cloud Guide F16 Sparks sign up! No [4] Yes No Yes
Documentation Guide - Sparks sign up! No [5] No No Yes
Elections Guide - Sparks sign up! No [6] Yes No Yes
FreeIPA Guide F17 *Open* sign up! No Orphaned  ? yes No Yes
Installation Guide F20 pbokoc sign up! No [7] 7 Yes†† No Yes
Installation Quick Start Guide F19 pbokoc jhradile No ** Merged into IG ** 6 Yes†† No Yes
Live Images F18 bcotton sign up! No [8] * Yes No Yes
Musicians' Guide F18 crantila sign up! Outdated [9] Yes No Yes
Multiboot Guide F19/F20 chrisroberts chrisroberts No [10] No No No
Networking Guide F20 StephenW No [11] No No Yes
OpenSSH Guide  ? kennepede sign up! No [12] No No Yes
Packager's Guide F18 pmkovar jhradile No [13] Yes No Yes
Power Management Guide F18 yruseva sign up! No [14] Yes No Yes
Release Notes All randomuser,jjmcd ryanlerch zoglesby Beats [15] 5 Yes Yes Yes
Resource Management Guide F17 *Open* sign up! Yes [16] Yes No Yes
Security Guide F18 sparks, kennepede bcotton Archived [17] 10 Yes No Yes
Software Collections Guide - pmkovar jhradile No [18] Yes No Yes
Software Management Guide F20 Gomix sign up! No [19] Yes No Yes
Storage Administration Guide F14 *Open* sign up! No [20] Yes No Yes
System Administrator's Guide F20 StephenW crantila No [21] 8 Yes No Yes
System Administrator's Reference Guide F20 StephenW No [22] No No Yes
Technical Notes F17 randomuser sign up! No [23] Yes No Yes
UEFI Secure Boot Guide F18 Sparks No [24] Yes No Yes
Virtualization Administration and Deployment Guide F19 lnovich sign up! No [25] Yes No Yes
Virtualization Getting Started Guide** F19 dmparker sign up! No [26] Yes No Yes
Virtualization Security Guide** F19 sradvan sign up! No [27] No No Yes
Wireless Guide F17 StephenW sign up! No [28] Yes No Yes

* This document is low priority, but is short and easy text ideal for new documentation translators.

** Replaces the Virtualization Guide from F14 onwards.

Important.png
Please use "Yes", "No", "Archived", "In Progress", or "Due on..." in each block to denote current status.
Status
Still under development
Branched for F21
Branched, in translation, and drafts on d.fp.o

Old Guides