#meeting:fedoraproject.org log

<@cmurf:fedora.im>

20:26:27

!startmeeting Workstation WG - 2025-06-03

<@meetbot:fedora.im>

20:26:28

Meeting started at 2025-06-04 20:26:27 UTC

<@meetbot:fedora.im>

20:26:28

The Meeting name is 'Workstation WG - 2025-06-03'

<@cmurf:fedora.im>

20:26:35

<@cmurf:fedora.im>

20:26:35

!info Present members: Michael, Matthias, Chris, Allan, Michel, Nieves

<@cmurf:fedora.im>

20:26:35

!info Regrets:

<@cmurf:fedora.im>

20:26:35

!info Missing:

<@cmurf:fedora.im>

20:26:35

!info Secretary: Allan

<@cmurf:fedora.im>

20:26:35

!info Guests: Barry, Bohdan, Lee

<@cmurf:fedora.im>

20:26:35

<@cmurf:fedora.im>

20:26:35

!topic Update policy

<@cmurf:fedora.im>

20:26:35

We had some major breakage due to a Mutter update. A lot of users were affected. In this case the update went to stable very quickly.

<@cmurf:fedora.im>

20:26:35

!link https://bugzilla.redhat.com/show_bug.cgi?id=2369567

<@cmurf:fedora.im>

20:26:35

Could our update policy prevent this type of issue? For example, we could keep updates in testing for a longer period of time.

<@cmurf:fedora.im>

20:26:35

Counter argument - core/important packages could have a longer test period.

<@cmurf:fedora.im>

20:26:35

A longer test period would increase the time required to fix regressions.

<@cmurf:fedora.im>

20:26:35

!link https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#karma-requirements

<@cmurf:fedora.im>

20:26:35

We have the authority to set our own updates policy.

<@cmurf:fedora.im>

20:26:35

Currently policy is:

<@cmurf:fedora.im>

20:26:35

+3 karma or 7 days in testing with no negative karma.

<@cmurf:fedora.im>

20:26:35

For critical path updates, +3 karma or 14 days with no negative karma. Critical path is defined in comps.

<@cmurf:fedora.im>

20:26:35

We think that it's possible that negative karma disables automatic push, but it is possible to reenable it.

<@cmurf:fedora.im>

20:26:35

Allan: a minimum testing period would make sense, irrespective of the amount of positive karma an update receives.

<@cmurf:fedora.im>

20:26:35

We can override the policy for special cases, if necessary?

<@cmurf:fedora.im>

20:26:35

!agreed We would like to add a minimum test period to the policy.

<@cmurf:fedora.im>

20:26:35

<@cmurf:fedora.im>

20:26:35

!action Nieves to talk to Adam about making the change

<@cmurf:fedora.im>

20:26:35

!topic Announcements, follow-ups, status reports

<@cmurf:fedora.im>

20:26:35

!meetingname workstation

<@cmurf:fedora.im>

20:26:35

!chair Matthias

<@cmurf:fedora.im>

20:26:35

!link https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.org/message/THPOLJYF7XKAYXPRNJFV7AKWZMW3V4CF/

<@cmurf:fedora.im>

20:26:35

<@cmurf:fedora.im>

20:26:35

Matthias gave a workstation update at the Fedora release party last Thursday. I hope it went ok.

<@cmurf:fedora.im>

20:26:35

Potential future topic: invite Adrian Vovk to talk about his work on gdm and gnome-session.

<@cmurf:fedora.im>

20:26:35

Flock is happening this week

<@cmurf:fedora.im>

20:26:35

<@cmurf:fedora.im>

20:26:35

!topic Open Floor

<@cmurf:fedora.im>

20:26:35

<@cmurf:fedora.im>

20:26:35

!topic Gemini notes for this meeting

<@meetbot:fedora.im>

20:26:35

The Meeting Name is now workstation

<@cmurf:fedora.im>

20:26:58

!endmeeting