Let's reconsider some more applications installed by default

[Michael Catanzaro]

On Fri, 2015-08-28 at 22:38 +0300, Elad Alfassa wrote:
> I don't see how "adding an app menu" would make Evolution any better.
> Following the HIG doesn't mean "implementing every pattern that
> exists in the HIG". 

Of course apps shouldn't need to implement every single pattern, but
they should implement at least the basics. An application menu is the
bare minimums for your app to feel well-integrated in Fedora
Workstation. The desktop environment provides the menu, and a little
arrow indicating that there are menu items, and the only menu item is
Quit? We should not consider that to be acceptable for default apps,
anymore.

> Regarding "installing extensions", I assume you mean stuff like 
> HTitle and the GNOME Theme... well, I'm not sure HTitle will continue 
> to be supported once firefox moves to its new addon API... as we 
> discussed in the past in this mailing list, we don't want to be
> installing any addons by default unless we can grantee they'll be
> supported for as long as our release is supported -  if Firefox
> updates and breaks one of them, reverting the user to "normal"
> Firefox would be a bad experience.
> 
> My previous comment about the HIG applies here too.

We would also need to never update Firefox until after the theme has
first been updated. Regarding HTitle: we can do it as a patch instead
of an extension (you're right; HTitle probably won't be possible as a
WebExtension). Or just not implement that at all. The theme and app
menu are the most important parts.

If we don't want to theme Firefox properly... Epiphany works great for
me. :)

> The problem is I don't think it's wise to enable SELinux by default
> without having any UI to let the user know when a violation happens.
> And we do want to keep SELinux enabled. 

I do want to keep SELinux enabled. I don't think users need to know
when a violation happens. That's just a bug, and I don't see any reason
to treat SELinux bugs as more special or more horrible than other bugs.

But frankly, I don't remember the last time I've had an SELinux
violation. totem-video-thumbnailer gets blocked from accessing the
Internet whenever I view my web cache in nautilus, but that's a real
bug in totem. And an example of one that users don't need to know
about.

> I think we can replace it with GNOME Photos today. Is there any
> reason not to? Regardless If it sends your password without verifying
> certificates then it's a bug that needs to be solved, not a reason to
> drop it completely. Have you filed the bug?

Debarshi doesn't want to include Photos until it matures further.

Regarding the TLS issue: consider that it currently depends on obsolete
WebKit, which means it has no security updates. That's an even more ser
ious issue. And modern WebKit handles this automatically, so it will be
fixed once they upgrade. See 
https://bugzilla.gnome.org/show_bug.cgi?id=751709