Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "UIBPWG060830"

 
Line 1: Line 1:
=UI Best Practices Working Group Meeting - 2006-08-30=
+
==UI Best Practices Working Group Meeting - 2006-08-30==
  
 
Attending: Bob Fraser, Troy Beecroft, Boris Bokowski, Wassim Melhem, Bjorn Freeman-Benson, Ward Cunningham
 
Attending: Bob Fraser, Troy Beecroft, Boris Bokowski, Wassim Melhem, Bjorn Freeman-Benson, Ward Cunningham
  
==Reviewed action items==
+
*Reviewed action items
  
 
*The group decided to change its name to the "Eclipse UI Best Practices Working Group" to better reflect the charter and to avoid confusion with what the Platform/UI team does.
 
*The group decided to change its name to the "Eclipse UI Best Practices Working Group" to better reflect the charter and to avoid confusion with what the Platform/UI team does.
 +
 
*Discussed the charter and adopted Boris' suggestion '''- [[User Interface Best Practices Working Group#Charter|see charter]]'''
 
*Discussed the charter and adopted Boris' suggestion '''- [[User Interface Best Practices Working Group#Charter|see charter]]'''
 +
 +
*Discussed the fine points of what the three activities under item one above mean, what the roles of the working group should be and what the roles of the projects should be.  Troy will write up a draft document.
 +
 +
*Discussed how to put things in motion.  We will come up with what we believe the practices and activities should be (eg. Post-mortems, show and tells, etc.) and propose this to the planning council.  Our goal is to get their buy-in and have them help drive this as requirements through the various projects that make up the simultaneous release.  Goal is to have actionable plans by the October Eclipse Council meetings.
 +
 +
*Suggestion was made to have three categories of requirements:
 +
**Must
 +
**Should
 +
**Suggestion
 +
 +
*Discussed the difference between "consistency" and "usability".  Having a consistent interface is not sufficient if it is not usable.
 +
 +
*Members discussion. We with to invite the following companies/projects:
 +
**Intel
 +
**Borland
 +
**Acutate
 +
**WTP
 +
**We will also look through newsgroup threads for individuals with a keen interest in the UI/usability of Eclipse.
 +
 +
*Action items:
 +
**Bjorn to change the name of the group, mailing list and wiki
 +
**Bob to draft a general call to action to join the group
 +
**Bob to update the wiki with the new charter
 +
**Troy to draft the next level of detail for the charter and what we wish to ask the planning council to drive as requirements.
 +
**Membership invitations - develop leads and invite:
 +
***Bob - Borland, Actuate
 +
***Boris - Intel
 +
***Wassim - WTP

Latest revision as of 18:35, 13 September 2006

UI Best Practices Working Group Meeting - 2006-08-30

Attending: Bob Fraser, Troy Beecroft, Boris Bokowski, Wassim Melhem, Bjorn Freeman-Benson, Ward Cunningham

  • Reviewed action items
  • The group decided to change its name to the "Eclipse UI Best Practices Working Group" to better reflect the charter and to avoid confusion with what the Platform/UI team does.
  • Discussed the charter and adopted Boris' suggestion - see charter
  • Discussed the fine points of what the three activities under item one above mean, what the roles of the working group should be and what the roles of the projects should be. Troy will write up a draft document.
  • Discussed how to put things in motion. We will come up with what we believe the practices and activities should be (eg. Post-mortems, show and tells, etc.) and propose this to the planning council. Our goal is to get their buy-in and have them help drive this as requirements through the various projects that make up the simultaneous release. Goal is to have actionable plans by the October Eclipse Council meetings.
  • Suggestion was made to have three categories of requirements:
    • Must
    • Should
    • Suggestion
  • Discussed the difference between "consistency" and "usability". Having a consistent interface is not sufficient if it is not usable.
  • Members discussion. We with to invite the following companies/projects:
    • Intel
    • Borland
    • Acutate
    • WTP
    • We will also look through newsgroup threads for individuals with a keen interest in the UI/usability of Eclipse.
  • Action items:
    • Bjorn to change the name of the group, mailing list and wiki
    • Bob to draft a general call to action to join the group
    • Bob to update the wiki with the new charter
    • Troy to draft the next level of detail for the charter and what we wish to ask the planning council to drive as requirements.
    • Membership invitations - develop leads and invite:
      • Bob - Borland, Actuate
      • Boris - Intel
      • Wassim - WTP

Back to the top