Line 29: | Line 29: | ||
== 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. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
Fedora includes a flatpak repo definition for Flathub in the fedora-flathub-remote package. So far, this remote | |||
was filtered by an allowlist that only made a limited subset of software from Flathub available. We've been told | |||
that it is ok for us to remove the filtering and make all of Flathub available. | |||
The filtering mechanism itself will still be there, and it will be possible for us to reinstate a filter via a package | |||
update, should the need arise in the future. | |||
== Feedback == | == Feedback == |
Revision as of 18:42, 28 June 2022
Unfiltered Flathub
Summary
The flatpak remote for Flathub will have no filtering, making all the Flathub content available in GNOME Software and via the flatpak commandline.
Owner
- Name: Workstation WG
- Email: mclasen@redhat.com
Current status
- Targeted release: Fedora Linux 37
- Last updated: 2022-06-28
- 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
Fedora includes a flatpak repo definition for Flathub in the fedora-flathub-remote package. So far, this remote was filtered by an allowlist that only made a limited subset of software from Flathub available. We've been told that it is ok for us to remove the filtering and make all of Flathub available.
The filtering mechanism itself will still be there, and it will be possible for us to reinstate a filter via a package update, should the need arise in the future.
Feedback
Benefit to Fedora
Scope
- Proposal owners:
- Other developers:
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
How To Test
User Experience
Dependencies
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
Documentation
N/A (not a System Wide Change)