<div dir="ltr">On Tue, Aug 19, 2014 at 11:21 PM, Josh Boyer <span dir="ltr"><<a href="mailto:jwboyer@fedoraproject.org" target="_blank">jwboyer@fedoraproject.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="">On Tue, Aug 19, 2014 at 3:51 PM, Elad Alfassa <<a href="mailto:elad@fedoraproject.org">elad@fedoraproject.org</a>> wrote:</div>
</blockquote><div class=""> <snip><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="">
> As always in policies, mandatory items are marked with the words "must" and<br>
> "must not", the rest is nice-to-have.<br>
><br>
> App launchers in Fedora workstation *must*:<br>
<br>
</div>This doesn't really seem specific to Workstation. We should aim for<br>
distro-wide first, so other products have a similar look and feel. If<br>
they need to deviate, they can do so later.<br></blockquote><div><br></div><div>I do have other product specific things here.<br></div><div>This policy is written with two facts in mind:<br></div><div>1) Fedora's default desktop offering is Fedora Workstation.<br>
</div><div>2) Fedora Workstation uses GNOME by default. <br><br>As such, if the WG would decide to switch desktops, this policy will need to be re-evaluated.<br></div><div>Furthermore, this policy does not aim to apply to all applications in the distribution. It's meant to apply to anything we include by default in our default desktop product.<br>
</div><div>If other applications want to follow it it'd be great, because it will improve user experience, but I can't force them to.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=""><br>
> * Have a unique 64x64 launcher icon (the same icon MUST NOT be used for one<br>
> default launcher).<br>
<br>
</div>I don't understand the "default launcher" follow on, nor why it isn't<br>
it's own bullet.<br></blockquote><div><br></div><div>It's a typo.<br></div><div>The same icon must not be used for more than one application launcher that is installed by default.<br>We can't enforce non-default apps to have unique icons. This is there because it's clarifying on the word unique. <br>
</div><div class=""> <br><snip><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="">
> * Installable and removable independently from within GNOME Software,<br>
> unless part of the "core applications" set, in which case they must NOT be<br>
> removable.<br>
<br>
</div>This last bullet seems product specific. That might be an addendum<br>
per-product, since the "core applications" are going to likely vary.<br></blockquote><div><br></div><div>Same comment as I said before. If other products or spins want to base on this policy, they can copy it and make the changes they need.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=""><br>
> Default apps in Fedora Workstation *should*:<br>
> * Have appdata metadata (soon to be turned into a must).<br>
> * Have a good reason for being included in the default set, especially if<br>
> not considered part of the core desktop experience by the GNOME upstream.<br>
<br>
</div>Uh, I kind of object to this bullet. This is a Fedora policy/product,<br>
not a GNOME one. If Fedora sees a non-GNOME application as part of<br>
the core desktop experience, it shouldn't have to justify it based on<br>
what upstream GNOME thinks.<br></blockquote><div><br></div><div>If we install it by default and GNOME thinks it's core then having it removable would hurt our user experience. We can't have users removing Software itself, for example. <br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=""><br>
> * Start in under than 10 seconds (on modern hardware).<br>
<br>
</div>That seems difficult to enforce/police. What happens if an app meets<br>
everything else but then fails to do this? Do we then yank it out?<br>
Who's going to sit there with a stopwatch and time every app? I<br>
realize this is a should, but it seems unnecessary.<br></blockquote><div><br></div><div>It's a "should" item. It will make UX better. It's not something you can enforce, and therefor it's not in the must column.<br>
</div><div>It's included because it's something many people don't pay much attention to, and if an app takes a long time to start (that is, show any UI, in case of libreoffice or similar big apps, a splash screen is fine) we should consider removing it from the default set or at least prioritize fixing it.<br>
</div><div> </div></div>-- <br><div dir="ltr">-Elad Alfassa.</div>
</div></div>