Page Comparison

...

• Brief Introductions
  • Name, job, institution, experience with UI design patterns, how you'd like to participate or what you'd like to get out of this group
• The Fluid Project & UI Design Patterns
  • The Open Source Design Pattern Library - preview release: http://uidesignpatternsosdpl.fluidproject.org
• What should the goal of the Open Source Design Pattern library group be?
  • Potential discussion topics:
    • Who is our audience?
    • How are patterns contributed, edited, and moderated?
    • Do we need a 'staging area' before releasing in process patterns?
    • How can we build a self-sustaining community of contributors?
    • Should there be patterns other that UI Design Patterns included in the library (e.g. HCI or pedagogical patterns like "Widespread participation"?)
    • Should patterns be general and apply to everyone, or customized for each community?
    • How can we encourage contributions and at the same time ensure the quality of the patterns remains high?
    • How can we ensure the library grows, evolves, & lives on?
    • Design Pattern Library Proposal
    • Jonathan's discussion of Workflow options: ** (see below)
    • Colin's preference for a community-driven ratings system (bottom of this page: http://wiki.fluidproject.org/display/fluid/Design+Patterns+Library+Proposal)
    • Discussion of Design Pattern Library Proposal
• Where do we go from here?
  • Future meetings
    • Day, time, alternating AM/PM, breeze vs. teleconference?
  • Participants
  • What work needs to be done?
    • bug fixing in Drupal: http://uidesignpatternsosdpl.fluidproject.org
      • need to show patterns as child nodes of categories in navigation (may not work automatically with taxonomy_menu...must we enter every one manually?)
      • Remove line on Home page where it says a the page is "in" a category...because the home page isn't
      • Figure out how to deal with child patterns
        • add a 'child patterns' field near the top of the display
        • link to sub-patterns from main Drag & Drop pattern
        • allow patterns to have hierarchy beyond categories?
      • remove UI Design Patterns link from navigation? Or perhaps we should keep it if we may have other categories of patterns in the future? If so, we need to create a View for it.
      • make URLs nicer for categories (currently generated by taxonomy_menu module)
      • issues with text being left-justified (e.g. on this page: http://127.0.0.1/drupal-5.7/admin/settings/taxonomy-breadcrumb)
      • turn off unused modules
      • on some pages, breadcrumb shows "::" when taxonomy_menu module is used
      • Finalize Design Pattern submission form - Allison
      • Required asterisk missing from ImageField in DP input form
      • Tweak styling of OSPL site and check cross browser behaviour
      • Finalize Screenshot policy for design patterns (or do not use any proprietary screenshot examples)
      • Streamline sidebars in OSDPL to improve UX
    • UX Walkthrough of OSDPL application
    • Addition (& editing) of Sakai Design Patterns
    • Creation (& review/moderation of?) new design patterns
    • Future features
      • Workflow & Notifications of actions required: the submission and approval of patterns and changes to patterns, and notifications that review or approval is necessary. Though this hasn't been decided for certain, approvals of changes would likely be managed by a moderator or group of reviewers. This is to ensure the pattern library remains a very high-quality reference for its diverse users. Again, community ranking and tagging may play a role here.
      • User Roles: give users different levels of access to add or edit patterns based on administrator-defined roles
      • Personalized Tags & Tag Clouds: allow all users to create their own personalized tags which have meaning to them to filter the patterns
      • Ratings of comments
      • Customized views of patterns & User Profiles: allow users to view the uPortal example images for a pattern vs. the Sakai example images based on the community they are associated with their profile - likely a future feature
      • Interface with and connect users to the Fluid Component Library & Fluid UX Toolkit (could be as simple as creating links, or as complicated as creating a presentation framework for these two items as well)
  • How can we distribute our work?

...