Release criteria proposal: networking requirements
by Adam Williamson
Hi folks!
So at this week's blocker review meeting, the fact that we don't have
explicit networking requirements in the release criteria really started
to bite us. In the past we have squeezed networking-related issues in
under other criteria, but for some issues that's really difficult,
notably VPN issues. So, we agreed we should draft some explicit
networking criteria.
This turns out to be a big area and quite hard to cover (who'd've
thought!), but here is at least a first draft for us to start from. My
proposal would be to add this to the Basic criteria. I have left out
some wikitext stuff from the proposal for clarity; I'd add it back in
on actually applying the proposed changes. It's just formatting stuff,
nothing that'd change the meaning. Anyone have thoughts, complaints,
alternative approaches, supplements? Thanks!
=== Network requirements ===
Each of these requirements apply to both installer and installed system
environments. For any given installer environment, the 'default network
configuration tools' are considered to be those the installer documents
as supported ways to configure networking (e.g. for anaconda-based
environments, configuration via kernel command line options, a
kickstart, or interactively in anaconda itself are included).
==== Basic networking ====
It must be possible to establish both IPv4 and IPv6 network connections
using DHCP and static addressing. The default network configuration
tools for the console and for release-blocking desktops must work well
enough to allow typical network connection configuration operations
without major workarounds. Standard network functions such as address
resolution and connections with common protocols such as ping, HTTP and
ssh must work as expected.
Footnote titled "Supported hardware": Supported network hardware is
hardware for which the Fedora kernel includes drivers and, where
necessary, for which a firmware package is available. If support for a
commonly-used piece or type of network hardware that would usually be
present is omitted, that may constitute a violation of this criterion,
after consideration of the [[Blocker_Bug_FAQ|hardware-dependent-
issues|normal factors for hardware-dependent issues]]. Similarly,
violations of this criteria that are hardware or configuration
dependent are, as usual, subject to consideration of those factors when
determining whether they are release-blocking
==== VPN connections ====
Using the default network configuration tools for the console and for
release-blocking desktops, it must be possible to establish a working
connection to common OpenVPN, openconnect-supported and vpnc-supported
VNC servers with typical configurations.
Footnote title "Supported servers and configurations": As there are
many different VPN server applications and configurations, blocker
reviewers must use their best judgment in determining whether
violations of this criterion are likely to be encountered commonly
enough to block a release, and if so, at which milestone. As a general
principle, the more people are likely to use affected servers and the
less complicated the configuration required to hit the bug, the more
likely it is to be a blocker.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
2 months, 3 weeks
How to hold-as-right-click with a stylus on GNOME Shell?
by Luya Tshimbalanga
Hello team,
I attempt to use *hold*-as-*right*-*click *with a styluson GNOME Wayland
session but nothing happens. Does anyone using a convertible laptop run
a similar issue?
Tested on HP Envy x360 15 Ryzen 5 2500u.
Thanks.
**
--
Luya Tshimbalanga
Fedora Design Team
Fedora Design Suite maintainer
1 year, 4 months
socializing upcoming GNOME UI changes?
by Matthew Miller
Looks like GNOME 40 won't be just another number — there's a significant
update to the Overview, with in particular workspaces moved from vertical to
horizontal. And it looks like the dash goes at the bottom now?
The changes look well-thought through and sensible, but it's also the most
significant change to the GNOME 3 UI in a long time.
The GNOME blog here https://blogs.gnome.org/shell-dev/ is a good start, but
I think we should plan to have some Fedora Magazine articles about this as
well.
Also, is there an extension which brings back the old layout for people who
want to stay the way it is?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
1 year, 5 months
Fedora Workstation WG minutes, 2020-12-15
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2020-12-15)
==============================================
Meeting started by cmurf at 01:52:40 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2020-12-17/workstation...
.
Meeting summary
---------------
* Rollcall (cmurf, 01:53:00)
* present: chris, tomas, michael, matthias, allan, jens, neal, kalev,
owen (cmurf, 01:53:02)
* regrets: langdon (cmurf, 01:53:04)
* present guests: michel salim (cmurf, 01:53:06)
* Announcements, follow-ups, status reports (cmurf, 01:53:08)
* Potential issue with Hidden GRUB menu + boot on btrfs (cmurf,
01:53:16)
* LINK: https://pagure.io/fedora-workstation/issue/206 (cmurf,
01:53:18)
* Neal sent PR for pipewire pulse* (cmurf, 01:53:20)
* Swap out Cheese for a more generic Camera app (cmurf, 01:53:22)
* LINK: https://pagure.io/fedora-workstation/issue/166 (cmurf,
01:53:24)
* totem might move to gtk4 (cmurf, 01:53:26)
* first step would be to get gnome-camera and libaperture into Fedora
(cmurf, 01:53:28)
* Make use of malcontent in the default install? (cmurf, 01:53:30)
* LINK: https://pagure.io/fedora-workstation/issue/186 (cmurf,
01:53:32)
* AGREED: enable in rawhide (cmurf, 01:53:40)
* ACTION: kalev will enable it (cmurf, 01:53:42)
* Improve the user feedback for OOM situations (cmurf, 01:53:44)
* LINK: https://pagure.io/fedora-workstation/issue/202 (cmurf,
01:53:46)
* ACTION: michel salim to work on a change proposal (cmurf, 01:54:04)
* ACTION: chris to reach out to ben, lennart, bastien (cmurf,
01:54:06)
* Approval of 08 Dec minutes (cmurf, 01:54:08)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2020-12-09/workstation...
(cmurf, 01:54:10)
* AGREED: no objections (cmurf, 01:54:12)
* Open Floor (cmurf, 01:54:14)
* Fedora moving to matrix; offering a native Matrix client (cmurf,
01:54:20)
* LINK: https://pagure.io/fedora-workstation/issue/207 (cmurf,
01:54:22)
Meeting ended at 01:55:30 UTC.
Action Items
------------
* kalev will enable it
* michel salim to work on a change proposal
* chris to reach out to ben, lennart, bastien
Action Items, by person
-----------------------
* **UNASSIGNED**
* kalev will enable it
* michel salim to work on a change proposal
* chris to reach out to ben, lennart, bastien
People Present (lines said)
---------------------------
* cmurf (49)
* zodbot (7)
* mcatanzaro (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
1 year, 5 months
Workstation WG meetings holiday schedule
by Michael Catanzaro
Hi,
The Workstation Working Group will no meet on Tuesday, December 22 or
Tuesday, December 29 due to winter holidays. I will try to turn off
calendar reminders for these dates, but if you receive a reminder, it
should be ignored.
Our next meeting will be Tuesday, January 5.
Michael
1 year, 5 months
Fedora Workstation contributors -- do you need ARM hardware?
by Matthew Miller
Hey all. We have a program to help get Fedora OS more broadly tested on ARM
hardware. While Fedora IoT is the main focus, we also have some budget to
supply small devices directly to project contributors who are working on
Fedora Workstation. If this would help you, let me know (off-list). I'll
need your shipping address and which device (or possibly devices) you could
use from this list:
Jetson NX
Jetson Nano
Pinebook Pro
RockPro64
The Raspberry Pi 400 is also an option, but be aware that this is not going
to be magic and smooth and probably doesn't even work right now, so I'd
prefer to reserve those for people with experience in hardware enablement.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
1 year, 5 months
