From Fedora Project Wiki
m (Add link to test instructions)
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Add Fedora Kinoite as an Emerging Edition =
+
= Add Fedora Kinoite as a variant =
  
 
== Summary ==
 
== Summary ==
  
Add Fedora Kinoite as an emerging edition of Fedora alongside Fedora Silverblue. Fedora Kinoite is an immutable desktop operating system featuring the KDE Plasma desktop and based on the same technologies as Fedora Silverblue (rpm-ostree, Flatpak, podman). Another way to view it is that Fedora Kinoite this is the Silverblue version of the KDE Spin.
+
Introduce Fedora Kinoite as a variant of Fedora alongside Fedora Silverblue.
  
 
== Owner ==
 
== Owner ==
 +
 
* Name: [[User:siosm| Timothée Ravier]]
 
* Name: [[User:siosm| Timothée Ravier]]
* Email: travier@redhat.com
+
* Email: travier AT redhat DOT com
* FESCo shepherd: [[User:Ngompa| Neal Gompa]] ngompa13 A gmail D com
+
* FESCo shepherd: [[User:Ngompa| Neal Gompa]] (ngompa13 A gmail D com)
 
* SIG: [[SIGs/KDE|KDE SIG]]
 
* SIG: [[SIGs/KDE|KDE SIG]]
  
 
== Current status ==
 
== Current status ==
[[Category:ChangePageIncomplete]]
+
 
<!-- When your change proposal page is completed and ready for review and announcement -->
+
[[Category:ChangeAcceptedF35]]
<!-- 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) -->  
 
<!-- 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-->
 
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
Line 29: Line 29:
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
-->
 
-->
* FESCo issue: <will be assigned by the Wrangler>
+
* FESCo issue: [https://pagure.io/fesco/issue/2571 #2571]
* Tracker bug: <will be assigned by the Wrangler>
+
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1927425 #1927425]
* Release notes tracker: <will be assigned by the Wrangler>
+
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/658 #658]
  
 
== Detailed Description ==
 
== Detailed Description ==
  
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+
Fedora Kinoite is an immutable desktop operating system featuring the KDE Plasma desktop. It is based on the same technologies as Fedora Silverblue (rpm-ostree, Flatpak, podman). Fedora Kinoite is to the Fedora KDE Spin what Fedora Silverblue is to Fedora Workstation.
 +
 
 +
We chose the Kinoite name for the following reasons:
 +
* KDE based projects traditionally start with a 'K'
 +
* Kinoite is a blue mineral (https://en.wikipedia.org/wiki/Kinoite), thus referring to both the 'silver' and 'blue' part of Silverblue and the blue color of the KDE logo.
 +
* "Kinoite" means "There is a tree" in Japanese (https://translate.google.com/?sl=auto&tl=en&text=kinoite&op=translate), thus referring to the 'tree' in 'ostree'.
  
 
== Feedback ==
 
== Feedback ==
 +
 +
No specific feedback received so far.
  
 
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
 
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
Line 43: Line 50:
 
== 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?
+
This will make Fedora more attractive to users that are interested in immutable OSes and underlying technologies but would prefer to use the KDE desktop environment. This should also strengthen Silverblue as more effort may be put into fixing the issues in the shared technologies.
 
 
      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.
+
== Scope ==
 
 
    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:
* Proposal owners: The KDE SIG will submit the Pungi changes needed to add this new emerging edition to the compose.
+
** The KDE SIG will submit the [https://pagure.io/pungi-fedora Pungi changes] needed to add this new variant to the compose.
 +
** The KDE SIG will submit the changes to add a new sub-package to [https://src.fedoraproject.org/rpms/fedora-release fedora-release].
 +
** The KDE SIG will maintain the Kinoite specific rpm-ostree config in the [https://pagure.io/workstation-ostree-config workstation-ostree-config repo].
  
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Other developers: N/A (not a System Wide Change)
<!-- 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 #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Release engineering: Submitted as [https://pagure.io/releng/issue/9952 #9952].
<!-- 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.  
 
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 -->
 
  
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Policies and guidelines: N/A (not a System Wide Change)
<!-- 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: [https://pagure.io/Fedora-Council/tickets/issue/344 "Fedora Kinoite" trademark requested ]
+
* Trademark approval: The "Fedora Kinoite" trademark has been [https://pagure.io/Fedora-Council/tickets/issue/344 approved]
  
* Alignment with Objectives:  
+
* Alignment with Objectives: N/A
<!-- Does your proposal align with the current Fedora Objectives: https://docs.fedoraproject.org/en-US/project/objectives/ ? It's okay if it doesn't, but it's something to consider -->
 
  
 
== 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 -->
 
 
N/A (not a System Wide Change)  
 
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.
 
 
A good "how to test" should answer these four questions:
 
  
0. What special hardware / data / etc. is needed (if any)?
+
Instructions to test the officials Fedora builds are in https://discussion.fedoraproject.org/t/how-to-test-fedora-kinoite/30405.
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 -->
+
You can still test or use the unofficial preview with the instructions from this [https://fedoramagazine.org/discover-fedora-kinoite/ Fedora Magazine article] that only need to be updated for F34 (instead of F33).
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.
 
  
Describe what Users will see or notice, for example:
+
Current limitations (last updated 2021-01-18):
  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
+
* No rpm-ostree support in Discover (graphical package and update manager). A Season of KDE is in progress to work on that.
  - 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.
+
* Partial Flatpak support in Discover.
- 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".
+
* [https://pagure.io/fedora-kde/SIG/issue/13 KDE applications are not yet available as Flatpak from the Fedora registry].
- 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 -->
 
 
N/A (not a System Wide Change)  
 
N/A (not a System Wide Change)  
  
Line 135: Line 94:
 
Report to the next release.
 
Report to the next release.
  
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)
+
* Contingency mechanism: N/A (not a System Wide Change)
 
* Contingency deadline: 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)
 
* Blocks release? N/A (not a System Wide Change)
Line 141: Line 100:
  
 
== 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. -->
 
  
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
A lot of the known issues impacting Fedora Kinoite are shared with Silverblue and their resolution is the same: https://docs.fedoraproject.org/en-US/fedora-silverblue/troubleshooting/. It is not clear for now if Kinoite specific documentation is needed but a landing page with pointer to known issues might be good.
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 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.  
+
Fedora Kinoite has been introduced as a new variant of Fedora Linux featuring the KDE desktop environment and the same technologies as Silverblue (rpm-ostree, Flatpak, podman).
-->
 

Latest revision as of 17:50, 2 June 2021

Add Fedora Kinoite as a variant

Summary

Introduce Fedora Kinoite as a variant of Fedora alongside Fedora Silverblue.

Owner

Current status

Detailed Description

Fedora Kinoite is an immutable desktop operating system featuring the KDE Plasma desktop. It is based on the same technologies as Fedora Silverblue (rpm-ostree, Flatpak, podman). Fedora Kinoite is to the Fedora KDE Spin what Fedora Silverblue is to Fedora Workstation.

We chose the Kinoite name for the following reasons:

Feedback

No specific feedback received so far.


Benefit to Fedora

This will make Fedora more attractive to users that are interested in immutable OSes and underlying technologies but would prefer to use the KDE desktop environment. This should also strengthen Silverblue as more effort may be put into fixing the issues in the shared technologies.

Scope

  • Proposal owners:
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: Submitted as #9952.
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: The "Fedora Kinoite" trademark has been approved
  • Alignment with Objectives: N/A

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

Instructions to test the officials Fedora builds are in https://discussion.fedoraproject.org/t/how-to-test-fedora-kinoite/30405.

You can still test or use the unofficial preview with the instructions from this Fedora Magazine article that only need to be updated for F34 (instead of F33).

User Experience

Current limitations (last updated 2021-01-18):

Dependencies

N/A (not a System Wide Change)

Contingency Plan

Report to the next release.

  • Contingency mechanism: 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)
  • Blocks product? N/A

Documentation

A lot of the known issues impacting Fedora Kinoite are shared with Silverblue and their resolution is the same: https://docs.fedoraproject.org/en-US/fedora-silverblue/troubleshooting/. It is not clear for now if Kinoite specific documentation is needed but a landing page with pointer to known issues might be good.

Release Notes

Fedora Kinoite has been introduced as a new variant of Fedora Linux featuring the KDE desktop environment and the same technologies as Silverblue (rpm-ostree, Flatpak, podman).