Perfect! it is UPPER case in logo, but lower case in title. Just what we
have today in the main website!

2010/10/18 Bruno Rocha <rochacbr...@gmail.com>

> Note that in book cover: http://www.setbit.us/IMG_0108.JPG
>
> WEB2PY is UPPER CASE too!
>
> 2010/10/18 Bruno Rocha <rochacbr...@gmail.com>
>
> The Dealine is still 19 for send logos, and 21 for vote.
>>
>> That is the round 1, we can have round 2 with the 10 best voted, one week
>> more for the second round, No uploads just votes.
>>
>> For the second round we can change rules and implement some new ideas as
>> commented here.
>>
>> ------
>>
>> BTW: I keep the track of "web2py" in twitter, identica, orkut, facebook,
>> reddit, googleAlerts, etc..
>> 99% of the people, when talking about web2py, are talking about the new
>> visual stylle.
>>
>> Everyone likes that, and that already is the new face of web2py, I think
>> if we have to change, dont have to change too much ( I like this idea
>> http://blouweb.com/logovote/default/index?logoid=17 )  It keeps the
>> actual style and gives us an Icon (that could be improved). I think it is
>> clean, beauty, soothing enought and enterprise as well.
>>
>> There are other important things about this logo (17 or 5), it is nice
>> with any background, the main idea came from Massimo, it differs web2py from
>> web.py, It is easy to draw, easy to print, easy to remember.
>>
>> The upper case in that is more closer to WEB2PY (because we have DAL, DIV,
>> FORM..)
>>
>> In the beggining it is strange to switch from web2py to WEB2PY, but IMO
>> UPPER case fits better in for logo, and everyone will differ web.py form
>> WEB2PY.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 2010/10/17 Anthony <av201...@yahoo.com>
>>
>> So, what's happening with the voting method? As already discussed at
>>> length, the one-vote-per-person method isn't a good idea with so many
>>> entries (particularly with sets of similar logos). For example, #5 and
>>> #17 are probably splitting votes.
>>>
>>> We really should implement one of the other suggested methods:
>>> * Approval Voting (vote for as many logos as you want): Probably the
>>> easiest to implement, and should handle the "clone" problem. (Still
>>> need the ability to change one's vote(s)).
>>> * Ratings: Though for this to work, either everyone has to rate every
>>> logo, or for each voter, each un-rated logo has to be assigned the
>>> lowest possible value (e.g., 1 star).
>>> * Ranking: Preferably using the Schulze method for tallying. Probably
>>> the most complex to implement.
>>>
>>> If we're not going to do any of the above, then at the very least, we
>>> should go back to showing the _number_ of votes for each logo (no need
>>> to show the names -- they should remain anonymous). That way, at least
>>> we could see if we are splitting (and possibly wasting) our votes and
>>> then shift our support to a logo we like that has a chance of winning.
>>>
>>> If we stick with the current voting method, with 50+ logos, we could
>>> easily end up with a "winner" that gets the support of only a small
>>> percentage of the voters.
>>>
>>> Also, is the voting deadline still Oct. 19?
>>>
>>> Thanks.
>>>
>>> Anthony
>>>
>>> On Oct 13, 5:17 pm, Bruno Rocha <rochacbr...@gmail.com> wrote:
>>> > Martin Mulone made the logovote application.
>>> >
>>> > I am hosting at my server
>>> >
>>> > You can post logo ideas, and vote for you prefered logo.
>>> >
>>> > Better if you made an transparent canvas .gif or .png maximum 250x70
>>> >
>>> > Maximum of 10 uploads per user, Just one vote per user.
>>> >
>>> > Take a look:http://blouweb.com/logovote/
>>>
>>
>>
>>
>> --
>>
>> http://rochacbruno.com.br
>>
>
>
>
> --
>
> http://rochacbruno.com.br
>



-- 

http://rochacbruno.com.br

Reply via email to