Branding

[Kalev Lember]

On 11/18/2014 03:16 PM, Paul W. Frields wrote:
> OK, a lot of quick action on this, on the part of several people
> yesterday and this morning.  Here's what we discovered:
> 
> Package bug:  https://bugzilla.redhat.com/show_bug.cgi?id=1161637
> Upstream git: https://git.fedorahosted.org/cgit/background-logo-extension.git/
> 
> (1) The SRPM in the bug appears to be *newer* than git (includes
> e.g. prefs.js, control utility).  Maybe something wasn't pushed?
> However, the SRPM seems like it should work.

Excellent, thanks for looking into this! Florian was waiting on approved
design before doing a final upstream release and now that we have it, he
should be able to do the release.

> (2) We need to package a wordmark, since that works visually better
> than the Fedora infinity-bubble logomark.  Also, from the mockups, an
> < 100% opacity was desirable.  Ryan has sent that on to Spot to add to
> fedora-logos.

Great -- we'll need a new fedora-logos build for the installer branding
anyway.

> (3) The package needs a .gschema.override file to point to the new
> logo.  That seems like the right thing to do for a distro-specific
> change like this.  I wasn't able to find fmuellner on line yesterday
> or this morning, so given the freeze, Stephen Gallagher was planning
> to help us with packaging since he's a provenpackager.  I pasted this:
> http://fpaste.org/151778/16319651/

It's a fedora-specific package anyway, I think we should be able to
avoid the overrides and just default to the correct logo. Florian, what
do you say?

Another thing we'll need is to include an override somewhere to enable
the extension by default. fedora-release-workstation seems like an
appropriate place -- I'll send a patch to dgilmore a bit later today
that adds the override if nobody comes up with a better way of doing it.

> If anyone has concerns or suggestions, please add them ASAP... the
> freeze is on today, so we may end up needing a QA exception to get
> this stuff done.

Yes, we're already frozen now, definitely need a QA exception.

-- 
Kalev