This ticket is being posted on behalf of the Fedora Workstation Working Group.
Two years ago, the Council approved the 3rd party software policy. This policy is being used by Fedora Workstation, but we have been unable to build a successful UI around it, largely due to the nature of the policy.
We would like to explore modifying the policy so that we can reliably integrate the 3rd party repos into the workstation experience.
The 3rd party repos are a collection of repositories which can be enabled on Fedora Workstation. Each one:
Today there are four 3rd party repositories, containing the following software: Google Chrome, Steam, the proprietary NVIDIA driver, and PyCharm.
The repos are shipped in a package called fedora-workstation-repos, which must be installed by the user. Theoretically this is supposed to be done as part of a step in initial setup (or through GNOME Software, as a backup).
fedora-workstation-repos
Once installed, the content of each repo can be searched for and installed (though users must explicitly enable each repo as part of the install process).
The main problem with the 3rd party repo policy is that it requires the 3rd party repos to be installed from a package. This makes it difficult (and in some cases impossible) to add a straightforward UI for enabling the 3rd party repos. This can be seen in specific issues like:
gnome-initial-setup
Installing the 3rd party repos through a package is also a critical issue for Silverblue, since it requires package layering, which requires a restart to even start using the repositories.
The Workstation WG would love to discuss solutions to these practical problems, while continuing to retain the principles behind the original 3rd party repo policy. One potential solution that we have come up with would be to:
This arrangement would prevent users from being exposed to any sight of the 3rd party repo content until they have explicitly enabled them. It would also enable us to build a functional and reliable UI on top of the 3rd party repos.
We look forward to your feedback and discussing this further!
TL;DR: we want to install disabled proprietary repo files into /etc/yum.repos.d by default.
I think the proposal is a fine solution, so long as the "hey this is proprietary" is both clear and friendly.
Thanks @bcotton . I'm sure we could run the proposed UI past the council, to get your input.
I am +1
I'm sure we could run the proposed UI past the council, to get your input.
That would be great @aday.
With two +1 in the ticket and @psabata's +1 in today's meeting, this is approved.
Metadata Update from @bcotton: - Issue close_status updated to: approved - Issue status updated to: Closed (was: Open)
Thanks everyone! I assume that we'll need to update some of the documentation around this. I'll follow up separately.
Login to comment on this ticket.