Revision as of 15:26, 20 April 2018

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)

Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- List of deliverables: 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

@@ 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?
@@ Line 23: / Line 23: @@
 <!-- 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 -->
-= Client Side of Gnome Replace each Radio Button by an mnemonics field =
+= Change Proposal Name <!-- The name of your change proposal --> =
 == Summary ==
-Client side. For the "ALL" activities page, replace the Gnome3.16+ radio button presentation  with a three or two character string representing the initial letters of the very first icon corresponding to that page. Justication -- My computer has 5 users, and to aid users in locating an icon for an application whose name is not known exactly, would eliminate selecting and scrolling through the each radio button until the desired application is found.
+<!-- 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 ==
+<!--
-I am not a developer, but an end-user. My All page has 9 radio buttons. This request would require a developer to review the practicality.
+For change proposals to qualify 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.
-* Name: lsatenstein | Leslie Satenstein|
+This should link to your home wiki page so we know who you are.
-* Email: < lsatenstein@yahoo.com >
+-->
+* 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. -->
+* 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)
@@ Line 57: / Line 61: @@
 == Detailed Description ==
-My computer is shared between a blogger, game player, C programmer, music author, and e-book reader/researcher. Currently my system, within the Gnome  "All" page of Activities has 9 radio buttons. When a program is not in the "frequent" page of the Activities presentation, it takes either scrolling or a binary search using the radio buttons in order to land on the page of icons that are of interest.
+<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
-By introducting the three character (or even two character) mnemonic in place of each radio button, zooming in to a good starting point for a visual search is facilitated.  The mnemonic serves in a way similar to the tabs on the large printed Paper bound book Dictionaries.
 == Benefit to Fedora ==
-Makes the Fedora "Applications All" facility easier and faster to use, without removing functionality. I am not aware of the effort to replace the radio buttons by a mnemonic field but it is practical if done?  The capabilities proposed will provide a means to reduce the number of mouse key clicks and unnecessary scrolling in order to locate an application by it's image. This change by reducing the number of mouse clicks will contribute to avoiding finger tendon muscle pain at the end of session of Gnome use.
+<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
+      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 ==
 * Proposal owners:
-I cannot say as I am not a gui developer  I consider the update as an isolated set of changes.
+<!-- What work do the feature owners 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?-->
 * Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- What work do other developers have to accomplish to complete the feature in time for release?  '''Localized to the Gnome presentation of this "Application All" presentation'''. Is it a large change affecting many parts of the distribution or is it a very isolated change? « isolated»  What are those changes? « keep click functionality but replace radio buttons by mnemonic -->
+<!-- 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 AS WELL AS FOR SELF CONTAINED 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.
-Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook  -->
+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 -->
+** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
 * Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 82: / Line 113: @@
 == Upgrade/compatibility impact ==
-The output would continue to allow the user to click on a mnenonic that takes the place of each radio button. The mnemonic for the current page would be highlighted. Currently the radio button for the current page is filled.
+<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 88: / Line 119: @@
 == How To Test ==
-If it works, with varying number of mnemonics, (application icon pages), from empty to a max number, it passes.
+<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation 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.
-It needs to be tested with different screen sizes, since the screen size will determine the number of application program images per page.
-End users will perform the testing of the alpha, beta, RC's  and later versons.
+Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
+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 change? What packages
+need to be installed, config files edited, etc.?
 . What specific actions do I perform to check that the change is
-working like it's supposed to?  Click on mnemonic and compare to first mnemonic listed on the page
+working like it's supposed to?
-. Improved functionality.
+. What are the expected results of those actions?
+-->
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 100: / Line 137: @@
 == User Experience ==
-Users will see a more thought out and better Gnome functionality that only experience can demonstrate.
+<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
+ 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 ==
-This change is isolated or localized to the "Activities «ALL » presentatation logic.
+<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change 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 change)? -->
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 N/A (not a System Wide Change)
 == Contingency Plan ==
-If it cannot be implemented in time, just do not implement and remain with previous version of logic.
-It is a replacement operation.
 <!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->

Search

Changes/EmptyTemplate: Difference between revisions

Revision as of 15:26, 20 April 2018

Contents

Change Proposal Name

Summary

Owner

Current status

Detailed Description

Benefit to Fedora

Scope

Upgrade/compatibility impact

How To Test

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes