~Nathan R. Hale
Rom. 12:2
>
> Hi Nathan, Magnus,
>
> My personal point of view on how MuseScore is being developed is in the same
> way as many Open Source projects, meaning by scratching your own itch. I
> didn't see this differently with the rebranding project which means that I
> didn't have a grand plan right from the start.
>
> I started the rebranding project because I felt that MuseScore didn't make a
> good first impression. That first impression is entirely based on how
> MuseScore is presented up to the step where you put your first note. The
> steps in between are downloading it from musescore.org, installing it on
> your computer and seeing the splash screen for the first time. During each
> step, one is confronted with the MuseScore brand, either the logo, wordmark
> or any form of artwork. So, I decided to do something about it.
>
> Since I'm not a designer, I first made
>
http://n2.nabble.com/Designer-request-MuseScore-banners-buttons-td1092415.html#a1115025> a post on the mailing list to see whether there was anybody in the
> community who could help us with this matter. After some mailing with
> Cambiata, I decided it was better to start from scratch. In order to improve
> my chances, I went to the design school not far from where I live. The rest
> of the story is openly communicated on musescore.org.
>
>
http://www.musescore.org/node/981>
http://www.musescore.org/node/1301>
http://www.musescore.org/node/1692>
> When rereading my own writings, I understand that I have not been clear
> about the selection procedure in my first post. In my second post, I thought
> it would be a good idea to ask for comments which could help the students
> for their second iteration. Still I didn't post anything about the selection
> procedure. I confess I didn't know yet how the selection procedure would
> happen. While talking with the teachers before the second iteration was
> ended, it became clear to me that selecting the strongest wordmark should be
> up to the designers themselves. My reason to take this decision was
> something I learned by following the
http://drupal.org Drupal
>
http://www.markboultondesign.com/news/detail/initial_wordmark_designs/> redesign project , lead by
http://www.markboultondesign.com/ Mark Boulton .
>
> Mark writes in
>
http://www.markboultondesign.com/news/detail/whats_in_a_wordmark/ What's in
> a wordmark :
>
> Mark Boulton wrote:
>>
>> For the Drupal wordmark, luckily, I’m not starting from scratch. There is
>> already a rich history of the logo, and the drupalicon (just read this
>> post for an insight into how the Drupalicon is changed, and how much of
>> that change is part of the Drupal community). However, with history, comes
>> culture and, sometimes, baggage. It’s my job to put all that to one side
>> and solve the problem in front of me. Luckily, a wordmark problem is a
>> typographic problem, and I’ve got a thing about type. [...] And like any
>> identity development, it’s only going to be the start. It’s up to you to
>> take this and run with it in the coming years.
>
> And so came my understanding that I could follow the same path for
> MuseScore: let the designers come up with the wordmark and give the future
> identity development to the community.
>
> This understanding only came to me just before releasing the results of the
> second iteration. I solely decided then to let the teachers, Marc & Bieke,
> take up the challenge to select the strongest wordmark which I also
> communicated in the post with the 2nd iteration results. My only concern was
> now whether Raúl could support us further with developing the MuseScore
> identity since he is the designer of the selected wordmark. Luckily, Raúl
> came back to me with a positive answer.
>
> I hope this story might answer some open questions. I sincerely apology if I
> may have raised different expectations on how the wordmark would be
> selected. Still, I hope we can go on with Raúls wordmark.
>
> Thomas
>
>
> Nathan Hale wrote:
>>
>> I for one really like the logo (although it wouldn't have been my
>> first choice, either) and I especially liked the mockups with the
>> simple stylized "MU" with the fermata...it looked pretty classy to me.
>>
>> Obviously our lead developers chose to leave the logo design in the
>> hands of the designers...and quite frankly I pretty sure that's their
>> prerogative, even under the GPL :). FOSS projects don't *have* to be
>> run democratically...many of them are (and I'm all for it), for sure,
>> but many of them aren't as well.
>>
>> Perhaps this is a good time to make it clear exactly how the project
>> is going be run in terms of community influence...Let's take this
>> opportunity to learn from each other a bit, but let's also not
>> overreact on this one issue. The logo/wordmark is certainly important,
>> but not nearly as much as getting a free, open, stable, bug-free, and
>> fully featured notation editor out there.
>>
>> My two cents,
>> ~Nathan R. Hale
>> Rom. 12:2
>> ---------------------------------------------------------------------
>>
http://nathanrhale.com - personal site
>>
http://linuxmusicians.com - create music freely
>> ---------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry® Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9-12, 2009. Register
>> now!
>>
http://p.sf.net/sfu/devconf>> _______________________________________________
>> Mscore-developer mailing list
>>
[hidden email]
>>
https://lists.sourceforge.net/lists/listinfo/mscore-developer>>
>>
>
> --
> View this message in context:
http://n2.nabble.com/Presenting-the-new-MuseScore-wordmark-tp3742104p3754185.html> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
>
http://p.sf.net/sfu/devconf> _______________________________________________
> Mscore-developer mailing list
>
[hidden email]
>
https://lists.sourceforge.net/lists/listinfo/mscore-developer>
is the only developer event you need to attend this year. Jumpstart your
ahead of the curve. Join us from November 9-12, 2009. Register now!