Currently we have coredumpctl installed by default, but it doesn't work
because core dumps are consumed by ABRT instead. I'd like to get
coredumpctl working out-of-the-box. We can do this by changing our
systemd presets  to disable abrt-ccpp.service.
ABRT will continue to function thanks to the ABRT developers' work on
coredumpctl integration via abrt-vmcore.service. There is a somewhat-
reduced feature set, but I've been running this for several months
happily and I haven't noticed any issues; my crashes are being reported
to FAF, and I can manually report to Bugzilla. See  for details.
This might be slightly controversial for two reasons. First, the big
change here is that core dumps will appear in the magical and super-
awesome coredumpctl tool in addition to ABRT, but would no longer be
created in the cwd when ulimit is set appropriately (we would need to
feature that in the release notes). This aligns us with upstream
systemd behavior, but diverges from Debian and Ubuntu, which still
create the old-style coredumps in the cwd. Second, my understanding is
that the ABRT developers prefer to improve abrt-cli and tell people to
use that rather than coredumpctl. But as coredumpctl is very mature
(nicer) and cross-distro so it gets many more contributors, I
definitely prefer to instruct people to use coredumpctl instead for
We could totally do this change for F24 as well as it should be just a
one-line change, but in the spirit of beta freeze I figure it's
probably best left for F25.
Recently the Workstation working group agreed to match the GNOME apps
we install by default in Fedora with upstream GNOME's core apps. We
will by default sync our default apps to upstream's, and make
exceptions only for exceptional reasons if when proposed on this list.
This adds a bit more cement to our status as the best GNOME
distribution with minimal divergence from upstream.
I worked upstream with designers and release team to move many
desirable apps into core, to better match what we're currently shipping
in Fedora. I also created a gnome-incubator metamodule upstream, which
is where we'll put apps that we want to be core apps by design, but
which we recognize are not yet ready to be installed by default in
distributions. Currently that is home to bijiben, gnome-boxes, gnome-
calendar, gnome-dictionary, gnome-music, and gnome-photos.
Here is how we currently diverge from the new upstream recommendations:
Apps missing from Fedora: epiphany, gnome-logs
Extra apps in Fedora: bijiben, evolution, gnome-boxes, shotwell, rhythmbox
I see little value in discussing Epiphany again right now. Let's make an exception for that.
I have added Logs in Fedora just now, as I expect that will be uncontroversial and I don't see any value in diverging from upstream here.
Bijiben is just not very good yet, and it's not under active
development. There's no good reason for us to diverge from upstream
here, and I expect it will be uncontroversial, so I've dropped it.
I guess Evolution might be controversial; I use it religiously, and
many of you probably do too. But the user interface is complex and
confusing; users should not be exposed to this by default, barring
drastic UI changes that are outside the scope of the Evolution project.
Evolution is a great mail client for power users, but I'm confident
that the average user will be better off with webmail services; folks
who want a desktop client can simply install one, after all. We intend
to replace it with GNOME Mail eventually, but nobody has started
developing it yet. I propose we drop Evolution, but I have not done so
yet, pending further discussion.
Boxes has too many serious bugs right now, so it cannot go into gnome-
core yet, but we intend it to eventually. Since this is a significant
application, I have not yet removed it from our default install,
pending further discussion. My main concern is that it would look odd
for us to remove such a significant app from the default install, then
bring it back in a year or two. On the other hand, users won't notice a
thing unless they make a habit of reinstalling Fedora, and it's not
good to include apps we can't fully recommend. It's not clear to me
what choice is best here.
I propose we make temporary exceptions to keep Shotwell and Rhythmbox, until their intended replacements, Photos and Music, move into
upstream's GNOME core moduleset. That will very likely happen for
Photos for F25. I'm less certain about Music.
I've just now gotten around to testing fedora 25. It's a fantastic
release, great work everyone! There are two bugs, minor ones both of
them, that I thought I'd mention though. The shortcut to enable the
screen reader and gnome's accessibility, alt+super+s, doesn't seem to
work on the gdm welcome screen or in gnome shell itself. Of course
pressing alt+f2 and typing 'orca' works just fine. The second bug is
that the keystrokes to raise and lower the volume, bound to xf86-volume
up and xf86-volume down respectively, don't seem to work, even though
I've checked and they are bound properly. I'm not certain if these are
fedora or gnome shell bugs, but just thought I'd report them. Either way
they're not showstoppers by any means. I wish I'd tested the alpha or
beta releases, I'd have caught them much earlier and I'd have reported them.
Reminder that we meet on Wed 2016-Jun-22 at 1400 UTC (10:00am US-EDT).
* Topic suggested by mcatanzaro. Status and plan for F25?
* Fedora 25 Workstation
* What are our next steps for Flatpaks?
* What are our next steps for an rpm-ostree based version?
* Overall themes/plans for F25?
Suggestions for the agenda are gratefully accepted.
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
In order to support the upcoming release of Fedora 24, the Fedora Marketing
team is preparing a press release announcement for next week.
While the tone of the article is about where we need it to be, we would
like to solicit input from as many groups as possible for new features that
you feel should have highlighted.
Please visit the discussion area of the release page if you have any
feedback and we will try to include as much as we can.