|
|
| Line 57: |
Line 57: |
| <span>INFO: Eighth_Doctor | I think this is the thing that actually manages /usr/bin/editor on debian: https://salsa.debian.org/debian/sensible-utils</span> | | <span>INFO: Eighth_Doctor | I think this is the thing that actually manages /usr/bin/editor on debian: https://salsa.debian.org/debian/sensible-utils</span> |
|
| |
|
| * Other developers: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | | * Other developers: N/A |
| <!-- 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: [https://pagure.io/releng/issues/9522 #9522] | | * Release engineering: [https://pagure.io/releng/issues/9522 #9522] |
| Line 65: |
Line 64: |
| <!-- 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) | | * Trademark approval: N/A |
| <!-- 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 == |
| <!-- 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 -->
| | Will not apply to upgrades. |
| N/A (not a System Wide Change)
| |
|
| |
|
| == How To Test == | | == How To Test == |
| <!-- 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.
| |
|
| |
|
| 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.
| | Lorem ipsum dolor sit amet ... |
| | |
| A good "how to test" should answer these four questions:
| |
| | |
| 0. What special hardware / data / etc. is needed (if any)?
| |
| 1. How do I prepare my system to test this change? What packages
| |
| need to be installed, config files edited, etc.?
| |
| 2. What specific actions do I perform to check that the change is
| |
| working like it's supposed to?
| |
| 3. What are the expected results of those actions?
| |
| -->
| |
| | |
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| N/A (not a System Wide Change)
| |
|
| |
|
| == User Experience == | | == User Experience == |
| <!-- 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.
| | Lorem ipsum dolor sit amet ... |
| | |
| 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 == |
| <!-- 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 -->
| | Lorem ipsum dolor sit amet ... |
| N/A (not a System Wide Change)
| |
|
| |
|
| == Contingency Plan == | | == Contingency Plan == |
|
| |
|
| <!-- 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. -->
| | * Contingency deadline: Revert? (Seems a bit roll the giant boulder back up the hill, but this is a required field.) |
| * Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | | |
| <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. -->
| | * Blocks release? Maybe? If the change breaks the redirection to an editor, might be blocking. |
| * Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| | * Blocks product? Potentially all. |
| <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
| |
| * Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |
| * Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next --> | |
|
| |
|
| == Documentation == | | == Documentation == |
Make nano the default editor
Summary
vim is powerful. nano is simple. Let's use nano as the default editor across all of Fedora.
Owner
Current status
- Targeted release: Fedora 33
- Last updated: 2020-06-12
- FESCo issue: <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
nano is already installed across most Fedora Editions and Spins. This proposal will make it the default editor, while continuing to install vim-minimal.
vim requires esoteric knowledge, or Googling, for common editing tasks: entering edit mode, saving, quitting. Let's leave such power in the hands of experts.
Feedback
Benefit to Fedora
- Makes the default editor across all of Fedora more approachable.
- Nano is also mostly self-documenting, by displaying common keyboard shortcuts on-screen).
- More in line with the default editor of other distributions.
Scope
- Proposal owners:
- Modify comps to include nano Fedora wide
- Create a package that provides /usr/bin/editor ... sprinkle on some magic and voila. Also include this package in comps.
INFO: Eighth_Doctor | I think this is the thing that actually manages /usr/bin/editor on debian: https://salsa.debian.org/debian/sensible-utils
- Release engineering: #9522
- Policies and guidelines: N/A (not a System Wide Change)
Upgrade/compatibility impact
Will not apply to upgrades.
How To Test
Lorem ipsum dolor sit amet ...
User Experience
Lorem ipsum dolor sit amet ...
Dependencies
Lorem ipsum dolor sit amet ...
Contingency Plan
- Contingency deadline: Revert? (Seems a bit roll the giant boulder back up the hill, but this is a required field.)
- Blocks release? Maybe? If the change breaks the redirection to an editor, might be blocking.
- Blocks product? Potentially all.
Documentation
N/A (not a System Wide Change)
Release Notes
