RE: [ui-arch-working-group] suggested charter

["Troy Beecroft" <troyb@xxxxxxx>]

These activities strike me generally as a practical approach.  I
particularly like that it engages the various project members.

Also, the "best practices" name change seems much closer to the mark,
especially given this proposed modus operandi.

-Troy

-----Original Message-----
From: ui-arch-working-group-bounces@xxxxxxxxxxx
[mailto:ui-arch-working-group-bounces@xxxxxxxxxxx] On Behalf Of Boris
Bokowski
Sent: Tuesday, August 29, 2006 3:52 PM
To: ui-arch-working-group@xxxxxxxxxxx
Subject: [ui-arch-working-group] suggested charter


Since we last met, we had a conversation with Julian Jones who worked on
cross-project usability in the early releases of Eclipse, when cross
project meant Platform, JDT, and PDE.  Based on his recommendations on
what
was most effective to improve the usability and consistency, we propose
the
following charter for the working group.  Note that there is more to it
than just updating the guidelines.  We can use tomorrow's call to talk
about this in more detail.

Boris


Eclipse UI Best Practices Working Group

The mandate of the working group is to help improve the usability across
the Eclipse projects that are part of the simultaneous release effort.

To this end, the working group will do the following:

1.  Facilitate usability discussions within projects and across projects
      - Trigger usability post-mortems to be performed by the
differerent
projects
      - Conduct regular "show and tells" with UI leads from the projects
to
shed spotlight on problem areas and promote good ideas as best practices
      - Do an end of release UI review and come up with a cross-project
list of polish items

2. Update the UI guidelines

_______________________________________________
ui-arch-working-group mailing list
ui-arch-working-group@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ui-arch-working-group
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.