From Fedora Project Wiki
m (Removed protection from "Changes/EmptyTemplate": updating)
(update template as decided in https://pagure.io/fesco/issue/1868)
Line 26: Line 26:
  
 
== 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 64: Line 65:
 
== 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 112: Line 137:
  
 
== 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 ==

Revision as of 15:18, 20 April 2018

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.>
  • Release notes owner:

Current status

  • Targeted release: [[Releases/<number> | Fedora <number> ]]
  • Last updated: 2018-04-20
  • Tracker bug: <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