We currently have a policy for applications and launchers:
https://fedoraproject.org/wiki/Workstation/Guidelines/Applications_and_Launchers
It gives minimum standards that apps installed by default must meet, and it is incorporated by reference into our final blocker criteria. However, in handling the blivet-gui case I realized we do not seem to have any blocker criterion that we can use in case an app we have not approved suddenly appears in the default install. The applications and launchers guidelines were not originally meant to cover this, but it seems appropriate to add, at the end of the section "For launchers":
"App launchers installed by default must be approved by the Workstation WG."
This will allow us to use the blocker bugs process to track issues like #14.
(Note that we've previously approved the inclusion of future core GNOME apps, with a few exceptions, so approval would in practice be needed only for other stuff. In practice we would use this rule whenever something unexpected shows up.)
Metadata Update from @pfrields: - Issue tagged with: meeting
I've proposed this to the QA team here: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/WTNURCPFQ26DK55M7SDXV4BOIJVECQIX/
This issues was discussed at today's Workstation WG meeting and then later at today's blocker review meeting with the QA team. At the Workstation WG meeting, we agreed to make my proposed policy change "App launchers installed by default must be approved by the Workstation WG" contingent on my running this past the QA team to ensure they're OK with it. Stephen Gallagher suggested that the new text is somewhat out of place in the applications and launchers guidelines, which is a fair point, and further proposed that the WG already has the power to designate particular bugs as blockers. (I didn't know this, and we should use the power sparingly.) So I propose that we leave the policy unchanged, and I will close this issue and update #14 .
Metadata Update from @catanzaro: - Issue close_status updated to: Won't fix - Issue status updated to: Closed (was: Open)
Metadata Update from @catanzaro: - Issue untagged with: meeting
Log in to comment on this ticket.