diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-artwork/2011-January/000058.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-artwork/2011-January/000058.html')
| -rw-r--r-- | zarb-ml/mageia-artwork/2011-January/000058.html | 191 |
1 files changed, 191 insertions, 0 deletions
diff --git a/zarb-ml/mageia-artwork/2011-January/000058.html b/zarb-ml/mageia-artwork/2011-January/000058.html new file mode 100644 index 000000000..707c1d3e7 --- /dev/null +++ b/zarb-ml/mageia-artwork/2011-January/000058.html @@ -0,0 +1,191 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-artwork] [RFC] Proposed logo guidelines + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-artwork%40mageia.org?Subject=Re%3A%20%5BMageia-artwork%5D%20%5BRFC%5D%20Proposed%20logo%20guidelines&In-Reply-To=%3CAANLkTinNLrv-wAzrkp%3D%2Br6RZW5dU%3DuChU%3DS9S56QH75f%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="000053.html"> + <LINK REL="Next" HREF="000050.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-artwork] [RFC] Proposed logo guidelines</H1> + <B>Romain d'Alverny</B> + <A HREF="mailto:mageia-artwork%40mageia.org?Subject=Re%3A%20%5BMageia-artwork%5D%20%5BRFC%5D%20Proposed%20logo%20guidelines&In-Reply-To=%3CAANLkTinNLrv-wAzrkp%3D%2Br6RZW5dU%3DuChU%3DS9S56QH75f%40mail.gmail.com%3E" + TITLE="[Mageia-artwork] [RFC] Proposed logo guidelines">rdalverny at gmail.com + </A><BR> + <I>Wed Jan 19 10:49:10 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000053.html">[Mageia-artwork] [RFC] Proposed logo guidelines +</A></li> + <LI>Next message: <A HREF="000050.html">[Mageia-artwork] [RFC] Proposed logo guidelines +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#58">[ date ]</a> + <a href="thread.html#58">[ thread ]</a> + <a href="subject.html#58">[ subject ]</a> + <a href="author.html#58">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi, + +On Wed, Jan 19, 2011 at 01:28, Olivier FAURAX <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-artwork">olivier at faurax.fr</A>> wrote: +><i> Le 18/01/2011 00:31, Romain d'Alverny a écrit : +</I>>><i> On Tue, Jan 18, 2011 at 00:02, Caroline Garlatti <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-artwork">cgarlatti at gmail.com</A>> wrote: +</I>>>><i> Le dimanche 9 janvier 2011 17:52:28, Romain d'Alverny a écrit : +</I>>>><i> Indeed, I was working on it. You can see my first draft here: +</I>>>><i> <A HREF="http://www.kalypo.com/share/">http://www.kalypo.com/share/</A> +</I>>>><i> +</I>>>><i> We have tried to: +</I>>>><i> - rebalance the logo: increase the size of the text and reduce the cauldron +</I>>><i> +</I>>><i> Actually, the size of the text made smaller relative to the cauldron +</I>>><i> (see <A HREF="http://blog.mageia.org/wp-content/uploads/2010/12/mageia_logo.jpg">http://blog.mageia.org/wp-content/uploads/2010/12/mageia_logo.jpg</A> +</I>>><i> ) :-p +</I>><i> +</I>><i> Yes, the cauldron is bigger, but also wider. +</I> +Well, that's the other way around. :-) The text has been made smaller, +to have the "m" aligned within the inner border of the cauldron +(that's an important setting in this realignement), and the same "m" +has been used to set the space around the icon (crucial setting too). + +><i> The cauldron border size was took from the size of the letter (bottom +</I>><i> border of the "e"), the new version breaks the link between the cauldron +</I>><i> and letter size. +</I> +Yes, but it will anyway if we change the font (and that may be an +option). I understand that the initial link makes sense, and that's a +good way to build the icon, but that too can be an intermediary step +and the icon may live on its own later on (that is, the icon strutural +definition may stand alone, separate from the initial "e"). + +><i> To me, this suggests that the name an "annex" of the logo, like if ti +</I>><i> was of less importance. +</I> +Not of less importance, but balanced/contrasted; it makes both more +remarkable: the icon is not a letter, but a distinctive sign, that may +be on the left, or above the text. + +May be it can be rebalanced again, but you can't have a name that +outweights the icon. Plus, negative space (around the full logo, +around/between each of its components) is crucial. + +>>><i> - introduce a color . This proposal offers the possibility to have one logo but +</I>>>><i> different color for each group (cf- Romain's mail_brand/logo management, +</I>>>><i> official/derivative) +</I>><i> +</I>><i> We need to know where we are going with colors. +</I>><i> Do we have some input from marcom ? +</I> +Not at this point. We'll add this point to discuss in the marcom +meeting on Thursday. However we must go fast; or (it's likely to be +this way given the time constraint) we will have a collector edition +of tee-shirts for FOSDEM (understand it as, with a logo that is not +the final official one). That may sound problematic at first, but it's +not; time goes on and we already did that (have Mageia tee shirts with +a temporary identity) for OWF back in October; and the +finalized/updated logo will replace all instances. + +><i> I made some tests during the logo elaboration : +</I>><i> <A HREF="http://www.flickr.com/photos/ofaurax/5118935357/in/set-72157625195368021/">http://www.flickr.com/photos/ofaurax/5118935357/in/set-72157625195368021/</A> +</I>><i> <A HREF="http://www.flickr.com/photos/ofaurax/5119536536/in/set-72157625195368021/">http://www.flickr.com/photos/ofaurax/5119536536/in/set-72157625195368021/</A> +</I>><i> <A HREF="http://www.flickr.com/photos/ofaurax/5159964096/in/set-72157625195368021/">http://www.flickr.com/photos/ofaurax/5159964096/in/set-72157625195368021/</A> +</I>><i> +</I>><i> The blue and orange are ok, but seems childish to me (I imagine them on +</I>><i> a toy). +</I>><i> It's ok if we don't want to suggest something "rock-solid" or corporate. +</I> +Define "corporate", "childish"; it's like "pro" or "commercial" it's a +word that's become difficult to define, especially since most of its +usage is in a negative, contradictory or depreciative context. + +So I would rather prefer we stay out of subjective interpretations +first and build from a similar set of rules as for the logo: initial +intentions, some strict requirements, open tracks, and see what comes +from this. That is, we build and define the story behind the logo, +rather than only leave it open to interpretations from here and there. + +As an exemple of requirement: do not use or rely on Mandriva colour +scheme (blue/orange/yellow); or of any other major Linux distribution. +It does not prevent to use the same colours, but it requires to do so +in a really distinctive manner/rearrangement. + +><i> Note that the bubble in orange seems more natural, as we expect lighter +</I>><i> colors for bubbles. +</I>><i> +</I>><i> For the letters, perhaps we might color "m", "g" and "a" of "mageia", as +</I>><i> this is its package suffix. +</I> +I'm not sure we should go further than marking more than one letter +(or even a single one, actually). It makes the full logo confusing. It +may still be relevant for bubbles/i-dot. + +>><i> With the time, I don't know if the color-coding will be enough to +</I>>><i> differentiate official/derivative uses. +</I>><i> +</I>><i> I think that color is not enough to differentiate. +</I>><i> We'll discussed that in another thread. +</I> +Yes. + +><i> - changed the font : this one is less wide (the "e" is no more rounded) +</I> +That was voluntary, because we wanted to use the same font for +headlines ; in some context, it's easier not to have to change the +font default properties. Or, it requires to have a precise track of +what has been altered so it can be reproduced. + +><i> - filled the bubbles +</I>><i> +</I>><i> The new border size of the cauldron with the filling of the bubbles +</I>><i> makes the icon heavier, especially the bubbles (I don't imagine tham +</I>><i> popping anymore). +</I> +The gradient may contribute to the popping/lightness effect, no? + +><i> I think that we need to fill them, or at least put a color in them, but +</I>><i> we might not lose the lightness of them (as this represents the boiling +</I>><i> of ideas). +</I> +On the other hand, filling them makes the whole icon less complex +(that's especially relevant for small size icons). + +>><i> Anyway, we have two interesting refinement directions I guess: +</I>>><i>  - caroline, with the gradient, filled-in bubbles, and color uses, +</I>>><i>  - alexn83, with the font change (alexn83, I don't remeber, do you +</I>>><i> have the font reference, or is it reworked?) and the match of the i +</I>>><i> point with the bubbles +</I>><i> +</I>><i> I'll try to put my remarks in another refinement as a showcase, if I +</I>><i> find some time. +</I> +Ok. + +Romain +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000053.html">[Mageia-artwork] [RFC] Proposed logo guidelines +</A></li> + <LI>Next message: <A HREF="000050.html">[Mageia-artwork] [RFC] Proposed logo guidelines +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#58">[ date ]</a> + <a href="thread.html#58">[ thread ]</a> + <a href="subject.html#58">[ subject ]</a> + <a href="author.html#58">[ 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> |