From Fedora Project Wiki
(Current status)
m (Clean up the template a bit)
 
(26 intermediate revisions by 10 users not shown)
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 CHANGE PROPOSAL.'''}}
+
{{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 "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
  
 
<!-- Self Contained or System Wide Change Proposal?
 
<!-- Self Contained or System Wide Change Proposal?
Line 14: Line 14:
 
* changing system defaults
 
* changing system defaults
  
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  
+
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 improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies).   
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies).   
 
  
 
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
 
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
Line 22: Line 21:
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
  
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 
 
= Change Proposal Name <!-- The name of your change proposal --> =
 
= Change Proposal Name <!-- The name of your change proposal --> =
  
 
== Summary ==
 
== 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.
 +
Note that motivation for the change should be in the Motivation section below, and this part should answer the question "What?" rather than "Why?". -->
  
 
== Owner ==
 
== Owner ==
Line 35: Line 34:
 
* Name: [[User:FASAcountName| Your Name]]
 
* Name: [[User:FASAcountName| Your Name]]
 
<!-- 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. -->
 
<!-- 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.>
+
* Email: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>
* 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)
 
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
 
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
 
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
Line 47: Line 45:
 
== Current status ==
 
== Current status ==
 
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
 
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
* Last updated: (DATE)
+
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
 
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
 
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
 
Bugzilla states meaning as usual:
 
Bugzilla states meaning as usual:
NEW -> change proposal is submitted and announced
 
 
ASSIGNED -> accepted by FESCo with on going development
 
ASSIGNED -> accepted by FESCo with on going development
 
MODIFIED -> change is substantially done and testable
 
MODIFIED -> change is substantially done and testable
Line 57: Line 54:
 
-->
 
-->
 
* Tracker bug: <will be assigned by the Wrangler>
 
* Tracker bug: <will be assigned by the Wrangler>
 +
* Release notes tracker: <will be assigned by the Wrangler>
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 64: Line 62:
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
  
   
+
<!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved?
 
    
 
    
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
+
      Be sure to include the following areas if relevant:
 +
      If this is a major capability update, what has changed?
 +
          For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
 +
      If this is a new functionality, what capabilities does it bring?
 +
          For example: This change allows package upgrades to be performed automatically and rolled-back at will.
 +
      Does this improve some specific package or set of packages?
 +
          For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
 +
      Does this improve specific Spins or Editions?
 +
          For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
 +
      Does this make the distribution more efficient?
 +
          For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
 +
      Is this an improvement to maintainer processes?
 +
          For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
 +
      Is this an improvement targeted as specific contributors?
 +
          For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
 +
 
 +
    When a Change has multiple benefits, it's better to list them all.
 +
 
 +
    Consider these Change pages from previous editions as inspiration:
 +
    https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
 +
    https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
 +
    https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
 +
    https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
 +
    https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
 +
-->
  
 
== Scope ==
 
== Scope ==
Line 75: Line 97:
 
<!-- What work do other 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?-->
 
<!-- What work do other 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?-->
  
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
+
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
 +
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
  
 
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
 
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
 +
 +
* Trademark approval: N/A (not needed for this Change)
 +
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
  
 
== Upgrade/compatibility impact ==
 
== Upgrade/compatibility impact ==
Line 106: Line 132:
  
 
== User Experience ==
 
== User Experience ==
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
+
<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
 
N/A (not a System Wide Change)
+
This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
 +
 
 +
  Describe what Users will see or notice, for example:
 +
  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
 +
  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
 +
- Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
 +
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
 +
-->
  
 
== Dependencies ==
 
== Dependencies ==

Latest revision as of 19:52, 14 May 2019

Important.png
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 "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.


Change Proposal Name

Summary

Owner

  • Name: Your Name
  • Email: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>

Current status

  • Targeted release: [[Releases/<number> | Fedora <number> ]]
  • Last updated: 2019-05-14
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

Benefit to Fedora

Scope

  • Proposal owners:
  • Other developers: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes