Default plymouth theme
by Stephen Gallagher
I was reading Fedora Magazine today and there was a really interesting
article up about setting the theme for plymouth[1].
It led me to wonder: why is "Charge" the default theme for Fedora
Workstation instead of something with stronger branding like "Spinfinity"?
In particular, I think Spinfinity would be more pleasant for people to see
while performing offline updates (rather than a monochrome thought bubble)
for that extended period.
I realize that this is probably going to get into an argument about the
relative merits of subjective interpretations of beauty, so let me try to
frame the conversation a little better:
I suspect that the primary reason for Charge is that it transitions more
seamlessly into the GDM login screen (having similar colors). So, is there
a way we could get more visual flare (and product identity) there without
losing the transition benefits? Is it worth considering a re-theming of
BOTH plymouth and GDM for Fedora?
[1] https://fedoramagazine.org/howto-change-the-plymouth-theme/
6 years, 2 months
Starting an Atomic Workstation SIG
by Owen Taylor
Hi desktop-list and others,
There was a lot of interest around Atomic Workstation at DevConf.cz - there
were three talks specifically about Atomic Workstation (*), in addition to
quite a few related talks.
We should try to catch some of this momentum and figure out how to move the
project forward. My thought is that it would be useful to set up a regular
IRC meeting, probably every two weeks - more or less an Atomic Workstation
SIG.
Areas of work that come to mind would be:
* Keeping the OSTree and installer composing, installing, and working
* Increasing automated testing done on the OSTree image
* Making sure that open technical questions and pull requests are dealt
with
* Documention, including best practices for development on an OSTree system
* General initiative planning - milestones, promotion, etc.
* Figuring out technical next steps
If you are interested and think you would regularly attend meetings and
participate, please add yourself to:
https://fedoraproject.org/wiki/Workstation/AtomicWorkstation/SIG
or email me. Please include your timezone, and whether you would would be
able to make a meeting opposite weeks from the workstation working group -
Monday 13:00 UTC - that's one time that comes to mind, but I'm not at at
all tied to it.
I can handle agenda and running the meeting for now.
Thanks!
Owen
(*)
Sanja Bonic and Colin Walters - https://www.youtube.com/watch?v=a4IPWlfkJSo
Kalev Lember - https://www.youtube.com/watch?v=Yc7lvkl5atE
Jonathan Lebon - https://www.youtube.com/watch?v=7c3GdfhWzcc
6 years, 2 months
some atomic questions
by Matthias Clasen
All this interest in atomic workstation made me dust off my vm.
While upgrading it, I ran into a number of questions that I couldn't find
any answers
for. This might be useful information to put on a new atomic workstation
website.
1) How do I find out what I'm running ?
I guess the answer to this is rpm-ostree status, but what does
it actually tell me ?
● atomicws:atomicws/fedora/x86_64/continuous
Version: 26.447 (2018-01-29 04:58:49)
BaseCommit:
ba986d4649f08705185ba1ce7208e72d149b1e35314d112a86348cb1d61f6f52
LayeredPackages: powerline
It would be nice to explain this output a bit - I assume the first
'atomicws' is a repository name, and 'atomicws/fedora/x86_64/continuous' is
a branch name. Version 26.447 may indicate that I am running some version
of Fedora 26.
Unfortunately, I haven't really seen the gnome-software support
in action yet, but I hope it shows this information as well.
2) How do I get the latest updates ?
rpm-ostree upgrade is easy enough (once I've found it).
3) How do I upgrade to a newer release ?
4) How do I find out what branches are available to rebase to ?
5) Where is the repo configuration stored ?
This is where I got stuck - I could not find any answers to these.
Very frustrating, a normal user would have given up here.
Eventually, Kalev told me to create a file in /etc/ostree/remotes.d/ with
some content, and then I figured out to run
ostree remote refs fedora
to see the branches in the repo, and
rpm-ostree rebase fedora:fedora/27/x86_64/workstation
to upgrade to one of them. I blindly picked this branch, since
I have no idea what the difference between
fedora/27/x86_64/testing/workstation
fedora/27/x86_64/updates/workstation
fedora/27/x86_64/workstation
might be...
Also, I had to disable gpg verification, since I didn't know where
to find the key for that repo.
We need to make the rpm-ostree plugin support distro-upgrades
inside gnome-software. And also make this information available
in some obvious place.
6 years, 2 months
Rotating WG chair
by Paul W. Frields
As we discussed in the meeting earlier this week (sorry for not
following up sooner), I'd like to start a process of rotating the
chair duties for the Workstation working group meeting.
The next meeting is scheduled for Monday, January 29. However, I
believe that many of us (at least Matthias, Christian, Owen, Kalev,
Jens, myself) will be either in meetings or traveling back from the
DevConf.cz event in Brno that day. So we could start this with the
Monday, February 12 meeting.
I'd intended to propose an alphabetical rotation. But if folks would
rather volunteer, that's fine with me. It seems to work well in
FESCo, which also rotates chairs. If you're interested, just reply
here.
--
Paul W. Frields <pfrields(a)redhat.com>
Manager, Fedora Engineering - Emerging Platform
http://redhat.com -- http://opensource.com
6 years, 2 months
Release criteria proposals: Edition branding and installer
customizations
by Adam Williamson
sgallagh and I both noticed that the release criteria do not currently
include any requirements around Edition branding or installer
customizations. We think they probably should. Thus, we're proposing
the following new criteria. They would be in a new section for each
page, something like "Edition requirements" or something like that,
probably with a brief explanation of what "Editions" are outside of any
specific criterion text.
For Beta:
== Installer customization ==
For each Edition, all significant functional customization of installer
behavior that are intended to be a part of that Edition must take
effect on that Edition's installable release-blocking images.
footnote: 'Significant functional?': significant functional
customization would usually include, for e.g., changes to the default
filesystem and firewall configuration. The WG or SIG responsible for
each Edition has the definitive say on what is or is not considered a
'significant functional customization' for that Edition.
For Final:
== Self-identification ==
For each Edition, the installer must be clearly identified as that
Edition in all of that Edition's installable release-blocking images.
Also, for any deployment of that Edition in accordance with the rest of
these criteria, the relevant fields in {{filename|/etc/os-release}}
must include the correct Edition name.
Thoughts, comments, suggestions, flames? Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
6 years, 2 months
[Talking Points] Desktop Team
by Alberto Rodriguez Sanchez
Hi Desktop Team,
I'm Alberto from the marketing team,
Talking points are key highlights of the new release. They should be
compelling, but they will not necessarily be comprehensive. There are
different types of talking points for different types of people:
general desktop users/everyone, developers, and sysadmins. For the
Fedora 28 cycle, we will also have talking points to address some of
the Spins. They are meant to provide a short, effective answer to the
question, "What cool stuff is in the latest release of Fedora?"
Each cycle, the Marketing team compiles a short list of approximately
three talking points for each of these audiences for the upcoming
release.
So, What is new from the Desktop Team side??
If you have a talking point that you feel meets the criteria found on
the talking points SOP page at
https://fedoraproject.org/wiki/Talking_points_SOP,
Best Regards,
--
Alberto Rodriguez Sanchez <bt0dotninja(a)fedoraproject.org>
6 years, 2 months
Where to find moz-grab-langpacks?
by Peter Oliver
The SRPM for Firefox contains the following source:
Source1: firefox-langpacks-%{version}%{?pre_version}-20171113.tar.xz
A README contained in this archive mentions:
Generated by moz-grab-langpacks.
Can anyone point me in the direction of where moz-grab-langpacks can be found?
--
Peter Oliver
6 years, 3 months
package cleanup after offline updates
by Chris Murphy
Hi,
Fedora 27 Workstation, using GNOME Software for offline updates, with
updates-testing enabled. I'm noticing an accumulation of long since
applied RPMs in
/var/cache/PackageKit/27/metadata/updates-testing/packages
What's responsible for package cleanup after applying updates? I'm
wondering if it's possible cleanups happen correctly for updates, and
there's a bug where cleanup isn't happening for updates-testing?
--
Chris Murphy
6 years, 3 months
