Sakai Design Patterns Library WG / UI Roadmap WG Weekly Meeting
2008-02-13/14 at 23:00 UTC time (3pm PST/6pm EST/8am Sydney)
Facilitator: Tim
Note taker: Barbara
Conference Call Info
Dial-in #: 812-856-7060
Conference ID: 350 #
Pin: 72524 #
Agenda
- Discuss Michael Korcuska's requirements proposal:
- blog entry: http://sakaiblog.korcuska.net/2008/01/18/product-management-in-sakai/
- wiki page: http://confluence.sakaiproject.org/confluence/display/REQ/2008+Proposed+Product+Management+Process (PLEASE READ PRIOR TO MEETING)
- new items on the Sakai UX Issues and Discussions list
- update on Pager: user testing results
- update on Design Patterns
- UX groups plans for Sakai 2.6 (and beyond)
Next Steps:
Note taker rotation: Allison, Barbara, Daphne, Eli, Erin, Jackie, Judy, Julie, Kathy, Shaw-Han, Tim, 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 (there is a "Copy" function in the Info tab) to create the next meetings agenda (make this a sub-page of "Meetings"). Update the agenda with any known items and included To Do's Strip out the notes section. (And leave this note for the next note taker.)
Meeting Notes
Present: Shaw-Han, Erin, Barbara, Allison, Daphne, Tim, Colin, Mike E., Will, Nathan Pearson, Kathy, Peter
Topics:
- Introductions of people to Nathan
- Nathan's update:
- Discussions with folks one-on-one basis
- Happy to discuss what he's doing, information gathering process, what are priorities, putting plan together.
- Identify what will make Sakai a better product, priorities
- Spreadsheet of usability issues might be helpful for Nathan
- How to take action on UE issues
- Peter what are people up to?
- Work should be out to community
- What are timelines for our stuff and Sakai releases
- User research in specific areas
- Colin discusses Fluid roadmap over next few quarters
- Next release 0.3 end of March
- 3 components:
- portlet layout manager
- file upload (may not make it for release)
- pager widget
- calendar widget
- 0.4 June
- File upload and Tagging components - activity based interactions
- Future releases
- "My files from anywhere": playlists, smart folders, searching
- Where are components useful across communities, plan more globally
- Put designs in Newsletter so people know about them
- Other design work (Opportunity for someone to pick up this work and continue with it)
- More-Tab work (wanted to do another iteration for Sakai 2.6--not sure if Fluid Resources will allow)
- Giving users a preview of how additional tabs will look when they save - building on Beth Kirschner's work
- Customized Tabs (a design for a better version is available - could be implemented if a developer is available)
- Link in tab row to Customize Tabs screen (Huge Usability area)
- Redesign of pager
- Preferences work
- Barbara Glover available to help work on the designs
- Looking for motivated developers
- More-Tab work (wanted to do another iteration for Sakai 2.6--not sure if Fluid Resources will allow)
- Hard to find stuff in Sakai UX area
- Web site should be more organized
- Sakai Search is difficult to use
- Hearing impressions of Michael K.'s proposal:
- Prioritizing bugs if no-one is going to take action on them
- So much stuff that needs fixing and gathering more info might not be worthwhile if nothing is getting done. Should focus on larger issues
- Developing tools or fixing bugs has been emphasis. Larger issues that need resources to work on them
- Some way other than jira for submitting requests
- Roadmap would be great!
- How does UX integrate early into process of requirements and design
- UX consulting service
- People know who to go to, to get UX help
- All this past UX research how to integrate into this process?
- Lack of incentive to involve UX due to small amount of designers
- Need to reach out to community about UX
- Education
- Place for people to connect with UX people
- UX comes in if a particular school is developing something and they don't have a UX person.
- Fluid is a 'home' of UX
- How are new tools and technology rolled into project?
- Variety of tools from different schools, are in core, how do they make it into core?
- How are changes evaluated?
- Historical over time has changed
- Initial set of tools needed and were put together quickly, don't meet a baseline that we hold new tools too.
- Guidelines for bringing tools into release. Tool criteria matrix.
- Tools can be nominated for a release if people think they are ready.
- Need to have common look and feel, perform better under load.
- UX criteria have been fuzzy
- UX side is less fleshed out than technical side
- Legacy tools should be improved
- No agreement for a high level UX vision
- How should a tool work?
- Larger UX issues that cross tools. Not being addressed but critical to consider.
- No gate keeping to know if something works or not, but doesn't get into higher level UX issues
- Higher rate of production? What is predominate at this time?
- New tools are being developed
- Also some are focusing on fixing older tools
- What is the product's vision?
- New feature set
- 2.5 - weighted towards new tools
- Need a vision to keep moving forward
- Is Sakai course management tool?
- Collaboration + learning environments
- People are trying to teach with it
- Instructors view it as teaching tool
- Project side less known, not marketed
- Institutional differences is why there is no consensus on this
- What does this UX group do?
- Discussion group
- Deliver for local issues, not as a group
- Might start working towards that, not sure
- There is some interest to have this group be more collaborative to produce designs to move things forward
- Nathan's Current Priorities
- Put plan together to work on
- People can get involved in
- Needs to learn culture, landmines, nuisances, etc
- We want to help him move UX vision forward
- Can we feed stuff/ ideas through Nathan to get people motivated.
- Group is excited about Nathan joining Sakai UX
Topics for next week:
- We will discuss the Requirements Proposal/Vision more next week.
- Process vision as well as product vision