I'd approve to that.

Tom.


Martin Hollmichel wrote:
Would it make sense to introduce a subcomponent for this in the ui project and make stella the default owner or QA contact ?

Martin


Tom Verbeek wrote:
Hi,

we currently have a major problem that resulted from a number of CWS that integrated changes to icon files. Mostly bugfixes these changed icons covered accessibility issues and others, so it was good that they have been modified.

The problem results from the fact that the icons have been modified without being looked over by the designer of the default icon set, which was Stella Schulze from Sun. Subsequently the current status of the icons in module default_images conflict with the set that is being maintained by Stella.

Sun does not want to restrict contributions to the icon set to Sun employees. The icon set that is checked in in module default_images is being used for StarOffice and OO.o and has been completely designed by one person (Stella). The issue we have is more about keeping the design consistent and - what's even more important - keeping the current tooling/workflow working. The IconTool is a database with a web based frontend that allows for a lot of useful measures to work with the icon set (including sorting/grouping them by semantical criteria). I feel that the IconTool should be available on OO.o, at least with read access.

I would like to set up a policy for changing icons. Please do not add module 'default_images' to your own CWS. Please do not check in icons. The best way to get in your changes would be to

a.) write an issue to [EMAIL PROTECTED] and request the change to an image

b.) modify an image and send it to [EMAIL PROTECTED]

This way we can reach the goal of keeping the default icon set consistent.

Again: Sun does not want to keep sole control over the look&feel of OO.o. The community could vote on changing the default icon set to a different set. But the set Sun provided for StarOffice and OpenOffice so far needs to be under supervision of the original designer for the above reasons.

Thanks for your understanding. Please do comment on this.

Regards,

Tom Verbeek.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to