<div dir="ltr">+1 from me to have some kind of design <span style="font-size:13px;font-family:arial,sans-serif">committee</span>. If we don't focus on this area of the project in the near future I feel it will always reflect an amateur project status, and as we all know that is not the case. Provided we have a mailing list that we can see what is going on and have some input if we feel then I'm all for that kind of thing. <div>
<br></div><div>I'm happy for Larry to be on said committee regardless of his work on the logo comp. Anita would also get my vote. Nyall would also be another person I would like to see added as he has some skills in this area. M<span style="font-family:arial,sans-serif;font-size:13px">athieu (nIRV) is another.</span><br>
</div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><font face="arial, sans-serif">So the committee so far for me:</font></div><div><font face="arial, sans-serif"> - Larry</font></div>
<div><font face="arial, sans-serif">- Anita</font></div><div><font face="arial, sans-serif">- Nyall</font></div><div><font face="arial, sans-serif">- </font>M<span style="font-size:13px;font-family:arial,sans-serif">athieu </span></div>
<div><span style="font-size:13px;font-family:arial,sans-serif"><br></span></div><div style><span style="font-size:13px;font-family:arial,sans-serif">I think it's best to keep it small or else we end up back in this situation again.</span></div>
<div><br></div><div>The current situation is that we HAVE to pick a design from the logo comp and pay the "winner" regardless of if we use that logo or not. 99design rules not mine. If everyone is currently not 100% happy with what has been presented I suggest that we pick one of Larry's, give him the money, and ramp up the committee to design something better. I would rather see the money go to one of our devs if we are not happy so the money stays with the project and we can keep working on it. </div>
<div><br></div><div>I will send an email to PSC asking for a vote on this and if I get all +1s then I will pick Larry as the "winner" so we can all move on and not have this hanging above our heads.</div>
<div><br></div><div>Regards,</div><div>Nathan</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, May 19, 2013 at 5:42 AM, Tim Sutton <span dir="ltr"><<a href="mailto:lists@linfiniti.com" target="_blank">lists@linfiniti.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi<br>
<div><div class="h5"><br>
On Sat, May 18, 2013 at 8:30 PM, Larry Shaffer <<a href="mailto:larrys@dakotacarto.com">larrys@dakotacarto.com</a>> wrote:<br>
> Hi,<br>
><br>
> On Sat, May 18, 2013 at 8:10 AM, Tim Sutton <<a href="mailto:lists@linfiniti.com">lists@linfiniti.com</a>> wrote:<br>
>><br>
>> Hi<br>
>><br>
>> On Fri, May 17, 2013 at 11:59 PM, Larry Shaffer <<a href="mailto:larrys@dakotacarto.com">larrys@dakotacarto.com</a>><br>
>> wrote:<br>
>> > Hi,<br>
>> ><br>
>> > On Fri, May 17, 2013 at 8:42 AM, Tim Sutton <<a href="mailto:lists@linfiniti.com">lists@linfiniti.com</a>> wrote:<br>
>> >><br>
>> >> Hi<br>
>> >><br>
>> >> I have to say when I compare them to our existing logo, none of them<br>
>> >> really do it for me. Perhaps we need a new mandate to freshen our<br>
>> >> exisiting logo rather than to try to create something new. Our current<br>
>> >> logo may have issues but it is:<br>
><br>
> ------snip 8< -------------------------<br>
>><br>
>> > Sorry, again, but I think the current logo falls far short of those<br>
>> > goals,<br>
>> > and any focus on revamping it is just prolonging the inevitable decision<br>
>> > to<br>
>> > move to a better one.<br>
>><br>
>><br>
>> Just to clarify - I am not opposed to replacing the logo at all. I<br>
>> just want to replace it with something that properly addresses our<br>
>> needs rather than taking an option we are not happy with simply<br>
>> because of the 99designs competition deadline. Currently there isn't<br>
>> an entry in my opinion that does this - for me anyway.<br>
><br>
><br>
> I agree 100% that a logo should not be settled upon, but happily selected,<br>
> regardless of any competition deadline. It's a very important decision. I<br>
> have a couple of ideas to overcome the current impasse:<br>
><br>
> 1) Run off - Currently there seems to be two popular designs, but a general<br>
> consensus that neither is the 'right' one. There could be a short-term 'run<br>
> off' competition that allows those two designers to try and come up with<br>
> better designs, in an attempt to find a good solution for 2.0 release.<br>
> Again, this should not mean the result has to be binding, i.e. the winner's<br>
> logo used.<br>
><br>
> 2) Use current logo - For 2.0 release, just use the current logo, as is.<br>
> After 2.0 release, I suggest the forming of an design committee to manage<br>
> another go at finding a new logo, and for the reasons mentioned below.<br>
><br>
> 3) Design committee - Kudos to Nathan for his efforts on the competition and<br>
> getting everyone involved in the process. In retrospect I think a logo by<br>
> popular consensus, as a means of getting to final logo selections, may not<br>
> be the best course of action. In many organizations there are people with<br>
> design background or knowledge who work on making the initial selections to<br>
> bring to the community or those who make decisions.<br>
><br>
> For example, the popular #50 has a inherent design flaw of being 95% black,<br>
> even though the rest of the design is OK. Such a committee could have<br>
> spotted this early on and asked the designer to work on a fix, before the<br>
> logo was presented to the community/PSC to vote on.<br>
><br>
> I suggest such a committee be formed and comprised of 3-5 people who's job<br>
> is to manage and make initial decisions on:<br>
><br>
> * Project logo, design style, fonts<br>
> * Marketing material design style<br>
> * Documentation/web site template style and fonts<br>
> * Program's general icons, toolbar icons, splash screen and style<br>
><br>
> A design committee will allow a cohesive 'look' for all parts of the project<br>
> to start taking shape. The committee should probably answer to and be under<br>
> the purview of the PSC marketing advisor, and have specific abilities<br>
> bestowed upon it members to vote internally to act on smaller decisions<br>
> without needing full PSC approval.<br>
><br>
> Basically, I feel design by community popular vote is not a good approach:<br>
> too many cooks in the kitchen. This committee could be formed now, with an<br>
> initial goal of handling the current logo situation. While personally I have<br>
> a lot of design experience and would like to be on such a committee, I<br>
> understand my current conflict of interest regarding the logo, and would<br>
> recuse myself regarding its decision.<br>
><br>
> An active community member who has clear public examples of quality,<br>
> design-oriented work would be Anita Graser. So, I would nominate her to be<br>
> on such a committee.<br>
><br>
<br>
</div></div>That all sounds like a very reasonable approach. I think this kind of<br>
filtering would be good as in retrospect there was such a high noise<br>
to signal ratio in the design competition I didn't find the process<br>
worked well for me. Hats off to Nathan for all the effort he put into<br>
it, but a more filtered and considered approach as described above<br>
sounds good. It would be also good to have a more rigorous set of<br>
criteria - the emotional response to a logo should be the last part of<br>
the process not the first, basic design principles should first be<br>
ticked off.<br>
<br>
+1 on your suggestions above<br>
<br>
Regards<br>
<br>
<br>
Tim<br>
<br>
<br>
> Regards,<br>
><br>
> Larry<br>
><br>
><br>
>><br>
>> Regards<br>
>><br>
>> Tim<br>
<div class=""><div class="h5"><br>
<br>
<br>
--<br>
Tim Sutton - QGIS Project Steering Committee Member (Release Manager)<br>
==============================================<br>
Please do not email me off-list with technical<br>
support questions. Using the lists will gain<br>
more exposure for your issues and the knowledge<br>
surrounding your issue will be shared with all.<br>
<br>
Visit <a href="http://linfiniti.com" target="_blank">http://linfiniti.com</a> to find out about:<br>
* QGIS programming and support services<br>
* Mapserver and PostGIS based hosting plans<br>
* FOSS Consulting Services<br>
Skype: timlinux<br>
Irc: timlinux on #qgis at <a href="http://freenode.net" target="_blank">freenode.net</a><br>
==============================================<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</div></div></blockquote></div><br></div></div>