Latest revision as of 02:43, 26 February 2009

Tasks for SingleSourceSummary

Current SSS is Releases/9/SingleSourceSummary

SingleSourceSummary Tasks

Desktop - Bluetooth
Desktop - Clock applet
Desktop - Dictionary Support
Desktop - Fingerprint Authentication
Desktop - KDE 4
Desktop - More NetworkManager
Desktop - PackageKit
Desktop - TeXLive
Server - Full Virt Kernel Boot
Server - Server Provides
Server - Virtual Authentication
Server - Virtual Manager PolicyKit
Server - Virtual Storage
Server - Xen paravirt_ops
System - ext4 Filesystem
System - Encrypted Filesystems
System - Fast X Startup and Shutdown
System - FreeIPA
System - gcc 4.3
System - Haskell Support
System - Input Method Integration
System - K12 Linux
System - Partition Resizing
System - Perl 5.10
System - Pre-Upgrade
System - Presto
System - Second State Install Source
System - Update X Server
System - Upstart

SingleSourceSummary Uses

Desktop - Bluetooth
Desktop - Clock applet
Desktop - Dictionary Support
Desktop - Fingerprint Authentication
Desktop - KDE 4
Desktop - More NetworkManager
Desktop - PackageKit
Desktop - TeXLive
Server - Full Virt Kernel Boot
Server - Server Provides
Server - Virtual Authentication
Server - Virtual Manager PolicyKit
Server - Virtual Storage
Server - Xen paravirt_ops
System - ext4 Filesystem
System - Encrypted Filesystems
System - Fast X Startup and Shutdown
System - FreeIPA
System - gcc 4.3
System - Haskell Support
System - Input Method Integration
System - K12 Linux
System - Partition Resizing
System - Perl 5.10
System - Pre-Upgrade
System - Presto
System - Second State Install Source
System - Update X Server
System - Upstart

Map and Merge

Find similar content (paragraph minimum size?)
Map back to where it came from
Merge it
Wrap the new merge with comment blocks
Use Include() to pull in the block to the mapped-from location

Individual Mapped Points

Fedora Release Summary

This is in the Release/N/ namespace.

Fedora Release Overview

This is a newer people-friendly way to present the content. The content here sits in front of deeper content from Docs/Beats/. Comparable to the GNOME release pages, focusing on the new stuff for users / developers / contributors.

Release Overview

This format was used in the Alpha/Beta release notes for F9.

Map and merge with the Fedora Release Overview

Press Release

Content here may have a different voice/style to other content. Some of this content may repeat content in other parts of this page, if the style needs adjusting for the press voice. To keep track of this, use an Include() to pull in the other comment block for constant comparison. Use a nested sub-section with a common title structure.

Release Announcements

Return to the canonical pages to ensure the process is updated
- Docs/Drafts/ReleaseAnnouncements needs to be moved to Releases/N/Announcements? or ... ?
Update
Announce the opening of release announcement fun for F9

Talking Points for Localized Summaries

Talking points need to give three to five short (one, two sentence) paragraphs that describes major points we want everyone talking about in their release announcements. A local team takes these points to write in their own language whatever style is appropriate (humorous, press release-like, technical, excited!, etc.). A local team can use other parts of the SSS to pull pieces to discuss, but that makes for very looooong release announcements, which we don't recommend. Maybe we want a way to localize the talking points to make it easier for Ambassadors?

Create three to five short (one, two sentence) paragraphs that describes major points we want everyone talking about in their release announcements.
Coordinate with the L10N team on potential localization
Announce availability on f-marketing-l and f-trans-announce
- Announcement should have link back to canonical Releases/Announcements page that explains how-to
Think of a way to get these annoucements staticly displayed on website (preferred) / wiki + get links to translated announcements in the official announcement
Maybe display the localized version on the localized fedoraproject.org front page?
- Promotes dual-use beyond the immediate announcement purpose

@@ Line 3: / Line 3: @@
 = Tasks for SingleSourceSummary  =
-{{ Template:message/note |  '''Current SSS is [[Releases/9/SingleSourceSummary| Releases/9/SingleSourceSummar]]  '''
+{{Admon/note | Current SSS is [[Releases/9/SingleSourceSummary]]}}
-}}
 == SingleSourceSummary Tasks ==
-{| style="t1" rowclass="th" style="text-align: left;"
+{|
 |-
 | Desktop - Bluetooth || ||
@@ Line 74: / Line 71: @@
 == SingleSourceSummary Uses ==
-{| style="t1" rowclass="th" style="text-align: left;"
+{|
 |-
 | Desktop - Bluetooth || || || ||
@@ Line 137: / Line 134: @@
 == Map and Merge ==
-. Find similar content (paragraph minimum size?)
+# Find similar content (paragraph minimum size?)
-. Map back to where it came from
+# Map back to where it came from
-. Merge it
+# Merge it
-. Wrap the new merge with comment blocks
+# Wrap the new merge with comment blocks
-. Use <code>Include()</code> to pull in the block to the mapped-from location
+# Use <code>Include()</code> to pull in the block to the mapped-from location
 == Individual Mapped Points ==
@@ Line 157: / Line 154: @@
 This format was used in the Alpha/Beta release notes for F9.
-. Map and merge with the Fedora Release Overview
+# Map and merge with the Fedora Release Overview
 === Press Release ===
@@ Line 165: / Line 162: @@
 == Release Announcements ==
-. Return to the canonical pages to ensure the process is updated
+# Return to the canonical pages to ensure the process is updated
-* [[Docs/Drafts/ReleaseAnnouncements| Docs/Drafts/ReleaseAnnouncements]]  needs to be moved to Releases/N/Announcements?  or ... ?
+#* [[Docs/Drafts/ReleaseAnnouncements| Docs/Drafts/ReleaseAnnouncements]]  needs to be moved to Releases/N/Announcements?  or ... ?
-. Update
+# Update
-. Announce the opening of release announcement fun for F9
+# Announce the opening of release announcement fun for F9
 === Talking Points for Localized Summaries ===
@@ Line 174: / Line 171: @@
 Talking points need to give three to five short (one, two sentence) paragraphs that describes major points we want everyone talking about in their release announcements. A local team takes these points to write in their own language whatever style is appropriate (humorous, press release-like, technical, excited!, etc.). A local team can use other parts of the SSS to pull pieces to discuss, but that makes for very looooong release announcements, which we don't recommend. Maybe we want a way to localize the talking points to make it easier for Ambassadors?
-. Create three to five short (one, two sentence) paragraphs that describes major points we want everyone talking about in their release announcements.
+# Create three to five short (one, two sentence) paragraphs that describes major points we want everyone talking about in their release announcements.
-. Coordinate with the L10N team on potential localization
+# Coordinate with the L10N team on potential localization
-. Announce availability on f-marketing-l and f-trans-announce
+# Announce availability on f-marketing-l and f-trans-announce
-* Announcement should have link back to canonical Releases/Announcements page that explains how-to
+#* Announcement should have link back to canonical Releases/Announcements page that explains how-to
-. Think of a way to get these annoucements staticly displayed on website (preferred) / wiki + get links to translated announcements in the official announcement
+# Think of a way to get these annoucements staticly displayed on website (preferred) / wiki + get links to translated announcements in the official announcement
-. Maybe display the localized version on the localized fedoraproject.org front page?
+# Maybe display the localized version on the localized fedoraproject.org front page?
-* Promotes dual-use beyond the immediate announcement purpose
+#* Promotes dual-use beyond the immediate announcement purpose
+[[Category:Docs Project archives]]

Search

Archive:DocsProject/Tasks/SingleSourceSummary: Difference between revisions