Sakai Design Patterns Library WG / UI Roadmap WG Weekly Meeting

2007-10-08/09 at 23:00 UTC time (3pm PST/6pm EST/8am Sydney)

Facilitator: Tim
Note taker: Allison

Conference Call Info
Dial-in #: 812-856-7060
Conference ID: 350 #
Pin: 72524 #

Agenda

• Progress with Spreadsheet
• Current Design Pattern review, status update
• Roadmap - what's happening with it?  what do we want to happen to it?  should we include those issues in the Fluid UX Walkthrough reports? - Talk to Michael K?
• Future Design Patterns
• Student view v Staff view - is there such a concept? as is the case in WebCT

Present

Allison, Daphne, Eli, Tim

Notes

• Tim updated us on what Michael K discussed last week about the UX initiative

User experience issue spreadsheet

• this is related to the Fluid UX walk-through work - should we pull this into the Fluid work?
  • probably not; may need to reside in both places
• the spreadsheet is valuable to show that we have helped some of these issues have been fixed & make the user experience work transparent
• goal of the spreadsheet was to get a sense of what we knew about the state of usability/ux within Sakai - this group is the audience, not the Sakai community
• top 10 list of usability problems to show the community? - based on the spreadsheet
• we could make the spreadsheet more of an executive summary, easier to review
• we could work on issues in the spreadsheet in a programmer/designer half day work session at the Sakai conference

UI group decisions

• should we bring UI roadmap, design patterns, etc. pages together?
  • Tim could do some, Will's been doing some editing of the DP...maybe we could see if he would have time to work on it...then we could put the call out to the community for more help if needed.
• do our groups need a mission statement? - Tim will try to pull that out of the UI Roadmap proposal

UI roadmap proposal - begun early 2006

• goal: get ux issues put into the requirements process
• community volunteers in the requirements wg synthesize all the requirements
• this release, there were too many requirements, so everyone in each group chose the top 10 for the community to vote on
• if something is voted to the top of the requirements, what does this mean? maybe not a lot, as someone still has to volunteer to fix it
• long ago, Daphne tried to get folks to approve 'design bugs' just like 'programming bugs' ...requirements wait for someone to pick them up and aren't assigned to anyone.
• may be hard to convince the community that a usability/design bug is a blocker
• do we need political muscle that the UX lead may be able to deliver? then existing partners could give resources to this person

Planning for u-Camp

• not much done yet

To do for next meeting:

• this call is getting smaller & smaller - we may need to send a list out to community about who can help with our "to do's" instead of just assigning them to the people on the call

1. formatting UX issue spreadsheet to make it more usable/creating "executive summary"
2. noting items in UX issue spreadsheet that have already been completed
3. coming up with next steps for UX spreadsheet issues
4. creat top 10 list of usability issues from UX spreadsheet (for community)
5. reorganizing UI spaces in Sakai wiki
6. have all attendees review the UX issues spreadsheet and help us determine what to do next with it

Note taker rotation: Allison, Colin, Daphne, Eli, Jackie, Judy, Julie, Kathy, Marc, Shaw-Han, Will

Note to note taker: On the Home page, please make these notes the "Last meeting's notes" link and increment the next meeting date and agenda link. Also, once you are done with these notes please duplicate and this page to create the next meetings agenda (make this a sub-page of "Meetings"). Update the agenda with any known items and included ToDo's Strip out the notes section. (And leave this note for the next notetaker.)