Changes/Silverblue

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

• Other developers:
  • Change lorax templates to refer to new branch name
  • Change anaconda install media: https://github.com/rhinstaller/anaconda/issues/1504
  • Create a Silverblue install class in anaconda: https://github.com/rhinstaller/anaconda/issues/1505
  • Make necessary changes in pungi: https://pagure.io/pungi/issue/982

• 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)

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)