[INPUT REQUESTED] fedora-chromium-config and Fedora Workstation
by Stephen Gallagher
There exists an extension[1] for Google Chrome that enables the
management of GNOME Shell extensions on extensions.gnome.org. I am
currently reworking some of the details around how the
fedora-chromium-config package works and I would like to know:
Would the Workstation WG be in favor of me adding a
fedora-chromium-config-gnome subpackage that would automatically
install the GNOME Shell Integration extension for Chrome/Chromium
browsers? I can make its installation conditional on the presence of
gnome-shell on the system if preferred.
Of the other changes I'm looking at making:
1. Enable Chrome's auto-detection of DNS-over-HTTPS. It ships as
disabled by default in Chrome currently, but it can be set to an
'auto' mode that will prefer DoH if it can determine that the DNS
server supports it.
2. Drop the user-agent extension. Ever since the advent of Chrome
v100, various sites (particularly those that rely on Cloudflare[2]
such as Gitlab.com) have been having difficulties when this is
enabled. As its utility is limited (mostly just for metrics purposes),
I think the easiest solution is to just remove it.
3. There's a KDE Plasma integration extension too, maintained by the
KDE upstream. Do we want to install that by default as well?
[1] https://chrome.google.com/webstore/detail/gnome-shell-integration/gphhapm...
[2] https://github.com/tpopela/fedora-user-agent-chrome/issues/11
1 year, 11 months
Fedora Workstation WG minutes, 2022-05-10
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2022-05-10)
==============================================
Meeting started by brainycmurf at 00:19:55 UTC. The full logs are
available athttps://meetbot.fedoraproject.org/fedora-meeting-2/2022-05-11/workstati...
.
Meeting summary
---------------
* Present members: Allan, Chris, Michael, Tomas, Matthias, Neal, Owen
(brainycmurf, 00:20:08)
* Guests: Luna Jernberg (bittin), Ben Cotton, Jack Sedita, Nishant, Jens
(2nd half) (brainycmurf, 00:20:08)
* Regrets: Jens (1st half) (brainycmurf, 00:20:08)
* Missing: (brainycmurf, 00:20:08)
* Secretary: Neal (brainycmurf, 00:20:08)
* Review the state of i18n and l10n (brainycmurf, 00:20:08)
* LINK: https://pagure.io/fedora-workstation/issue/267 (brainycmurf,
00:20:10)
* Release blocking status of basic functionality tests for apps
(brainycmurf, 00:20:14)
* LINK: https://pagure.io/fedora-workstation/issue/304 (brainycmurf,
00:20:16)
* ACTION: Clarify timings for testing the upcoming GNOME release. Put
a reminder in our own schedule so we check that the packages are
available when they're supposed to be. (brainycmurf, 00:20:43)
* Appoint a chair for the F37 cycle (brainycmurf, 00:20:55)
* LINK: https://pagure.io/fedora-workstation/issue/308 (brainycmurf,
00:20:57)
* grub: Show old kernels under a "advanced options"submenu
(brainycmurf, 00:21:05)
* LINK: https://pagure.io/fedora-workstation/issue/282 (brainycmurf,
00:21:07)
* ACTION: Chris will reach out to GRUB upstream to figure out if it's
possible to improve SB multiboot. Ticket should be closed as
deferred to upstream. (brainycmurf, 00:21:14)
* Howdy integration (brainycmurf, 00:21:17)
* LINK: https://pagure.io/fedora-workstation/issue/272 (brainycmurf,
00:21:19)
* In Repository Gnome Shell Extesions Need Some TLC (brainycmurf,
00:21:23)
* LINK: https://pagure.io/fedora-workstation/issue/254 (brainycmurf,
00:21:25)
* Announcements, Status Updates (brainycmurf, 00:21:29)
* The minutes from last week have been posted. (brainycmurf,
00:21:43)
* LINK:
https://meetbot.fedoraproject.org/teams/workstation/workstation.2022-05-0...
(brainycmurf, 00:21:45)
Meeting ended at 00:21:47 UTC.
Action Items
------------
* Clarify timings for testing the upcoming GNOME release. Put a reminder
in our own schedule so we check that the packages are available when
they're supposed to be.
* Chris will reach out to GRUB upstream to figure out if it's possible
to improve SB multiboot. Ticket should be closed as deferred to
upstream.
Action Items, by person
-----------------------
* **UNASSIGNED**
* Clarify timings for testing the upcoming GNOME release. Put a
reminder in our own schedule so we check that the packages are
available when they're supposed to be.
* Chris will reach out to GRUB upstream to figure out if it's possible
to improve SB multiboot. Ticket should be closed as deferred to
upstream.
People Present (lines said)
---------------------------
* brainycmurf (47)
* zodbot (7)
* aday (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 11 months
Proposal: changes to "default application functionality" release
criteria
by Matthew Miller
Time to talk about
https://www.fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Defau...
again!
Lots of desktop-app-related blockers this time around, and last time too. I
think we're hitting a symptom-of-our-success problem here: increasing
popularity and reviews noting how polished everything is makes us very much
want to build on that. So I understand why this is here, including the
expanded "all installed applications" Workstation criteria.
But I think we might be using the wrong tool for some of this polish, and I
think we also need to give ourselves some escape hatches.
By way of concrete example, the Photos application is meant to be a photo
organizer, so "album picker duplicates fields, preventing photo
organization" https://bugzilla.redhat.com/show_bug.cgi?id=2081291 is easy to
classify as failing the basic functionality test currently. But, it's really
painful for that to be blocking the release.
So, ideas for discussion:
1. I know we have had GNOME Test days, but this
stuff didn't come up. Presumably, it would have if someone had happened
to look at GNOME Photos. Can we formally go through
https://www.fedoraproject.org/wiki/QA:Testcase_desktop_app_basic and
https://www.fedoraproject.org/wiki/QA:Testcase_desktop_app_basic_others
much, much earlier (probably when the GNOME pre-release is available),
either as part of a test day or some other formal thing? Or is there
something else going on here that I'm not looking closely enough to see?
(Same for KDE and any other theoretical release-blocking desktops!)
2. "Basic functionality" seems scoped too broadly currently. I propose, for
the release criteria, we change this to: A) "the app doesn't crash on
launch", and B) "the app's behavior does not seem immediately
embarrassing with a few minutes of playing around with it".
As a barometer for "embarrasing", you can imagine me trying to explain
the issue to a tech reporter, and weigh how awkward I will feel saying
"this is fine" vs. how I will feel explaining that we delayed the whole
release for that same issue.
3. Problems found which are not regressions should not be blockers. We're
just hurting ourselves when we make this our forcing function to get
something fixed.
Some of these could be Prioritized Bugs, but I don't want to overload
that too much.
I propose that the teams responsible for blocking desktop deliverables
keep their own prioritized lists of this kind of problem that the team
agrees should be fixed for a good user experience. Not just add to the
general queues of bugs or tickets, but specific lists of "application
experience issues".
These lists, of course, could include problems which also don't qualify
for point #2 but which seem important. Like the Photos app issues.
(This could also extend to "desktop experience issues" rather than just
"application". Or for that matter there could be a similar mechanism for
non-desktop blocking deliverables.)
I could be convinced either way on having these in the teams' issue
trackers in pagure or whereever _or_ having it as more targets in the
blockerbugs app. I tend towards the latter: I think it might help with
the problem where blockers feel like the only obvious way to bugs tracked
and fixed. But either way, there should be lists!
4. Desktop application problems discovered during at the last minute should
not be blockers. If the problem is really going to impact a lot of
people, it should have been discovered in the beta. (Exception for _new_
regressions, of course.) By the time we're in final freeze, this ends up
being hero work for everyone.
I don't know how to phrase this in a way that doesn't make Adam sad with
me, but maybe something like: Desktop application blockers discovered
during the final freeze are automatically waived unless the relevant Spin
or Edition team decides otherwise.
That lets us still block if something is really bad and just happened to
slip through.
5. Okay, and... bigger: we should aim for more approaches which let us
decouple as much as possible from the Release. (My grand hope is that we
can release every deliverable on its own schedule, but I also understand
the _highly aspirational_ nature of that idea. But...) What if we could
just easily ship GNOME Photos from GNOME 41 until a fix is found in the
updated one?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
1 year, 11 months
Fwd: [Test-Announce] Fedora 36 Candidate RC-1.5 Available Now!
by Adam Williamson
Hey folks! Please see attached. Due to some late-breaking blockers and
fixes, we're now up to RC5 for F36 Final. Go/no-go is tomorrow. If
folks can help with testing, that'd be great.
Here's a quick summary of the changes between the RC composes:
RC1 -> RC2
gtk4-4.6.2-3.fc36 to fix #2071228
clevis-pin-tpm2-0.5.2-1.fc36 rust-tpm2-policy-0.6.0-1.fc36 to fix FTBFS
RC2 -> RC3
wpa_supplicant-2.10-4.fc36 to fix #2072070
tracker-miners-3.3.0-2.fc36 to fix #2079308
mutter-42.0-6.fc36 to fix #2081070
openssl-3.0.2-4.fc36 to fix #2069239
gzip-1.11-3.fc36 to fix #2073312
kernel-5.17.5-300.fc36 for #2080694
snapper-0.10.1-1.fc36 for FTBFS
selinux-policy-36.8-1.fc36 for #2065940
livecd-tools-30.0-1.fc36 for #2007045
xz-5.2.5-9.fc36 for #2080938
xdg-desktop-portal-1.12.4-1.fc36 for #2060990
sssd-2.7.0-1.fc36 for #2077856
gr-osmosdr-0.2.3-21.20210217gita100eb02.fc36 to fix FTBFS
RC3 -> RC4
firefox-100.0-2.fc36 for #2081488
RC4 -> RC5
sushi-41.2-1.fc36 for #2067969
gnome-photos-42.0-2.fc36 for #2079344 #2081291
aws-2020-7.fc36 matreshka-20.1-10.fc36 templates_parser-11.8.0-30.fc36 for FTBFS
So, RC3 had quite a lot of change in it. RC4 and RC5 are much more
limited. So we can count most tests from RC3 or later as being valid
for RC5; tests of Firefox, Nautilus and GNOME Photos should be re-
confirmed.
I have transferred results from RC3 and RC4 to RC5 in the matrix where
appropriate, leaving out things that are considered 'sanity tests'
(basic boot and install tests) which we try to run on every compose to
rule out some kind of cosmic bit-flip unexpectedly breaking an image.
So any spaces left on Basic/Beta/Final tests are ones we should try to
fill.
Special note on the Active Directory tests: it looks like tflink and
sgallagh ran these on RC1, thanks a lot. Since we did get a new sssd
between then and RC5 it would be *nice* if we could run them again, but
if not we can probably run with the RC1 results in the end.
Thanks again everyone!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 year, 11 months
Fedora Workstation WG minutes, 2022-05-03
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2022-05-03)
==============================================
Meeting started by brainycmurf at 17:27:05 UTC. The full logs are
available athttps://meetbot.fedoraproject.org/fedora-meeting-2/2022-05-03/workstati...
.
Meeting summary
---------------
* Present members: Allan, Tomas, Chris, Matthias, Owen, Neal
(brainycmurf, 17:27:32)
* Guests: Ben (brainycmurf, 17:27:32)
* Regrets: Jens (brainycmurf, 17:27:32)
* Missing: (brainycmurf, 17:27:32)
* Secretary: Chris (brainycmurf, 17:27:32)
* Release blocking status of basic functionality tests for apps
(brainycmurf, 17:27:33)
* LINK: https://pagure.io/fedora-workstation/issue/304 (brainycmurf,
17:27:34)
* Fedora final release criterion specifying "basic functionality"
(brainycmurf, 17:27:39)
* LINK:
https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Default_a...
(brainycmurf, 17:27:41)
* LINK:
https://fedoraproject.org/wiki/Fedora_36_Final_Release_Criteria#Default_a...
(brainycmurf, 17:29:24)
* LINK:
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
(brainycmurf, 17:29:29)
* Parental Controls app getting poor reviews (brainycmurf, 17:29:31)
* LINK: https://pagure.io/fedora-workstation/issue/263 (brainycmurf,
17:29:33)
* AGREED: Parental Controls should not be visible in g-c-c
(brainycmurf, 17:29:44)
* grub: Show old kernels under a "advanced options"submenu
(brainycmurf, 17:29:50)
* LINK: https://pagure.io/fedora-workstation/issue/282 (brainycmurf,
17:29:52)
* Howdy integration (brainycmurf, 17:29:54)
* LINK: https://pagure.io/fedora-workstation/issue/272 (brainycmurf,
17:29:56)
* In Repository Gnome Shell Extesions Need Some TLC (brainycmurf,
17:29:58)
* LINK: https://pagure.io/fedora-workstation/issue/254 (brainycmurf,
17:30:00)
* Announcements, Status Updates (brainycmurf, 17:30:02)
* Go/no go is this Thursday (brainycmurf, 17:30:04)
* Fedora 36 flatpak runtime is almost ready (brainycmurf, 17:30:06)
* F36 release party May 13-14 (brainycmurf, 17:30:08)
* Neal: Fedora Media Writer 5.0 is nearly ready, now using Qt6 with
native styles on Windows and Mac, and QGnomePlatform for Linux on
GNOME (brainycmurf, 17:30:10)
* The minutes from last week have been posted. (brainycmurf,
17:30:13)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-04-26/workstation...
(brainycmurf, 17:30:17)
Meeting ended at 17:30:36 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* brainycmurf (71)
* zodbot (7)
* aday (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 11 months
