Sakai Design Patterns Library WG / UI Roadmap WG Weekly Meeting
2007-11-06/07 at 23:00 UTC time (3pm PST/6pm EST/8am Sydney)
Facilitator: Allison
Note taker: Daphne
Conference Call Info
Dial-in #: 812-856-7060
Conference ID: 350 #
Pin: 72524 #
Agenda
- Open Source Design Pattern Library (OSDPL) proposal
Present
- Allison, Eli, Marc, Daphne Colin, Barbara, Will, Kathy, Paul, Gary
Notes
- Allison went over the Design Pattern Strawman: http://wiki.fluidproject.org/display/fluid/Design+Patterns+Library+Proposal
*Excerpt from the email she sent out previous to the meeting that we reviewed:
"In the meantime, some of the major points of the proposal include:
-
- We'd like the library to be co-branded by all the contributing organizations (e.g. Sakai, uPortal, Moodle, Kuali Student), indicating that it is a cooperative effort of all these communities, and not a "Fluid" library
- The library will provide a space for Fluid (and maybe other open source) communities to grow their own design patterns libraries, and contribute to a larger library at the same time
- the goal of the library will be to introduce design patterns as a way to design the proper user interface for a specific context (though this process will not be totally prescriptive, and some choice/judgement will definitely be involved)
- The library will initially use the UC Berkeley Web Patterns Library design/framework (http://harbinger.sims.berkeley.edu/ui_designpatterns/webpatterns2/webpatterns/home.php), and hopefully be expanded to include many additional features to make the library more usable to its target audiences in the future
- Target audiences for the library (in relative order of precedence) will be: junior UI designers & UI designers new to the community, developers who need to design the UIs they build, and more experienced UI designers
- We'd like to bring Sakai design patterns into OSDP library because it will:
1) offer a better presentational framework than the wiki
2) allow Sakai patterns to be shared with the other Fluid communities as appropriate - Folks working on the Fluid project will take the lead on creating patterns related to Fluid components. Fluid project team members will also work with each of the communities to advise and/or assist with the creation of additional patterns.
- Design patterns libraries can sometimes function as somewhat of a style guide, and this is a link we should explore"
- Restrict to Higher Ed?
- We want to focus on higher ed and specifically Fluid goals and projects. BUT no reason to be exclusionary.
- Will suggested looking at the library that is a work in process at: http://new.osportfolio.org/ There may be some ideas, code, etc. that can be leveraged.
- If we use a common pattern library, what happens to the more style guide-like standards we want to promote.
- Drupal is brandable so there could be content specific to a project within the space.
- Another question is about how we show examples. So if a pattern relates to multiple products, we want to show them the relevant examples, codes, etc.
- As soon as Allison gets the pattern library up and running we'll want to continue building out patterns. Everyone is welcome to join this effort.
- There is also some research and competitive analysis going on now. Let Allison know if you'd like get involved
- What else would this group like to do with these calls?
- Everyone is interested in design patterns
- uCamp that happens every 6 months
- Roadmap work - getting involved in projects
- We can be flexible and focus on design patterns now while there doesn't seem to be other burning work and when it happens, we can make room for it.
- Should we have separate groups for Sakai, uPortal & Fluid design patterns?
- People seemed to want one overarching group since patterns likely cross products.
Next Steps:
- Allison will schedule a meeting for design patterns
- Next week's meeting will focus on uCamp
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.)