Nominating a creative director

[Kevin Ottens]

Le Thursday 29 May 2008, Aaron J. Seigo a écrit :
> the creative director would take it upon themselves to:
>
> * ensure there is a defined visual goal. note that this is not necessarily
> the same as defining it themself; they can (and should) make it an effort
> that takes several voices into consideration
>
> * coordinate those working on art and those using it in the code
>
> * communicate regularly about what is happening
>
> * discover limitations put upon visual elements due to technical issues
> (systray is a good example here) and either push at the technical
> implementors (coders) or adjust the visual implementation (or both) to
> achieve harmony
>
> * make the "hard" decisions when needed to avoid just discussing different
> points of view without any final decision being made
>
> this is, as you can see, not about power at all but about coordination.

And this is much more appropriate to our culture if the goals are defined this 
way.

Just like Chani I found Riccardo's mails scary at best...

Regards.
-- 
Kévin 'ervin' Ottens, http://ervin.ipsquad.net
"Ni le maître sans disciple, Ni le disciple sans maître,
Ne font reculer l'ignorance."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/panel-devel/attachments/20080529/d4f64909/attachment.pgp