Archive:DocsProject/Tasks/SingleSourceSummary

= Tasks for SingleSourceSummary =

Map and Merge

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

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.


 * 1) 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  to pull in the other comment block for constant comparison. Use a nested sub-section with a common title structure.

Release Announcements

 * 1) Return to the canonical pages to ensure the process is updated
 * 2) * Docs/Drafts/ReleaseAnnouncements  needs to be moved to Releases/N/Announcements?  or ... ?
 * 3) Update
 * 4) 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?


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