From Fedora Project Wiki
(interim save)
 
(first draft)
Line 41: Line 41:
 
** Make necessary changes in pungi: https://pagure.io/pungi/issue/982
 
** Make necessary changes in pungi: https://pagure.io/pungi/issue/982
  
* 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 -->
+
* Release engineering: [https://pagure.io/releng/issue/7579] (a check of an impact with Release Engineering is needed)  
<!-- 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.
+
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]:  
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 -->
+
*** The Fedora Atomic Workstation iso will be renamed to Fedora-Silverblue-x86_64...
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
*** The getfedora.org webpage will need corresponding adjustments
<!-- 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 -->
+
* Policies and guidelines:  No 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. -->
 
  
 
* Trademark approval: N/A (not needed for this Change)
 
* 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 ==
<!-- 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? -->
+
This change does not affect the function of rpm-ostree rebase, which is explicitly switching
 
+
between two differently named branches anyway.
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
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.
+
* Download the Silverblue install media, and do an installation
 
+
* Verify that the media and the installer refer to Silverblue, not to Atomic Workstation
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:
 
 
 
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?
+
Apart from the name change in the installer, the user experience will not change
 
+
noticably compared to Atomic Workstation in F28.
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 ==
<!-- 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)? -->
+
No dependencies
 
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
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 mechanism: Keep old names. As an intermediate step, we can change just the user-visible names, and leave branch names and other less visible references unchanged
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Contingency deadline: beta
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
+
* Blocks release? No
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Blocks product? No
<!-- 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 ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+
Documentation about Silverblue is being collected here: https://docs.teamsilverblue.org
 
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
N/A (not a System Wide Change)
 
  
 
== Release Notes ==
 
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
+
The Atomic Workstation variant is now called Silverblue.
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
 
 
 
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
 
-->
 
 
 
[[Category:ChangePageIncomplete]]
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
 
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
 
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
 
  
<!-- Select proper category, default is Self Contained Change -->
+
[[Category:ChangeReadyForWrangler]]
[[Category:SelfContainedChange]]
+
[[Category:SystemWideChange]]
<!-- [[Category:SystemWideChange]] -->
 

Revision as of 17:21, 18 June 2018

Rename Atomic Workstation to Silverblue

Summary

The Atomic Workstation variant is being renamed to Fedora Silverblue.

Owner

  • Name: Matthias Clasen
  • Email: mclasen@redhat.com
  • Product: Workstation
  • Responsible WG: Workstation WG and Team Silverblue (formerly Atomic Workstation SIG)

Current status

  • Targeted release: Fedora 29
  • Last updated: 2018-06-18
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The Atomic Workstation is being rebranded as Fedora Silverblue, to give this project more visibility and realize its full potential for bringing new users to Fedora. There is new website, www.teamsilverblue.org, which is gathering information and resources around this effort.

Benefit to Fedora

The Atomic Workstation has been an 'undercover' effort so far that was created as a by-product of Project Atomic, but it was not widely known. The name change and the new website are aiming to make this Workstation variant more prominent. The Atomic variant is better suited for some use cases than the traditional Workstation and will make Fedora more attractive for those users.

Scope

Concrete suggested changes:

    • Change ostree repo branch name to fedora/29/x86_64/silverblue
    • Change /etc/os-release to say Silverblue in the appropriate places
    • Provide branding in fedora-logos package that says Silverblue
    • Change install media name to Fedora-Silverblue-ostree-...
  • Proposal owners:
    • Provide patches for /etc/os-release and fedora-logos
  • Release engineering: [1] (a check of an impact with Release Engineering is needed)
    • List of deliverables:
      • The Fedora Atomic Workstation iso will be renamed to Fedora-Silverblue-x86_64...
      • The getfedora.org webpage will need corresponding adjustments
  • Policies and guidelines: No changes
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

This change does not affect the function of rpm-ostree rebase, which is explicitly switching between two differently named branches anyway.

How To Test

  • Download the Silverblue install media, and do an installation
  • Verify that the media and the installer refer to Silverblue, not to Atomic Workstation

User Experience

Apart from the name change in the installer, the user experience will not change noticably compared to Atomic Workstation in F28.

Dependencies

No dependencies

Contingency Plan

  • Contingency mechanism: Keep old names. As an intermediate step, we can change just the user-visible names, and leave branch names and other less visible references unchanged
  • Contingency deadline: beta
  • Blocks release? No
  • Blocks product? No

Documentation

Documentation about Silverblue is being collected here: https://docs.teamsilverblue.org

Release Notes

The Atomic Workstation variant is now called Silverblue.