Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Upstream application icons and branding should be respected #21
From @chergert on September 29, 2017 10:31
Steps to reproduce (if you know)
Install Builder from apt or via Flatpak.
Application developers icons and branding are respected.
I understand Pop!_OS might have a desire for a unified style on the OS that is shipped. But consider third-party application authors and how their brand is equally important to them.
Imagine shipping an app in the Android store and it having different branding on Sony phones.
You might consider breaking up the icon theme into tiers with a core set of icons for applications shipped as part of the OS and an additional package users can install to "override all my applications to look like my OS instead of as the authors intended".
Copied from original issue: pop-os/iso#103
referenced this issue
Oct 31, 2017
FWIW, a consistent specific look and feel for Pop!_OS can be achieved without a total-coverage icon theme.
A solution would be to strip all icons that impact third-party applications from the theme leaving what constitutes a "core" icon set behind–this would leave something like all folders and system icons in place.
An "extension" of the icon theme could then be provided that users can optionally install which would include all these third-party icons. This extension would be a user-level modification and not constitute an infringement of third-party brands at the vendor-level.
I have a PR, #33, that addresses the GNOME Builder icon by blacklisting it from the installed by default package. We will need to create either a whitelist of application icons we want to include, or update this blacklist of applications we do not want to include.
@jackpot51 Thanks, I can easily do that. My point was about the overall consistency of the OS. People shouldn’t have to install a separate package to get consistency. (You’ve done an amazing job of crafting a consistent OS out of so many moving parts; it’s just sad to see such a simple thing break that consistency.)
@aral As the upstream author of Builder, I don't want my applications branding overridden by default. I want all of the Builder materials and web properties to match so people know things are correct as they move between applications and external product materials.
It's very much fine for users to change things if they wish, because they are aware of the difference.