<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
</head>
<body smarttemplateinserted="true" bgcolor="#FFFFFF" text="#000000">
<div id="smartTemplate4-quoteHeader"><br>
Just 2 comments inline:<br>
<blockquote type="cite" style="margin-bottom: -20px !important;
padding-bottom:20px !important;">
<div id="newHeaderAG" style="font-size: x-small; padding:1em;
background-color:rgba(220,220,240,0.4); border-radius:3px;"> <b>Subject:</b>
Re: Avocet branding - What do you think?<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:tb-planning@mozilla.org">tb-planning@mozilla.org</a> <br>
<b>From: </b>Martin Kotulla (Softmaker)<br>
<b>Sent: </b>Sunday, 29/03/2015 13:45:25 13:45 GMT ST +0100
[Week 13]<br>
</div>
</blockquote>
</div>
<blockquote class=" cite" id="mid_5517F3E5_4090304_softmaker_de"
cite="mid:5517F3E5.4090304@softmaker.de" type="cite">Frankly, I
don't like much the idea of using bird names:
<br>
<br>
1. Most people outside the English-speaking countries have no idea
what an avocet or bunting is. They will not even recognize the
terms as bird names.
<br>
<br>
2. How do you want to make people understand that a bunting is
better/newer than an avocet? You either need to have multiple
releases in succession for people to recognize that it is a
numbering/naming system. Or you need to explain this system to our
users, again and again.
<br>
</blockquote>
It is just a build name, I don't think this is better or worse. It
is like OS 10 Panther or whatever they are using or Android Icecream
Sandwich<br>
<blockquote class=" cite" id="mid_5517F3E5_4090304_softmaker_de"
cite="mid:5517F3E5.4090304@softmaker.de" type="cite">
<br>
4. You wrote that you would use customized artwork to announce a
release, but Thunderbird in general would use the conventional
branding.
<blockquote class=" cite" id="Cite_7990457" type="cite">From a
branding/marketing viewpoint, this is not good. Create artwork </blockquote>
and stay with it. The most hardcore branding advocates will even
dictate the background color the artwork is placed on.
<br>
<br>
Imagine we get some good online reviews for TB 38 with a black
avocet. These reviews stay up for years, and they will often show
the artwork. When people go to download TB, they will not see this
artwork anymore but only the "conventional" one, or even the next
bird artwork. They will be confused.
<br>
</blockquote>
Not sure if the artwork is going to replace but if this is a build
name I would definitely say we keep the Thunderbird as a part.<br>
<br>
e.g. Thunderbird Avocet, Thunderbird Bunting ... etc.<br>
<br>
Axel<br>
<br>
</body>
</html>