For the latest information on the OSDPL Roadmap, please visit the OSDPL Roadmap

This project plan is a DRAFT, and will be used for the Fluid UX Team's planning exercises. The tasks which are coming up soon are defined in a more granular fashion than those far in the future.

 Fluid 0.1 Release

Add tasks to the List. Assign yourself to work and mark when complete.

{dynamictasklist:Fluid 01 Release}
||Completed||Priority||Locked||CreatedDate||CompletedDate||Assignee||Name||
|T|M|F| | |abloodworth|Determine where pattern will live (on a temporary basis, until a pattern library is started)|
|T|M|F| |1196405823286|abloodworth|Add introductory text to front page of DP Library|
|F|M|F| | | |Add examples of implementations in non-Fluid applications|
|F|M|F| | | |Add examples of implementations in Sakai|
|F|M|F| | | |Add examples of implementations in uPortal, Moodle (if possible)|
|F|M|F| | | |determine whether we have all needed DP sections by looking at other DP libraries|
{dynamictasklist}

General Planning

Add tasks to the List. Assign yourself to work and mark when complete.

{dynamictasklist:General Planning}
||Completed||Priority||Locked||CreatedDate||CompletedDate||Assignee||Name||
|F|M|F| | |abloodworth|Create meeting/working group plan|
|F|M|F| | | |Create project communications plan (for members interested in and impacted by the project, but not part of a working group)|
|F|M|F| | | |Determine what we think the goals of the project are in the current context (see Questions for the Group to Consider for some ideas)|
|F|M|F| | | |Create Scope statement for the project|
{dynamictasklist}

Research/Competitive Analysis

Add tasks to the List. Assign yourself to work and mark when complete.

{dynamictasklist:Research Competitive Analysis}
||Completed||Priority||Locked||CreatedDate||CompletedDate||Assignee||Name||
|F|M|F| | |abloodworth|Determine libraries to analyze (see Design Pattern Libraries)|
|F|M|F| | | |Analyze Design Pattern Libraries|
|F|M|F| | | |Select Design Pattern literature to read|
|F|M|F| | | |Read Design Pattern literature|
|F|M|F| | | |Are there Accessibility Design Patterns?|
|F|M|F| | | |Should Accessibility for a feature be it's own "pattern" or part of the component?|
{dynamictasklist}

User Needs Assessment

Add tasks to the List. Assign yourself to work and mark when complete.

{dynamictasklist:User Needs Assessment}
||Completed||Priority||Locked||CreatedDate||CompletedDate||Assignee||Name||
|F|M|F| | |abloodworth|Observe users of the Design Patterns Library (& likely the Design Handbook & Component Library) as they do work which uses it|
|F|M|F| | | |Revisit goals and scope statement based on research|
{dynamictasklist}

System Design

Add tasks to the List. Assign yourself to work and mark when complete.

{dynamictasklist:System Design}
||Completed||Priority||Locked||CreatedDate||CompletedDate||Assignee||Name||
|F|M|F| | |abloodworth|Determine whether we can reuse any Oracle materials/infrastructure|
|F|M|F| | | |Determine whether we can reuse UC Berkeley's Design Patterns Library infrastructure (PHP or Drupal version)|
|F|M|F| | | |Determine whether we can reuse materials from other design patterns libraries|
|F|M|F| | | |Gather existing content|
|F|M|F| | | |Determine content which must still be created|
|F|M|F| | | |Design information architecture|
|F|M|F| | | |Determine what technology will be used to present information|
{dynamictasklist}

Implementation

Add tasks to the List. Assign yourself to work and mark when complete.

{dynamictasklist:Implementation}
||Completed||Priority||Locked||CreatedDate||CompletedDate||Assignee||Name||
|F|M|F| | |abloodworth|Build system/website to hold Design Pattern Library/Design Handbook|
|F|M|F| | | |Create content|
{dynamictasklist}

Current Implementation (website building tasks)

{dynamictasklist:Website Building}

{dynamictasklist}

Project Plan Draft from Barbara

Activity

Task & Sub-task Work Breakdowns

Priority

Date Needed

Organize DP Team

  •  Select Coordinator
  • Look for Volunteers
    • Send email to communities to request volunteers
    • Fluid members who are interested
  • Determine OSDP meetings
    • How often
    • What day and time
  • How to work with partner communities (Sakai, uPortal, etc)

 

 

Create OSDP Library

  • Establish a timeline for completing below tasks to create the initial OSDP library.
    • The library will continue as a work in progress but initial construction needs a timeline.
    • Establish who will do what parts of above list and when each should be completed by.
    • Each steptask must be prioritized so the work can progress.
  • Create accounts for Fluid OSDP members who will be working on the library and adding patterns
  • Send out to Fluid-work and other mailing lists progress reports on the library and its creation.
  • Encourage volunteers to help with OSDP work.
  • Research how screen shots from commercial web sites should be included "legally" in the Fluid OSDP. 
    • Are there legal issues? 
    • How best to show screen shots? 
    • Can we include TMs and copyrights? 
    • What are other pattern libraries doing?** Add Fluid patterns already created
      • Drag and Drop
      • Reorderer
      • Pager
    • If a pattern that Fluid needs already exists in another "partner" community library like Sakai, link to it.  Add a Fluid example.
    • Fluid Patterns should have at least one Fluid example screen shot. 
      • If the pattern is also for another community like Sakai then add a Sakai screen shot as well.*** For Fluid patterns, make the Fluid screen shot larger and the first or most prominent one shown.  Show the other community screen shots smaller but on the same "page".
    • Use tagging to create "views" into the Fluid OSDP.  Tags for each community such as Sakai or uPortal would allow someone from those communities to find patterns relevant to their work.