summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-artwork/2011-January/000059.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-artwork/2011-January/000059.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-artwork/2011-January/000059.html')
-rw-r--r--zarb-ml/mageia-artwork/2011-January/000059.html169
1 files changed, 169 insertions, 0 deletions
diff --git a/zarb-ml/mageia-artwork/2011-January/000059.html b/zarb-ml/mageia-artwork/2011-January/000059.html
new file mode 100644
index 000000000..404d2b91c
--- /dev/null
+++ b/zarb-ml/mageia-artwork/2011-January/000059.html
@@ -0,0 +1,169 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-artwork] brand/logo management, official/derivative
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-artwork%40mageia.org?Subject=Re%3A%20%5BMageia-artwork%5D%20brand/logo%20management%2C%20official/derivative&In-Reply-To=%3CAANLkTim9NGt%3DxH_Tu0A5P7vHw%2B1NBSirrFu0m8XQ8-gm%40mail.gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000054.html">
+ <LINK REL="Next" HREF="000051.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-artwork] brand/logo management, official/derivative</H1>
+ <B>Romain d'Alverny</B>
+ <A HREF="mailto:mageia-artwork%40mageia.org?Subject=Re%3A%20%5BMageia-artwork%5D%20brand/logo%20management%2C%20official/derivative&In-Reply-To=%3CAANLkTim9NGt%3DxH_Tu0A5P7vHw%2B1NBSirrFu0m8XQ8-gm%40mail.gmail.com%3E"
+ TITLE="[Mageia-artwork] brand/logo management, official/derivative">rdalverny at gmail.com
+ </A><BR>
+ <I>Wed Jan 19 11:10:33 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000054.html">[Mageia-artwork] brand/logo management, official/derivative
+</A></li>
+ <LI>Next message: <A HREF="000051.html">[Mageia-artwork] 2011/week 3 meeting
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#59">[ date ]</a>
+ <a href="thread.html#59">[ thread ]</a>
+ <a href="subject.html#59">[ subject ]</a>
+ <a href="author.html#59">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Woooo \o/
+
+On Wed, Jan 19, 2011 at 02:38, Olivier FAURAX &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-artwork">olivier at faurax.fr</A>&gt; wrote:
+&gt;<i> Le 17/01/2011 22:24, Romain d'Alverny a &#233;crit :
+</I>&gt;<i> As an example, look at the difference between the former
+</I>&gt;<i> ubuntu/canonical logos.
+</I>&gt;<i> <A HREF="http://www.ivankristianto.com/wp-content/uploads/2009/04/ubuntu-logo217.gif">http://www.ivankristianto.com/wp-content/uploads/2009/04/ubuntu-logo217.gif</A>
+</I>&gt;<i> <A HREF="http://www.webactus.net/wp-content/uploads/2010/01/687px-Canonical_logo.png">http://www.webactus.net/wp-content/uploads/2010/01/687px-Canonical_logo.png</A>
+</I>&gt;<i>
+</I>&gt;<i> The whole thing has been redesigned since, and it's worth reading :
+</I>&gt;<i> <A HREF="http://design.canonical.com/the-toolkit/ubuntu-brand-guidelines/">http://design.canonical.com/the-toolkit/ubuntu-brand-guidelines/</A>
+</I>
+Yes.
+
+&gt;<i> For example, they defines colors (orange, grey, white and
+</I>&gt;<i> aubergine/purple), and they use it differently for ubuntu (orange on
+</I>&gt;<i> white, highlight in purple) and canonical (aubergine on grey, highlight
+</I>&gt;<i> in orange).
+</I>&gt;<i>
+</I>&gt;<i> I definitely need someone who can choose colors like that.
+</I>
+Yep. That's a mix for marcom, artwork and council.
+
+&gt;&gt;<i> We already have the official Mageia logo (waiting for
+</I>&gt;&gt;<i> refinements/discussions yet, another separate mail), designed by
+</I>&gt;&gt;<i> Olivier. We would like, if possible, to have the Mageia
+</I>&gt;&gt;<i> derivative/community logo based on the official, so there is an
+</I>&gt;&gt;<i> obvious connection, yet difference between the two.
+</I>&gt;<i>
+</I>&gt;<i> An idea to be refined :
+</I>&gt;<i> - color the cauldron body with a color representing the desktop (or
+</I>&gt;<i> purpose) : blue for KDE, red for GNOME, and so on, the border being
+</I>&gt;<i> untouchable black
+</I>
+As for that, I would leave out the colour coding and use
+KDE/GNOME/YOUR-CHERISHED-DE labels instead and separate from the
+Mageia logo (that is, next to it, or below it). More to the point.
+
+&gt;<i> - let the top 3 bubbles color and the &quot;eia&quot; letters color chosen by the
+</I>&gt;<i> group, &quot;mag&quot; being untouchable black
+</I>&gt;<i>
+</I>&gt;<i> So the logo will have a untouchable part, and a &quot;use your colors&quot; part.
+</I>&gt;<i> I think that every group can choose a set of 3 colors to represent
+</I>&gt;<i> themselves (it's not a flag or something like that).
+</I>
+Let's call this our first design option.
+
+&gt;<i> Something to discuss : would we be open to replace one of the last
+</I>&gt;<i> letter ? For example, the Paris User Group replacing the i of mageia
+</I>&gt;<i> with an effeil tower ? (I would be ok, as it's in the 3 final letters).
+</I>
+Hmmm, not in favour of that at this point.
+
+&gt;&gt;<i> So to allow/ease derivative/community uses, we need to setup a
+</I>&gt;&gt;<i> dedicated logo (still with important guidelines/purposes to follow).
+</I>&gt;&gt;<i> There are several use cases that should be facilitated with that:
+</I>&gt;&gt;<i> &#160;- derivative/customized distribution release,
+</I>&gt;&gt;<i> &#160;- local communities events,
+</I>&gt;&gt;<i> &#160;- communities web sites.
+</I>&gt;<i>
+</I>&gt;<i> Note that this can be combinated e.g. you need a logo for the KDE liveCD
+</I>&gt;<i> from the Italian group.
+</I>
+Yep.
+
+&gt;&gt;<i> In short, that would make:
+</I>&gt;&gt;<i> &#160;- official Mageia.Org brand/logo (the one chosen a few days ago) =&gt;
+</I>&gt;&gt;<i> strict guidelines, for Mageia.Org official releases only (and quotes)
+</I>&gt;&gt;<i> &#160;- Mageia community derivated identity (for local
+</I>&gt;&gt;<i> communities/projects/initiatives that are tied to Mageia but not
+</I>&gt;&gt;<i> necessarily officially managed) =&gt; strict guidelines too, but for
+</I>&gt;&gt;<i> community/derivative uses
+</I>&gt;&gt;<i> &#160;- case by case management for further logos, with required approval
+</I>&gt;&gt;<i> from the artwork team and validation from council or board.
+</I>&gt;&gt;<i> &#160;- exclusive source distribution from Mageia.org website (or dedicated
+</I>&gt;&gt;<i> Mageia.org artwork website).
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> What's your take on this?
+</I>&gt;<i>
+</I>&gt;<i> It's ok for me.
+</I>&gt;<i> You might also start a list of communities to see if our process can
+</I>&gt;<i> provide a logo for each of them. It would be better to do it for them
+</I>&gt;<i> rather than waiting for them to design their own logo, by the way.
+</I>
+Yes, so we can validate it as well. That's why I would prefer us to:
+ - start small, with the official and the generic solution for
+derivatives; publish those with guidelines and submission/validation
+process;
+ - start pushing specific derivatives for specific use cases:
+ - customized distribution provided/sold by a for-profit company to
+its customers;
+ - local website/initiative;
+ - local event.
+
+&gt;<i> Oh, and finally, I've got it :
+</I>&gt;<i> <A HREF="http://www.flickr.com/photos/ofaurax/5368859836/">http://www.flickr.com/photos/ofaurax/5368859836/</A>
+</I>&gt;<i> (I did it quickly with random colors, I hope you'll get the idea)
+</I>
+Ok, great. Wooo... all this would be way more easy in a big room with
+a big drawing board, wouldn't it? :-)
+
+Well, further than not being really confident in this option (I'm more
+enclined to have the Mageia official and derivative identity to stay
+as a signature, and have it not spread too much in a lot of directions
+- but that's my take only) I would like too to see if we can have
+other design solutions.
+
+Cheers!
+
+Romain
+</PRE>
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000054.html">[Mageia-artwork] brand/logo management, official/derivative
+</A></li>
+ <LI>Next message: <A HREF="000051.html">[Mageia-artwork] 2011/week 3 meeting
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#59">[ date ]</a>
+ <a href="thread.html#59">[ thread ]</a>
+ <a href="subject.html#59">[ subject ]</a>
+ <a href="author.html#59">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-artwork">More information about the Mageia-artwork
+mailing list</a><br>
+</body></html>