Hi, For the most part I was unaware of these issues - so please excuse me if these remarks are silly.
Randall Arnold wrote: > Problem: Official MeeGo font is commercial, closed source. > Solution: Use a similar rendition fo the typeface that is open (creative > commons) [2]. Replace current logo with this font asap What's the official MeeGo font? And why should we care what it is? What's important is that we have an SVG & PNG version of the logo which we are free to reuse (withing the bounds of acceptable guidelines). As I understand it (which may be wrong, of course) a free typeface only matters if we're creating text other than the MeeGo logo using the same typeface. > Problem: Official MeeGo logo spec demands excessive white space around > logo for all uses > Solution: Develop broad array of white space requirements based on use > context. Current space requirement [3] is too restrictive (and in fact > was violated by MeeGo Conference 2010 badge!) What would you suggest? It definitely seems reasonable to define a whitespace clearing area around a logo. GNOME defines a clearing space of 1/10 x around the logo, where x is the horizontal width of the GNOME foot, and also shows some acceptable examples of "hacked" logos: http://live.gnome.org/BrandGuidelines > Problem: MeeGo secondary color pallette [4] is too restrictive. > Solution: add a few more shades. I recommend a Light Magenta, a Dark > Cyan, Dark Green, Orange and one or two Brown shades (note: at least one > brown shade is used on some MeeGo characters... that should be made > official) I don't think that it's necessarily true that only MeeGo palette colours can be used for elements outside the MeeGo logo - perhaps it'd be useful to define a 16 or 32 colour palette for general use, and a smaller palette for use specifically in the wordmark (and I'd definitely like to see a graphic designer propose one). > Problem: no clear usage policy on MeeGo characters and derivatives > Solution: craft one! I have been creating derivatives for some time [5] > and we have just now run into issues about use. I would like clear > guidelines on what shall, should and/or may be done with originals and > derivatives. If it was up to me, I'd say "Anything goes" (within reason for things like obscenity). I don't see any trademarking of ameegos happening and the brand value is more for community identity than it is for the project. I don't see any need to regulate this. Like you, I'd be interested in Ibrahim's comments. Cheers, Dave. -- maemo.org docsmaster Email: [email protected] Jabber: [email protected] _______________________________________________ MeeGo-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community
