oship-dev team mailing list archive

[Maxwell Dayvson <dayvson@xxxxxxxxx>]

*Hi Roger, My comments area in red.*

cheers,


On Thu, Sep 17, 2009 at 2:45 PM, Roger Erens <roger.erens@xxxxxxxxx> wrote:

> Hi Maxwell,
>
> Having had a chemical training, I like it! But on the other hand, it has a
> high 'straight from the labs' meaning. I don't know if we want to convey
> that (in the long run) to users who might like something 'stable' or
> 'proven'. But maybe there are users who feel adventurous and that's why they
> choose OSHIP. Who do we want to target?


> We should have a story behind the logo: what do we want it to convey; what
> does it mean; and also try to imagine what kind of
> feeling someone gets when (s)he first sees it.
>
*
Your feedback and tip about the story behind the logo is very important. And
I`m trying to think in another logo with this "rules"* ;)

>
> In the oship/src/oship/static/images directory I put some oship-logo_star
> images with my stab at creating a logo. It is composed of 5 outward-lying
> puzzle pieces (OSHIP has 5 letters) that visualize the complex field of
> health informatics. OSHIP has 'solved' the puzzle and comes out as a shiny
> star, connecting 'all the pieces'. The pieces are connected via the hub in
> the middle.
> The color is green because I) Tim likes that, as is clear from his logo;
> and II) because python snakes are green (I'm not sure though that they all
> are). But there's no snake in the logo as in Tim's, because in the long run
> I don't think that (end) users care about the programming language being
> used.
>
*
**I agree with you. I believe that the OSHIP is something much bigger than a
python program and it  is independent of  the language it was developed.
I Don't think that we have to put a snake at the logo, because in future,
if we migrate to another language, we have to change the visual identity of
the project  and that is not cool to the integrity.
*

> As a bonus, I envisage that when used in a document with several sections,
> every section could have another outward lying piece in a differing color in
> its header. I used Inkscape to create the .SVG-format. Hence it should look
> good in any resolution and size.
> *
> *

Maybe you can use this sort of rationale behind a logo, maybe not. Another
> option might be to try to find some (junior) designer who wants to show off
> his/her capabilities and sponsor us with a logo.
> *
> *

*I'll try to think in this sense too.
But now I'm going to start codereview-common. By the way, it is nice to try.
*

Cheers,
>
> Roger
>
> On Thu, Sep 17, 2009 at 17:57, Maxwell Dayvson <dayvson@xxxxxxxxx> wrote:
>
>> Hi, Tim and everybody.
>> This is my first contribution in this project,
>> In Python Brasil Conference, I've talked to Tim about project and he
>> explained me why the project doesn't have logo.
>> I've decided to create a simple logo. Of course, I'm not a designer, so I
>> am afraid the result will only be good enough.
>> I'm proposing this new logo (see attachment) for the time being.
>> What do you think about it?
>>
>> cheers!
>> --
>> Maxwell Dayvson
>> www.dayvson.com
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~oship-dev<https://launchpad.net/%7Eoship-dev>
>> Post to     : oship-dev@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~oship-dev<https://launchpad.net/%7Eoship-dev>
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>


-- 
Maxwell Dayvson
www.dayvson.com