[Battlemesh] Battlemesh v9 logo rules, definitions, consensus

Nemesis nemesis at ninux.org
Fri Dec 11 15:48:21 UTC 2015


On 12/08/2015 06:06 PM, cmsv wrote:
> On 12/07/2015 10:40 AM, Nemesis wrote:
>> > On 12/05/2015 05:48 AM, fboehm wrote:
>>> >> Am 04.12.15 um 17:38 schrieb Nemesis:
>>>> >>> Having a design background and having designed websites and logos as a
>>>> >>> professional freelancer for 7 years I keep suggesting to you all to stop
>>>> >>> wasting valuable resources, energy and emails on this issue every year.
>>>> >>>
>>>> >>> The logo is the most important way through which people recognize an
>>>> >>> idea, conference, brand, community or product, changing it every year is
>>>> >>> a very bad decision from a communication point of view.
>>>> >>>
>>>> >>> So I won't waste time saying what we should not do because that is not
>>>> >>> the way logos are designed. Logos are designed to endure several years
>>>> >>> and the process involves studying IN PRIMIS what kind of message you
>>>> >>> want to send out, not what you don't want to send out.
>>>> >>>
>>>> >>> My 2 cents
>>>> >>>
>>>> >>> Nemesis
>>>> >>>
>>>> >>>
>>>> >>> On 12/04/2015 09:08 AM, cmsv wrote:
>>>>> >>>> Hello guys,
>>>>> >>>>
>>>>> >>>> It seems that this years logo and possibly poster suggestions may
>>>>> >>>> not be
>>>>> >>>> as usual as in previous years. Some people have some ideas that may or
>>>>> >>>> may not be in the best interest of the majority and or the event itself
>>>>> >>>>
>>>>> >>>> So in order to get to a consensus and maybe a standard for future
>>>>> >>>> designs, we could all give a few cents to this thread with what should
>>>>> >>>> not be part of a logo or moderated.
>>>>> >>>>
>>>>> >>>> A few things that have been said:
>>>>> >>>>
>>>>> >>>> * Avoid state symbols (in an affirmative way)
>>>>> >>>> * No military and war related references & symbols
>>>>> >>>> * Avoid colonialism symbols
>>>>> >>>> * Stereotypical and cultural references that can be depreciative
>>>>> >>>>
>>>>> >>>> Perhaps and before continuing with logo designs we could decide what
>>>>> >>>> else to avoid in there.
>>>>> >>>>
>>>> >>>
>>> >> Nemesis, I couldn't agree more.
>>> >>
>>> >> Don't get me wrong, I like the individual logos and also helped in the
>>> >> past with a logo. But also from a ressource mgmt standpoint we run off
>>> >> the track with this task. Why not derive one simple logo from the
>>> >> older logos that can be used in the upcoming years.
>>> >>
>>> >> I should be fine (if not helpful) to add a small flag and a date next
>>> >> to it to state where and when the event happens.
>> > 
>> > Sorry for the previous top-posting.
>> > 
>> > The logo of the v8 edition is good and general enough to be reused,
>> > maybe we can just ask the designer the favour to donate us the design so
>> > we can adapt the colors.
>> > 
>> > It's a good compromise for the short term, a not time-consuming solution.
>> > If this will be (finally) accepted, then at a later step we can talk
>> > about a long-term solution to this problem.
>> > 
>> > Looking forward to hear feedback or alternative proposals.
>> > 
>> > Nemesis
> I do agree.
> Guys, your feedback has very good valid points.
> Logo should be simple and I see no reason to not adapt the previous one
> and make it the default logo for the battlemesh.
>
> For local events, the local team can always have the poster with
> something related or inherent to the event local/place and perhaps here
> one can have their local place/country symbols , etc.
>
> I guess now, we only need to hear from the top brass if they agree
> having that logo or prefer another one to be the battlemesh symbol.
>
> After 9 editions might be time to have a default logo ;)

No feedback so far.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20151211/c75ce381/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20151211/c75ce381/attachment.pgp>


More information about the Battlemesh mailing list