On 14/10/11 12:29 +0200, Bertrand Chenal wrote: > Le Fri, 14 Oct 2011 11:48:46 +0200, > Cédric Krier <[email protected]> a écrit : > > > > > Tryton. Our image only starts to be known that we should not > > > > change it. > > > > > > > > > > It's your point of view. :) > > > > So what is your point of view about the knownledge of Tryton's image? > > I have no point of view about what people know about Tryton, but a > point of view about the evolution of the image of Tryton. > > Most if not all companies/products have changed (or will change) their > image.
There is two factors that generates those changes:
- Trying to make forget bad image
- An new direction for the company/product
I think we are in any of both cases.
> First, this brings some freshness (and shows to people that there
> is some activity)
If it is the only way for a project to show it is living than it is in really
bad shape. This will be the worst cases (first point of the two factors).
> and sometimes the change is made to fix issues with
> old design (nobody is perfect).
You can fix design issue but keep the same spirit.
> Simple example: the gradient at the bottom of the logo. IMO it looks
> already old-fashioned (gradient are so '09 ...)
So for you the website must change every 2 years.
I really prefer to spend times to improve the software than having such boring
discussion on the website design.
> and moreover it can
> not be printed reliably (on T-shirts for example), so it's not
> consistent.
There is no issue to have declination of the same logo depeding of the
support. And removing this gradient is not really a change of the image of
Tryton but just a fix. (Completly different than adding a new color).
> Still in my opinion, one of the important principle that we follow since
> day one in Tryton is that we try hard to develop code that is designed
> to stay,
The same for the image.
> but at the same time we are not afraid of change if we see it
> as an improvement. So, I think we should have the same approach with
> the image of Tryton.
Except that the code is visible only to the developpers.
Moreover when such changes happen, we change all the code to work with the new
design because we can master the code. But talking about external image, it is
completly different, we don't master it. We already have some issues with some
guys using old/wrong logo, wrong name (Tryton ERP) etc.
Changing the image of the project must be done with great caution.
I don't want that the Tryton project has the image (like some others follow my
eyes) to change everything on each releases.
Having a stable image is also a good message sent outside that we are stable
and reliable (like the release policy, bugfix backport…)
--
Cédric Krier
B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: [email protected]
Website: http://www.b2ck.com/
pgpGvD1jjjcOH.pgp
Description: PGP signature
