desktop June 2022

desktop@lists.fedoraproject.org

17 participants
19 discussions

Fedora Workstation WG minutes, 2022-06-28
by Chris Murphy 28 Jun '22

28 Jun '22

============================================== #fedora-meeting-2: Workstation WG (2022-06-28) ============================================== Meeting started by brainycmurf at 00:35:33 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2022-06-29/workstation.2… . Meeting summary --------------- * Present members: Allan, Matthias, Tomas, Michael, Jens, Neal (brainycmurf, 00:35:42) * Guests: Ray, Felipe (brainycmurf, 00:35:42) * Regrets: Chris (brainycmurf, 00:35:43) * Missing: (brainycmurf, 00:35:43) * Secretary: Matthias (brainycmurf, 00:35:43) * Planning for Fedora 37/38 (brainycmurf, 00:35:43) * LINK: https://pagure.io/fedora-workstation/issue/318 (brainycmurf, 00:35:47) * F37 issue list (brainycmurf, 00:35:49) * LINK: https://pagure.io/fedora-workstation/issues?status=Open&milestone=Fedora+37… (brainycmurf, 00:35:51) * Issues without a milestone (brainycmurf, 00:35:53) * LINK: https://pagure.io/fedora-workstation/issues?status=Open&milestone=none&clos… (brainycmurf, 00:35:55) * F37 wish list items: (brainycmurf, 00:35:57) * Today is the deadline for systemwide change proposals (brainycmurf, 00:36:21) * Howdy integration (brainycmurf, 00:36:23) * LINK: https://pagure.io/fedora-workstation/issue/272 (brainycmurf, 00:36:25) * GNOME Software is recommending proprietary software (brainycmurf, 00:36:37) * LINK: https://pagure.io/fedora-workstation/issue/203 (brainycmurf, 00:36:39) * Remove Boxes from the default install (brainycmurf, 00:36:56) * LINK: https://pagure.io/fedora-workstation/issue/179 (brainycmurf, 00:36:58) * Ship preininstalled apps as Flatpaks (brainycmurf, 00:37:22) * LINK: https://pagure.io/fedora-workstation/issue/269 (brainycmurf, 00:37:24) * Announcements, Status Updates (brainycmurf, 00:37:28) * The minutes from last week have been posted. (brainycmurf, 00:37:30) * LINK: https://meetbot.fedoraproject.org/fedora-meeting-2/2022-06-23/workstation.2… (brainycmurf, 00:37:32) * https://discussion.fedoraproject.org/t/fedora-docs-design-work/40062 (brainycmurf, 00:37:35) Meeting ended at 00:37:39 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * brainycmurf (61) * zodbot (7) * Allan (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions

1 0

Fedora 36 on Linux Saloon
by Luna Jernberg 28 Jun '22

28 Jun '22

https://www.youtube.com/watch?v=769-0f75Xag The last episode of Linux Saloon of June 2022 is about Fedora 36

1 0

Workstation WG meeting, 21 June (secretary: Neal)
by Allan Day 28 Jun '22

28 Jun '22

Hi all, The next meeting of the Fedora Workstation Working Group is planned for Tuesday 21 June, at 9.30 EDT. Join links: - https://bluejeans.com/395383051/ - https://www.bluejeans.com/numbers See below for the agenda. Allan -- Agenda #topic Fedora branded Slimbooks #link https://pagure.io/fedora-workstation/issue/317 #topic Planning for Fedora 37/38 #link https://pagure.io/fedora-workstation/issue/318 #topic Howdy integration #link https://pagure.io/fedora-workstation/issue/272 #topic Ship preininstalled apps as Flatpaks #link https://pagure.io/fedora-workstation/issue/269 #topic Announcements, Status Updates #info The minutes from last week have been posted. #link https://meetbot.fedoraproject.org/fedora-meeting-2/2022-06-14/workstation.2…

3 3

Automated test coverage plan
by Lukas Ruzicka 27 Jun '22

27 Jun '22

Hello, TL;DR To what extent should we test Desktop applications? How to automate them? Currently, we are testing all Desktop applications as required by the release criteria, but we have identified different approaches with different testers which resulted in several problematic bugs in the very last moments of the release cycle. We would like to avoid such a situation in the future, so we would like to discuss this matter a bit more. The release criteria state that the applications must *withstand basic functionality tests*, but it is not very clear what the basic functionality is and how we shall test it. Therefore, we would like your view on the following questions: - What should be tested in the scope of basic functionality in general? - Are there specific features or workflows you would like us to test with specific applications? - What could be set as an absolute required minimum for the Desktop applications to not block Fedora (ergo to make Fedora pass the Go/No go meeting). I would like to work on automating this so that we could have that tested very frequently. Otherwise the automation is difficult and requires a lot of time spent if we want to test for the overall functionality. Thank you very much for your help. -- Lukáš Růžička FEDORA QE, RHCE Red Hat <https://www.redhat.com> Purkyňova 115 612 45 Brno - Královo Pole lruzicka(a)redhat.com TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

2 1

Workstation WG meeting, 28 June (secretary: Matthias)
by Allan Day 26 Jun '22

26 Jun '22

Hi all, The next meeting of the Fedora Workstation Working Group is planned for Tuesday 28 June, at 9.30 EDT. Join links: - https://bluejeans.com/395383051/ - https://www.bluejeans.com/numbers See below for the agenda. Allan -- Agenda #topic Planning for Fedora 37/38 #link https://pagure.io/fedora-workstation/issue/318 #topic Howdy integration #link https://pagure.io/fedora-workstation/issue/272 #topic GNOME Software is recommending proprietary software #link https://pagure.io/fedora-workstation/issue/203 #topic Remove Boxes from the default install #link https://pagure.io/fedora-workstation/issue/179 #topic Ship preininstalled apps as Flatpaks #link https://pagure.io/fedora-workstation/issue/269 #topic Announcements, Status Updates #info The minutes from last week have been posted. #link https://meetbot.fedoraproject.org/fedora-meeting-2/2022-06-23/workstation.2…

2 1

Fedora Workstation WG minutes, 2022-06-21
by Chris Murphy 23 Jun '22

23 Jun '22

============================================== #fedora-meeting-2: Workstation WG (2022-06-21) ============================================== Meeting started by brainycmurf at 16:01:19 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2022-06-23/workstation.2… . Meeting summary --------------- * Present members: Allan, Jens, Matthias, Tomas, Michael, Neal (brainycmurf, 16:01:40) * Guests: Zac, Jack (brainycmurf, 16:01:40) * Regrets: Chris (brainycmurf, 16:01:40) * Missing: (brainycmurf, 16:01:40) * Secretary: Neal (brainycmurf, 16:01:40) * Fedora branded Slimbooks (brainycmurf, 16:01:41) * LINK: https://pagure.io/fedora-workstation/issue/317 (brainycmurf, 16:01:43) * Workstation community web page (brainycmurf, 16:02:08) * LINK: https://pagure.io/fedora-workstation/issue/319 (brainycmurf, 16:02:10) * Planning for Fedora 37/38 (brainycmurf, 16:02:23) * LINK: https://pagure.io/fedora-workstation/issue/318 (brainycmurf, 16:02:25) * Howdy integration (brainycmurf, 16:02:29) * LINK: https://pagure.io/fedora-workstation/issue/272 (brainycmurf, 16:02:31) * Ship preininstalled apps as Flatpaks (brainycmurf, 16:02:35) * LINK: https://pagure.io/fedora-workstation/issue/269 (brainycmurf, 16:02:37) * Announcements, Status Updates (brainycmurf, 16:02:41) * The minutes from last week have been posted. (brainycmurf, 16:02:43) * LINK: https://meetbot.fedoraproject.org/fedora-meeting-2/2022-06-14/workstation.2… (brainycmurf, 16:02:45) * LINK: https://wiki.gnome.org/Hackfests/BerlinMiniGUADEC2022 (brainycmurf, 16:02:52) * LINK: https://pagure.io/mindshare/issue/347 (brainycmurf, 16:02:56) Meeting ended at 16:03:00 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * brainycmurf (42) * zodbot (7) * Allan (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions

1 0

Plan / proposal: enable openQA update testing and potentially gating on Rawhide updates
by Adam Williamson 22 Jun '22

22 Jun '22

Hi folks! We've had openQA testing of updates for stable and branched releases, and gating based on those tests, enabled for a while now. I believe this is going quite well, and I think we addressed the issues reported when we first enabled gating - Bodhi's gating status updates work more smoothly now, and openQA respects Bodhi's "re-run tests" button so failed tests can be re-triggered. A few weeks ago, I enabled testing of Rawhide updates in the openQA lab/stg instance. This was to see how smoothly the tests run, how often we run into unexpected failures or problems, and whether the hardware resources we have are sufficient for the extra load. So far this has been going more smoothly than I anticipated, if anything. The workers seem to keep up with the test load, even though one out of three worker systems for the stg instance is currently out of commission (we're using it to investigate a bug). We do get occasional failures which seem to be related to Rawhide kernel slowness (e.g. operations timing out that usually don't otherwise time out), but on the whole, the level of false failures is (I would say) acceptably low, enough that my current regime of checking the test results daily and restarting failed ones that don't seem to indicate a real bug should be sufficient. So, I'd like to propose that we enable Rawhide update testing on the production openQA instance also. This would cause results to appear on the Automated Tests tab in Bodhi, but they would be only informational (and unless the update was gated by a CI test, or somehow otherwise configured not to be pushed automatically, updates would continue to be pushed 'stable' almost immediately on creation, regardless of the openQA results). More significantly, I'd also propose that we turn on gating on openQA results for Rawhide updates. This would mean Rawhide updates would be held from going 'stable' (and included in the next compose) until the gating openQA tests had run and passed. We may want to do this a bit after turning on the tests; perhaps Fedora 37 branch point would be a natural time to do it. Currently this would usually mean a wait from update submission to 'stable push' (which really means that the build goes into the buildroot, and will go into the next Rawhide compose when it happens) of somewhere between 45 minutes and a couple of hours. It would also mean that if Rawhide updates for inter-dependent packages are not correctly grouped, the dependent update(s) will fail testing and be gated until the update they depend on has passed testing and been pushed. The tests for the dependent update(s) would then need to be re- run, either by someone hitting the button in Bodhi or an openQA admin noticing and restarting them, before the dependent update(s) could be pushed. In the worst case, if updated packages A and B both need the other to work correctly but the updates are submitted separately, both updates may fail tests and be blocked. This could only be resolved by waiving the failures, or replacing the separate updates with an update containing both packages. All of those considerations are already true for stable and branched releases, but people are probably more used to grouping updates for stable and branched than doing it for Rawhide, and the typical flow of going from a build to an update provides more opportunity to create grouped updates for branched/stable. For Rawhide the easiest way to do it if you need to do it is to do the builds in a side tag and use Bodhi's ability to create updates from a side tag. As with branched/stable, only critical path updates would have the tests run and be gated on the results. Non-critpath updates would be unaffected. (There's a small allowlist of non-critpath packages for which the tests are also run, but they are not currently gated on the results). I think doing this could really help us keep Rawhide solid and avoid introducing major compose-breaking bugs, at minimal cost. But it's a significant change and I wanted to see what folks think. In particular, if you find the existing gating of updates for stable/branched releases to cause problems in any way, I'd love to hear about it. Thanks folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

3 7

[Fedocal] Reminder meeting : Workstation WG
by catanzaro＠fedoraproject.org 20 Jun '22

20 Jun '22

Dear all, You are kindly invited to the meeting: Workstation WG on 2022-06-21 from 09:30:00 to 10:30:00 US/Eastern At https://bluejeans.com/395383051/ The meeting will be about: Regular meeting for the Workstation Working Group Current Topics: https://pagure.io/fedora-workstation/issues?status=Open&tags=meeting Etherpad: https://etherpad.gnome.org/p/fedora-workstation-wg More information available at: https://fedoraproject.org/wiki/Workstation Source: https://calendar.fedoraproject.org//meeting/10142/

1 0

Re: Plan / proposal: enable openQA update testing and potentially gating on Rawhide updates
by Adam Williamson 17 Jun '22

17 Jun '22

On Fri, 2022-06-17 at 19:33 +0000, Dan Čermák wrote: > Sounds like a great addition Adam! > > Just to double check: if you have not enabled gating, then openQA will not be run at all? No, the two are separable. We can enable the tests before we turn on gating. Right now, the tests are already running, but only on the stg/lab instance of openQA - https://openqa.stg.fedoraproject.org/group_overview/2 (that shows all update tests, not just Rawhide ones). We can turn them on in production without turning on gating. Although when we don't gate, there can be an effect where an update that makes the tests fail gets pushed stable, and then *all* subsequent updates start failing the same way - this happened recently with the 389-ds-base update that broke FreeIPA deployment, after that was pushed stable, all Rawhide updates failed the FreeIPA tests until the fixed 389-ds-base reached a compose yesterday. This is one big reason I would like to enable gating. :D Without gating, I have to run around cleaning up cases like that manually - getting the issues fixed as fast as possible and then re- running failed tests once the fix lands. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Computer
by Alejandro López 17 Jun '22

17 Jun '22

Greetings, my name is Alejandro Lopez from Slimbook Computers and I'm writing this email following Matthew's advice. We are hardware company committed to the flawless integration and improvement of the end user experience with the Linux OS and the hardware it runs on. We were given the chance to work together with the KDE team back in 2016 when other laptop brands didn't even think about it, and after getting the approval from both parties, the objective of our collaboration was the birth of a modern and sleek device that excelled in performance and provided a flawless user experience for the community. The intent of this email is to let you know that the current demand for your amazing Fedora distribution is 2% from all our orders, and we think that this should change. I've sent to Matthew some general reports on which distros are currently in demand from our customers, and KDE Neon had an exponential growth versus other distros. What are your thoughts on this situation? I believe that we should work something out together to fix this. I think we should do more than offer Fedora as just another operating system (the user can choose up to 12 distributions). Thank you, -- *Alejandro López* /CEO/ <https://slimbook.es/?utm_source=mailfirma&utm_medium=free&utm_campaign=logo…> *The BEST GNU/Linux computers since 2015* alejandrolopez(a)slimbook.es www.slimbook.es <https://slimbook.es/?utm_source=mailfirma&utm_medium=free&utm_campaign=enla…> Este mensaje y sus archivos adjuntos van dirigidos exclusivamente a su destinatario, pudiendo contener información confidencial sometida a secreto profesional. No está permitida su reproducción o distribución sin la autorización expresa de Grupo Odin Soluciones Informáticas, S.L.N.E. Si usted no es el destinatario final por favor elimínelo e infórmenos por esta vía. De acuerdo con lo establecido por la Ley Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter Personal (LOPD), le informamos que sus datos están incorporados en un fichero del que es titular Grupo Odin Soluciones Informáticas, S.L.N.E. con la finalidad de realizar la gestión administrativa, contable y fiscal, así como enviarle comunicaciones comerciales sobre nuestros productos y/o servicios. Asimismo, le informamos de la posibilidad de ejercer los derechos de acceso, rectificación, cancelación y oposición de sus datos en el correo electrónico: info(a)slimbook.es

8 11

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop June 2022