Workstation WG meeting recap 2018-Jul-30
by Paul W. Frields
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-2/2018-07-30/workstation...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-2/2018-07-30/workstation...
Log: https://meetbot.fedoraproject.org/fedora-meeting-2/2018-07-30/workstation...
* * *
=================================
#fedora-meeting-2: Workstation WG
=================================
Meeting started by stickster at 13:06:57 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-07-30/workstation...
.
Meeting summary
---------------
* roll call (stickster, 13:07:07)
* Agenda is officially empty, see... (stickster, 13:09:01)
* LINK:
https://pagure.io/fedora-workstation/issues?status=Open&tags=meeting
(stickster, 13:09:03)
* aday suggests we look at first run experience (stickster, 13:09:35)
* First run experience (stickster, 13:09:40)
* LINK: https://pagure.io/fedora-workstation/issue/57 (stickster,
13:10:52)
* Seems like fixing g-i-s handoff to session probably will take
precedence over new animation/tour work (which is bigger anyway)
(stickster, 13:28:55)
* g-i-s has some experience regressions to deal with as well
(stickster, 13:29:21)
* aday proposes we need new greeter before we add animations, or else
it will mean repeat/redundant work (stickster, 13:30:13)
* aday proposes new artwork is needed at minimum for stopgap, though
(stickster, 13:30:37)
* All other business / Open floor (stickster, 13:38:28)
* aday is lead on design side for greeter redesign, but needs help
from devs (stickster, 13:41:04)
* ACTION: stickster file ticket for gnome-shell-chrome inclusion (or
renamed package) (stickster, 13:47:57)
* ACTION: mclasen gather info on how g-s-chrome works across browsers
and bring to ticket for vote (stickster, 13:48:22)
* LINK: https://pagure.io/teamsilverblue/issue/22 (mclasen,
13:50:20)
* LINK:
https://pagure.io/dusty/failed-composes/issue/580#comment-523684
(mclasen, 13:54:41)
Meeting ended at 13:57:57 UTC.
Action Items
------------
* stickster file ticket for gnome-shell-chrome inclusion (or renamed
package)
* mclasen gather info on how g-s-chrome works across browsers and bring
to ticket for vote
Action Items, by person
-----------------------
* mclasen
* mclasen gather info on how g-s-chrome works across browsers and
bring to ticket for vote
* stickster
* stickster file ticket for gnome-shell-chrome inclusion (or renamed
package)
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* stickster (56)
* mclasen (29)
* aday (19)
* zodbot (12)
* otaylor (11)
* juhp (10)
* cschalle (3)
* ryanlerch (2)
* kalev (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
4 years, 7 months
Re: Release criteria proposal: installing / removing software
by Adam Williamson
On Tue, 2018-07-17 at 15:09 -0600, Nathanael D. Noblet wrote:
> On Mon, 2018-07-16 at 17:32 -0700, Adam Williamson wrote:
> >
> > Basic:
> >
> > "The installed system must be able appropriately to install, remove,
> > and update software with the default console tool for the relevant
> > software type (e.g. default console package manager). This includes
> > downloading of packages to be installed/updated."
> >
>
> Just a small typo/grammar correction I think.
>
> "The installed system must be able to appropriately install, remove,
> and update.."
>
> just moved the 'to' infront of appropriately.. Apologies if that's a
> dumb thing to nit-pick. Otherwise looks good to me.
This is the old English grammatical chestnut known as the "split
infinitive" (or rather, in the case of my draft, the infinitive is
intentionally *not* split).
Both forms are used, and mean the same. The one I chose is sometimes
considered the more 'classically' correct, and some stick-in-the-muds
consider your form to be incorrect. Wikipedia has quite a good article
on it:
https://en.wikipedia.org/wiki/Split_infinitive
I instinctively like the non-split form here because, to me, it
emphasizes more clearly that "appropriately" applies to all three
actions.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
4 years, 8 months
Release criteria proposal: installing / removing software
by Adam Williamson
Hi, folks!
It's been noted a few times before that we have a release criterion
that requires *updating* packages (or, these days, 'software', to cover
things like modules) to work...but we don't have criteria covering
other basic software management tasks, notably installing and removing.
There is a possible justification for this: so long as update works,
bugs in installation and removal can be fixed with updates. But really,
it seems reasonable to me that we should require basic
installation/removal of packages (and modules, and anything else we may
choose to consider release critical now or in future, e.g. flatpaks,
Shell extensions...) to work on release.
So, I'm proposing we modify the existing Basic and Beta criteria that
cover only updates, to also cover installation and removal. I like this
a bit more than adding separate criteria as the footnotes would be very
similar, and combining allows the footnotes to be shared.
So, the Basic criterion would change from:
"The installed system must be able to download and install appropriate
updates with the default console tool for the relevant update type
(e.g. default console package manager)."
to:
"The installed system must be able to install, remove, and install
appropriate updates for software with the default console tool for the
relevant software type (e.g. default console package manager). This
includes downloading of packages to be installed/updated."
the Beta criterion would similarly change from:
"The installed system must be able to download and install appropriate
updates with the default tool for the relevant update type in all
release-blocking desktops (e.g. default graphical package manager)."
to:
"The installed system must be able to install, remove, and install
appropriate updates for software with the default tool for the relevant
update type in all release-blocking desktops (e.g. default graphical
package manager). This includes downloading of packages to be
installed/updated."
the footnotes would be tweaked to refer more generically to 'software'
and stuff instead of 'updates', just kinda logical changes to reflect
the broadened criterion; I can go into detail on that if anyone wants.
Obviously if the criterion change is agreed upon, we will add test
cases to the test matrices.
Thoughts, comments, suggestions, acks and nacks? Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
4 years, 8 months
