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
Fedora Workstation WG minutes, 2020-09-23
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2020-09-22)
==============================================
Meeting started by cmurf at 01:42:18 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2020-09-24/workstation...
.
Meeting summary
---------------
* Rollcall (cmurf, 01:42:42)
* present: cmurf, mcatanzaro, mclasen, aday, jens, kalev, langdon,
tpopela, neal (cmurf, 01:42:44)
* regrets wg members: (cmurf, 01:42:46)
* present guests: james, felipe (cmurf, 01:42:48)
* Approve 15 Sep minutes (cmurf, 01:42:50)
* LINK:
https://meetbot.fedoraproject.org/teams/workstation/workstation.2020-09-1...
(cmurf, 01:42:52)
* AGREED: Approved - no objections (cmurf, 01:42:54)
* Announcements (cmurf, 01:42:56)
* Langdon: devconf.us is happening 24-25 September; it's free, come!
(cmurf, 01:43:02)
* LINK: https://www.devconf.info/us/ (cmurf, 01:43:04)
* Follow-ups & Status reports (cmurf, 01:43:06)
* gnome-initial-setup Google online account issue is now fixed
(cmurf, 01:43:08)
* Specify "basic" functionality for default Workstation applications
(cmurf, 01:43:10)
* https://pagure.io/fedora-workstation/issue/189 (cmurf, 01:43:12)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1880752 (cmurf,
01:43:16)
* LINK: https://gitlab.gnome.org/GNOME/sushi/-/issues/44 (cmurf,
01:43:18)
* AGREED: The Sushi issue doesn't need to be a blocker (cmurf,
01:43:28)
* ACTION: Chris to forward the decision to QA (cmurf, 01:43:30)
* Firefox 78 in Fedora 33 beta? (cmurf, 01:43:40)
* Tomáš filed a bug (cmurf, 01:43:48)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1881495 (cmurf,
01:43:50)
* ABRT is broken (cmurf, 01:43:52)
* LINK: https://pagure.io/fedora-workstation/issue/156#comment-687524
(cmurf, 01:43:54)
* GNOME Software is recommending proprietary software (cmurf, 01:44:14)
* LINK: https://pagure.io/fedora-workstation/issue/111 (cmurf,
01:44:16)
* AGREED: Deferred. (cmurf, 01:44:18)
* Open Floor (cmurf, 01:44:20)
Meeting ended at 01:45:17 UTC.
Action Items
------------
* Chris to forward the decision to QA
Action Items, by person
-----------------------
* **UNASSIGNED**
* Chris to forward the decision to QA
People Present (lines said)
---------------------------
* cmurf (58)
* zodbot (7)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
1 year, 8 months
Re: Release criteria proposal: first boot experience
by Adam Williamson
On Wed, 2020-09-16 at 19:17 -0500, Michael Catanzaro wrote:
> On Wed, Sep 16, 2020 at 10:55 pm, majid hussain <mhussaincov93(a)gmx.com>
> wrote:
> > hi,
> >
> > i'm no dev but
> >
> > i'm blind would functional include being accessible to orca the
> > screen reader?
> >
> > after all to a blind person like me having an accessible setup
> > experience is a requirement?
> >
> > or after I install the system, I would be in the dark?
> >
> > Majid
> >
> I think it makes sense to have a criterion to ensure, at minimum, that
> the screen reader is working throughout the initial setup process, yes.
> orca was completely broken in F33 until last week [1] and we only
> noticed by coincidence, since it doesn't get tested much.
>
> Unfortunately right now the login screen is not accessible (regression,
> [2]). gnome-initial-setup is pretty hard to use with just a screen
> reader. And anaconda doesn't seem to be accessible at all (at least, I
> don't know how to get orca to read anything in anaconda). So things
> would probably need to first be in better shape before we can actually
> start enforcing a blocker criterion to ensure it stays working....
Right, I pretty much agree with Michael.
The way I'd want it to work in the criteria, ideally, is we'd say
something like "all desktop requirements must be met for blind users
with assistive technology, e.g. screen reading" - i.e. rather than this
being a criterion exactly, we'd expect sufficient a11y support to be in
place that *all* the desktop criteria would be met for blind users. But
as Michael says, it sounds like we haven't really got things in good
enough shape yet that we'd be able to enforce such a requirement right
now, so that should be fixed first.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
1 year, 8 months
Fedora Workstation WG minutes, 2020-09-15
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2020-09-15)
==============================================
Meeting started by cmurf at 03:03:30 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2020-09-16/workstation...
.
Meeting summary
---------------
* Rollcall (cmurf, 03:04:47)
* present wg members: cmurf, aday, neal, tpopela, mclasen, mcatanzaro,
kalev, owen, langdon, petersen (cmurf, 03:04:49)
* regrets wg members: (cmurf, 03:04:51)
* present guests: feborges, james, (cmurf, 03:04:53)
* Approve 8 Sep minutes (cmurf, 03:04:55)
* LINK:
https://meetbot.fedoraproject.org/teams/workstation/workstation.2020-09-1...
(cmurf, 03:04:57)
* AGREED: Approved - no objections (cmurf, 03:04:59)
* Announcements (cmurf, 03:05:01)
* Kalev: GNOME 3.38.0 is in Bohdi. If the F33 release slips by a week,
that will end up in the F33 beta - which is great. (cmurf,
03:05:03)
* Michael: systemd-resolved is experiencing issues - 3 blockers
(cmurf, 03:05:09)
* Follow-ups & Status reports (cmurf, 03:05:11)
* Allan: the new 3rd party repos policy has been merged - removes the
policy blocker from #108 (cmurf, 03:05:13)
* Flatpak preferred over native (rpm) software in GNOME Software
(cmurf, 03:05:15)
* LINK: https://pagure.io/fedora-workstation/issue/151 (cmurf,
03:05:17)
* Give ABRT some lurve (cmurf, 03:06:36)
* LINK: https://pagure.io/fedora-workstation/issue/130 (cmurf,
03:06:38)
* AGREED: Deferred (cmurf, 03:06:40)
* GNOME Software is recommending proprietary software (cmurf, 03:06:42)
* LINK: https://pagure.io/fedora-workstation/issue/111 (cmurf,
03:06:44)
* AGREED: Deferred (cmurf, 03:06:46)
* Open Floor (cmurf, 03:06:48)
* AGREED: Deferred (cmurf, 03:06:50)
Meeting ended at 03:06:55 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* cmurf (61)
* zodbot (7)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
1 year, 8 months
