…and I too. :)
In the release blog post of GNOME v3.24, the recipes application was promised:
> This release also includes a new Recipes application, which contains recipes contributed by members of the GNOME community. It has an extensive set of features for adding and editing recipes, creating shopping lists, adjusting quantities and even has a hands-free cooking mode.
https://www.gnome.org/news/2017/03/gnome-3-24-released/
Now, Fedora 26 is using v 3.24, but this application is not there?
This should be fixed until the final Fedora 26 release as, well…, it has been promised. And breaking promises is not good. It makes users sad… ;)
Originially raised in https://bugzilla.redhat.com/show_bug.cgi?id=1462008, where Zbigniew Jędrzejewski-Szmek also commented:
> I think it would be a shame not to package it in time for F26 final.
I agree… so could someone help here?
Best regards,
rugk

Hi,
As discussed at today's WG meeting, I've prepared a draft change page
for reducing initial setup redundancy:
https://fedoraproject.org/wiki/Changes/ReduceInitialSetupRedundancy
I'm going to send a heads-up to the Anaconda developers now (though I
don't plan to join their mailing list, so hopefully they have an active
list moderator). And then we will no doubt have a discussion when the
change is announced on devel@. Ideally I would have prepared this
earlier and had time to run it by the Anaconda developers *before*
submitting, but the change proposal deadline is tomorrow, so I'm going
to submit it now, even though I haven't had any feedback on it beyond
approval of the general idea from the Workstation WG. Sorry for the
very short notice and for delaying too long.
Everything is subject to change and nothing is set in stone.
Michael

As discussed in the meeting today, I have put together the draft Change
Page for the Fedora Visual Identity:
https://fedoraproject.org/wiki/Changes/VisualIdentity
The content is pretty much a placeholder, as nothing concrete has been
approved on this by the WG, but just filing the feature page today, before
the deadline.
cheers,
ryanlerch

Hi,
Jiri found this review (among many) of Fedora 25:
http://www.hecticgeek.com/2016/12/fedora-25-review/
It includes a couple recommendations:
* We should restore systemd-readahead to speed boot time by ~30% for
users without SSDs. Endless has a downstream patch for this. Or we
could use Ubuntu's readahead utility.
* We should switch from CFQ to deadline I/O scheduler (which Ubuntu
has been using for years) for subjective massive responsiveness
improvements when the system is under load
Of these, the later seems easier to change and more important. Anyone
know why we're still using CFQ? If the answer is "it's better for
servers" then perhaps we need a mechanism to adjust this on a per-
product basis.
Just wanted to put these issues back on the radar....
Michael

The actual PR is posted in: https://pagure.io/pungi-fedora/pull-request/257
This is only for: https://fedoraproject.org/wiki/Changes/WorkstationOstree
The primary reason to do this is that the blivet defaults break with ostree,
since `/home` needs to be `/var/home` with ostree.
https://bugzilla.redhat.com/show_bug.cgi?id=1382873
But bigger picture than that, having a split `/home` makes less sense using
rpm-ostree, because the primary original rationale for introducing that split
was to make upgrades easier by reinstalling but preserving `/home`. With
rpm-ostree upgrades should be much more reliable and easier.
We also to use XFS (as opposed to the blivet ext4 default) for the same reason as Atomic/Server -
it works better with overlay2 because it avoids inode limits.
And not using all of the disk makes it easier to do more advanced
partitioning *post* installation. For example, in the past I've used dm-crypt
for the OS and `/home`, but not for `/srv` where I put non-private data like my
git repositories. (Although I recently switched back to dm-crypt for everything
for simplicity).
Another good example of this is that `container-storage-setup` supports
allocating a separate LV for `/var/lib/docker`, so container storage is isolated
from the host.
Anaconda is making it easier to do arbitrary partitioning in the installer via
blivet-gui, but I think doing it post-install is more flexible. One can
use scripts as well (e.g. Ansible).
The flip side of course is that users are going to wonder why they only have
`14G` of space...we should likely teach the installer to have a simple "use all
of my disk" button, and also have one post-install (something like Nautilus
launching `Disks` with awareness of LVM)?
Signed-off-by: Colin Walters <walters(a)verbum.org>
---
fedora.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fedora.conf b/fedora.conf
index a7d403b..edc3586 100644
--- a/fedora.conf
+++ b/fedora.conf
@@ -812,7 +812,7 @@ ostree_installer = [
"x86_64": {
"repo": "Everything",
"release": None,
- "installpkgs": ["fedora-productimg-workstation"],
+ "installpkgs": ["fedora-productimg-atomic"],
"rootfs_size": "8",
"add_template": ["workstation-ostree-installer/lorax-configure-repo.tmpl",
"workstation-ostree-installer/lorax-embed-repo.tmpl"],
--
2.9.4