Revision as of 14:53, 26 March 2013

Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR PROPOSED CHANGE.

All sections of this template are required for announcing the feature.

Change Proposal Name

Summary

Owner

Name: Your Name
Email: <your email address so we can contact you, invite you to meetings, etc.>
Release notes owner:

Current status

Targeted release: [[Releases/<number> | Fedora <number> ]]
Last updated: (DATE)
Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Benefit to Fedora

Scope

How To Test

N/A

User Experience

N/A

Dependencies

N/A

Contingency Plan

N/A

Documentation

N/A

@@ Line 1: / Line 1: @@
+{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section.  They are invisible when viewing this page.  To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR PROPOSED CHANGE.'''}}
+{{admon/note | All sections of this template are required for announcing the feature.}}
 <!-- Self Contained or System Wide Change Proposal?
-Use this guide to determine ...
+Use this guide to determine to which category your proposed change belongs.
+Self Contained Changes are:
+* changes to isolated/leaf package without the impact on other packages/rest of the distribution
+* limited scope changes without the impact on other packages/rest of the distribution
+* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
+System Wide Changes are:
+* changes that does not fit Self Contained Changes category touching
+* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
+* changing system defaults
 -->
 <!--
 All fields on this form are required for announcing the change proposal. We also request that you maintain the same order of sections so that all of the change proposal pages are uniform.
 For self contained changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is
-updated to System Wide category.
+updated to System Wide category).
 -->
@@ Line 15: / Line 29: @@
 == Summary ==
-<!-- A sentence or two summarizing what this change is and what it will do.  This information is used for the overall changeset summary page for each release. -->
+<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
 == Owner ==
-<!--This should link to your home wiki page so we know who you are.
+<!--
+For a feature to quality as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
-TODO: For a feature to quality as self-contained, owners of all affected packages need to be included here.  Alternatively, a SIG can be listed as an owner if it owns all affected packages. -->
+This should link to your home wiki page so we know who you are.
+-->
 * Name: [[User:FASAcountName| Your Name]]
-<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved.  If the feature is owned by a SIG, please also add a primary contact person. -->
+<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
 * Email: <your email address so we can contact you, invite you to meetings, etc.>
+* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
+<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
+* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
+-->
 == Current status ==
@@ Line 30: / Line 49: @@
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page -->
 * Tracker bug: <will be assigned by the Wrangler>
+== Detailed Description ==
+<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+== Benefit to Fedora ==
+<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
+== Scope ==
+<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+== How To Test ==
+<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
+Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
+A good "how to test" should answer these four questions:
+. What special hardware / data / etc. is needed (if any)?
+. How do I prepare my system to test this feature? What packages
+need to be installed, config files edited, etc.?
+. What specific actions do I perform to check that the feature is
+working like it's supposed to?
+. What are the expected results of those actions?
+-->
+<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+N/A
+== User Experience ==
+<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
+<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+N/A
+== Dependencies ==
+<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
+<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+N/A
+== Contingency Plan ==
+<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
+<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+N/A
+== Documentation ==
+<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+N/A
 == Release Notes ==
@@ Line 37: / Line 106: @@
 Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
 -->
-* Release notes owner:

Search

Changes/Policy: Difference between revisions