Hagar and I presented the problem to both, the deb and the marketing mailing lists and got no answer. Maybe we can call the "lazy consensus" herefloris v wrote:These comments by Jan are, by the way, what I wanted to write all along when I went on about the Marketing department, but it came out all wrong. And while we as content providers may not care much about pixel perfection of logos, other people do
Anyway, there are two things to consider:
1- There is no warranty that the "official logo" for the project we have today will survive the AOO 4.0 transition. As a matter of facts there are discussions to change it again on a future so arguments like fonts and colours are not determinant, IMO.
2- The "product" we offer here is different from the product offered by the project as a whole: we provide support for the program, not the program. On this situation a logo that is different but still recognisable is a "good thing", IMO.