<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 28, 2015 at 10:07 PM, Michael Catanzaro <span dir="ltr"><<a href="mailto:mcatanzaro@gnome.org" target="_blank">mcatanzaro@gnome.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">From the latest revision of our PRD [1]:<br>
<br>
"Fedora Workstation follows the GNOME Human Interface Guidelines. These<br>
guidelines are mandatory for applications installed by default."<br>
<br>
Currently we have applications that clearly do not follow these<br>
guidelines. Unless we plan to revisit this section of the PRD, we<br>
should remove them, or set a deadline for them to be improved.<br>
<br>
* Devassistant. Needs an app menu, plus a serious sit-down with the<br>
GNOME designers. We want to make it easy to develop apps for Fedora,<br>
but not at the cost of leaving a bad quality impression.<br></blockquote><div><br></div><div>I really don't see devasistant as helpful, it's harder to figure out what it is and how to use it than starting a new project manually. I agree it should either be re-designed or removed.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
* Evolution: Needs a major redesign that is not going to happen. Geary<br>
is not yet a suitable replacement. Options: (1) Not install any email<br>
client, because most users will use webmail; we can feature Evolution<br>
in GNOME Software. (2) If we want to keep Evolution installed by<br>
default, it's time to require the maintainers to add an app menu.<br></blockquote><div><br></div><div>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". <br></div><div>As long as an app included by default satisfies the HIG's application definition, it's okay. Sure, Evolution is not the best when it comes to UX, and "not shipping an email client" feels really weird for me, as every major competitor does ship with an email client. It's a basic feature.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
* Firefox. I see two options here: (1) replace it with Epiphany (FWIW,<br>
I think Epiphany has matured enough recently for this to be reasonable,<br>
but I am biased ;) (2) enable the GNOME extensions, mandate that they<br>
be updated in tandem with updates to Firefox in Fedora, and patch in an<br>
application menu. The extensions are good, and Mozilla is a reasonable<br>
upstream we can work with to get permission for this. The status quo<br>
should not be an option.<br></blockquote><div><br>I, personally, don't think Epiphany is mature enough to replace Firefox by default.<br><br>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.<br><br></div><div>My previous comment about the HIG applies here too.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
* setroubleshoot. This app is completely hopeless. SELinux issues are<br>
sufficiently rare nowadays that we simply do not need this anymore,<br>
although it would be ideal for ABRT to detect the issues and handle bug<br>
reports.<br></blockquote><div><br></div><div>It might be out of scope for ABRT, since it's about reporting problems, and setroubleshoot sometimes suggests troubleshooting options... and it's too bad that setroubleshoot can't automatically fix things (like bad contexts on files or booleans you need to enable) instead of requiring you to dive into the terminal.<br><br></div><div>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. <br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
* Shotwell. Eventually we can replace it with GNOME Photos, but in the<br>
meantime, users can just install a photo management app if they want<br>
one. Also, I suspect Shotwell sends your password to Facebook without<br>
verifying its TLS certificate....<br></blockquote><div><br></div><div>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?<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
* Transmission. Its only significant legal use is to download our<br>
competitor's products (Linux ISOs), hardly something we need to<br>
encourage. It's featured in GNOME Software already.<br>
<br></blockquote><div><br></div><div>"Legal" is different from country to country.<br></div><div>Before we consider removing transmission, I think it's wise to figure out why is it installed by default in the first place - there might have been some useful rationale behind it.<br></div><div> </div></div>-- <br><div class="gmail_signature">-Elad.</div>
</div></div>