From Fedora Project Wiki

Line 55: Line 55:
! style="width:20%"|Beat Name || style="width:20%"|Writer || style="width:20%"|Developer PoC || style="width:15%"|Wiki good || style="width:15%"|In Publican ||style="width:15%"|Proofread
! style="width:20%"|Beat Name || style="width:20%"|Writer || style="width:20%"|Developer PoC || style="width:15%"|Wiki good || style="width:15%"|In Publican ||style="width:15%"|Proofread
|-
|-
| [[ Documentation_Architecture_Specific_Content_Beats | Architecture Specific Content ]] || ''Open'' || ''Open'' || '''0''' || '''1''' || '''[[User:Immanetize|Immanetize]] ([[User talk:Immanetize|talk]])'''
| [[ Documentation_Architecture_Specific_Content_Beats | Architecture Specific Content ]] || ''Open'' || ''Open'' || '''0''' || '''0''' || '''[[User:Immanetize|Immanetize]] ([[User talk:Immanetize|talk]])'''
|-
|-
| [[Documentation_x86_Specific_Content_Beat| x86 Specific Content]] || ''Open'' || ''Open'' || '''0''' || '''0''' || '''-'''  
| [[Documentation_x86_Specific_Content_Beat| x86 Specific Content]] || ''Open'' || ''Open'' || '''0''' || '''0''' || '''0'''  
|-
|-
| [[Documentation_x86_64_Specific_Beat| x86_64 Specific Content]] || ''Open'' || ''Open'' || '''0''' || '''0''' || '''-'''  
| [[Documentation_x86_64_Specific_Beat| x86_64 Specific Content]] || ''Open'' || ''Open'' || '''0''' || '''0''' || '''0'''  
|}
|}



Revision as of 00:11, 22 January 2013

Beat Assignments

This page lists all of the writing beats for the release notes, and who is assigned to them. See an empty slot? That means it's waiting for you! More specifically...

What will I be writing?

Beat writing is a good place for a new contributor to start working with the Fedora project. You'll learn about the next release of Fedora, but you don't need to be highly technical. Most of the work is done in the wiki, which means it's easy to get input from more experienced contributors.

These beats are essentially draft sections for the release notes document. (An annotated version of the Fedora 25 schedule for Release Notes is available at Releases/25/Schedule.) You're likely to have a developer contact and will be able to use the feature pages for your beat, as well as other resources. You can even start by pasting the release notes from your feature's page. So don't be nervous--just claim a beat!


Review Docs_Project_workflow_-_beat_writing for more thorough details about what you'll need to do.


How to take a beat or remove yourself from one

- If a beat writer has an asterisk (*) next to his/her name, that writer has not yet indicated whether (s)he will write for Fedora 25. If you are that writer, and you are still willing to help, please remove the asterisk.

- If a beat is a lonely orphan with no writer, and you'd like to be that person (or to help), just add your name to the Writer column.

- Once you've added your name, you should subscribe to the content flow mailing list.


Welcome to Fedora 25

Beat Name Writer Developer PoC Wiki good In Publican Proofread
Welcome Docs N/A 0 0 0
OverView Gadgetwisdom* N/A 0 0 0
Hardware Overview Greg Krpan* Open 0 0 0
Feedback Docs N/A 0 0 0
Release Notes Directory Change Donald Winslow* 0 0 0 0

Installation Notes

Beat Name Writer Developer PoC Wiki good In Publican Proofread
Installer Ben Cotton PJones *, Clumens * 0 0 0

Architecture Specific Notes

Beat Name Writer Developer PoC Wiki good In Publican Proofread
Architecture Specific Content Open Open 0 0 Immanetize (talk)
x86 Specific Content Open Open 0 0 0
x86_64 Specific Content Open Open 0 0 0

Changes in Fedora for Desktop users

Beat Name Writer Developer PoC Wiki good In Publican Proofread
Desktop crantila (KDE & GNOME), Sergio Cipolla (Xfce), Deepak Bhole* (Java) KevinKofler* (KDE) *, ChristopherAillon * 0 1 Immanetize (talk)
Productivity Bryan Sutherland Open 0 1 Immanetize (talk)
Networking Will Morris * ChristopherAillon * 0 1 Immanetize (talk)
Printing Ben Cotton Tim Waugh * 1 0 -
I18n JensPetersen* AkiraTagoh 1 1 Immanetize (talk)
Multimedia zoglesby* Open 0 0 -
Entertainment Nathant* Open 0 0 -
Live Emad78* Open 0 0 -

Changes in Fedora for System Administrators

Beat Name Writer Developer PoC Wiki good In Publican Proofread
Kernel Danny Stieben* Open 0 1 Immanetize (talk)
Boot (systemd) Nathant* Open 0 1 Immanetize (talk)
Security Ben Cotton Dan Walsh 1 1 Immanetize (talk)
Virtualization Stephen Gordon Open 1 1 Immanetize (talk)
Web Servers Yuri Khabarov Open 0 1 Immanetize (talk)
Cloud Ben Cotton Open 1 1 Immanetize (talk)
Mail Servers Danny Stieben* Open 0 0 -
Database Servers Zach Oglesby* Open 0 1 Immanetize (talk)
File Servers Tomoyuki KATO Open 1 1 Immanetize (talk)
Samba Danny Stieben* Open 0 1 Immanetize (talk)
System Daemons (cron, etc.) Ben Cotton Open 1 1 Immanetize (talk)
Server Configuration Tools Rashadul Islam Open 0 1 Immanetize (talk)
File Systems Ben Cotton Open 1 1 Immanetize (talk)
Xorg (X Window System) Stephen Gordon Adam Jackson* / Peter Hutterer* 1 1 Immanetize (talk)
Cluster DavidNalley* Open 0 0 -

Changes in Fedora for developers

Beat Name Writer Developer PoC Wiki good In Publican Proofread
Development Nathant* Open 1 1 Immanetize (talk)
Runtime Open Open 0 0 -
Development Tools Open Open 0 1 Immanetize (talk)
GCC Nathant* UlrichDrepper * 0 1 Immanetize (talk)
Java Potty* Open 0 0 -
D bioinfornatics* bioinfornatics* 0 1 Immanetize (talk)
Haskell JensPetersen* JensPetersen* 0 1 Immanetize (talk)
Eclipse MatBooth * MatBooth* 0 0 -
Backwards Compatibility Open Open 0 0 -
OCaml RichardJones* RichardJones* 0 0 -

Changes in Fedora for specific audiences

Beat Name Writer Developer PoC Wiki good In Publican Proofread
Scientific and Technical A.Mani* Open 0 0 -
EDA ChitleshGoorah* Shakthi Kannan* 0 0 -
Embedded Development JohnMcDonough Shakthi Kannan* 1 1 -
Circuit Design JohnMcDonough Shakthi Kannan* 1 1 -
Robotics Ruth Suehle* Tim Niemueller* 0 0 -
Amateur Radio JohnMcDonough* Open 0 1 Immanetize (talk)
Musicians crantila Open 0 0 -
Monitoring Volker Fröhlich - 1 0 -


Appendices

Beat Name Writer Developer PoC Wiki good In Publican Proofread
Legal Docs N/A - - -


Status key:

  • A 1 in the Wiki Good column indicates that the beat is ready for conversion to XML
  • A 0: Not ready for conversion to XML
  • A 0 indicates that the XML needs to be backported to the wiki
  • A *: Means ... what? It is recommended by "Warning / Beat Converted" blurbage.


  • A 1 in the In Publican column indicates that the beat has been converted
  • A 0 in the In Publican column indicates that the beat has not been completely converted to XML


  • A 1 in the Proofread column indicates that the published chapter has been reviewed
  • A 0 in the Proofread column indicates that it has not

Pages in category "Documentation beats"

The following 77 pages are in this category, out of 77 total.

D