1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
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 <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-artwork">olivier at faurax.fr</A>> wrote:
><i> Le 17/01/2011 22:24, Romain d'Alverny a écrit :
</I>><i> As an example, look at the difference between the former
</I>><i> ubuntu/canonical logos.
</I>><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>><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>><i>
</I>><i> The whole thing has been redesigned since, and it's worth reading :
</I>><i> <A HREF="http://design.canonical.com/the-toolkit/ubuntu-brand-guidelines/">http://design.canonical.com/the-toolkit/ubuntu-brand-guidelines/</A>
</I>
Yes.
><i> For example, they defines colors (orange, grey, white and
</I>><i> aubergine/purple), and they use it differently for ubuntu (orange on
</I>><i> white, highlight in purple) and canonical (aubergine on grey, highlight
</I>><i> in orange).
</I>><i>
</I>><i> I definitely need someone who can choose colors like that.
</I>
Yep. That's a mix for marcom, artwork and council.
>><i> We already have the official Mageia logo (waiting for
</I>>><i> refinements/discussions yet, another separate mail), designed by
</I>>><i> Olivier. We would like, if possible, to have the Mageia
</I>>><i> derivative/community logo based on the official, so there is an
</I>>><i> obvious connection, yet difference between the two.
</I>><i>
</I>><i> An idea to be refined :
</I>><i> - color the cauldron body with a color representing the desktop (or
</I>><i> purpose) : blue for KDE, red for GNOME, and so on, the border being
</I>><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.
><i> - let the top 3 bubbles color and the "eia" letters color chosen by the
</I>><i> group, "mag" being untouchable black
</I>><i>
</I>><i> So the logo will have a untouchable part, and a "use your colors" part.
</I>><i> I think that every group can choose a set of 3 colors to represent
</I>><i> themselves (it's not a flag or something like that).
</I>
Let's call this our first design option.
><i> Something to discuss : would we be open to replace one of the last
</I>><i> letter ? For example, the Paris User Group replacing the i of mageia
</I>><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.
>><i> So to allow/ease derivative/community uses, we need to setup a
</I>>><i> dedicated logo (still with important guidelines/purposes to follow).
</I>>><i> There are several use cases that should be facilitated with that:
</I>>><i>  - derivative/customized distribution release,
</I>>><i>  - local communities events,
</I>>><i>  - communities web sites.
</I>><i>
</I>><i> Note that this can be combinated e.g. you need a logo for the KDE liveCD
</I>><i> from the Italian group.
</I>
Yep.
>><i> In short, that would make:
</I>>><i>  - official Mageia.Org brand/logo (the one chosen a few days ago) =>
</I>>><i> strict guidelines, for Mageia.Org official releases only (and quotes)
</I>>><i>  - Mageia community derivated identity (for local
</I>>><i> communities/projects/initiatives that are tied to Mageia but not
</I>>><i> necessarily officially managed) => strict guidelines too, but for
</I>>><i> community/derivative uses
</I>>><i>  - case by case management for further logos, with required approval
</I>>><i> from the artwork team and validation from council or board.
</I>>><i>  - exclusive source distribution from Mageia.org website (or dedicated
</I>>><i> Mageia.org artwork website).
</I>>><i>
</I>>><i> What's your take on this?
</I>><i>
</I>><i> It's ok for me.
</I>><i> You might also start a list of communities to see if our process can
</I>><i> provide a logo for each of them. It would be better to do it for them
</I>><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.
><i> Oh, and finally, I've got it :
</I>><i> <A HREF="http://www.flickr.com/photos/ofaurax/5368859836/">http://www.flickr.com/photos/ofaurax/5368859836/</A>
</I>><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>
|
