OSDPL roadmap (Jan. - Mar. '09), planned pattern workflow, and features
Quick Background on Issues
In November 2008, user testing was carried out to test some features of the OSDPL. The results of that user testing revealed the following issues:
not clear how a draft pattern gets to a published state.
how does a pattern get promoted once in a published state?
how does the feedback process work on a draft pattern? Who gets to give feedback? Can others not on the system be allowed to be part of this process?
This document outlines the tasks and goals required to improve the above issues. A sizable portion of this work is dedicated to solidifying a "community process" in which various users and groups collaborate on design patterns. An outline of the interactions in this community process is also contained in this document.
Goals for January to end of March 2009:
Fix the site so it is usable in its most essential features.
Finish editing existing Fluid and Sakai patterns in the OSDPL.
Engage communities and build a sustainable OSDPL community beyond March 2009.
Implement a flexible pattern workflow and create site functionality that encourages and nurtures community participation.
These goals are accomplished via the timeline below.
Timeline:
Early to Mid January 2009 (Design Iteration 24):
Fix bugs and make critical improvements to existing site functionality.
Objective: get site stable and usable with essential bits in working order.
FLUID-1969 Fieldset for submit and delete buttons.
FLUID-1880 Large image upload error.
Can not fix. Appears to be a bug in Drupal 5, 6 and 7. Watching a patch. See comments in FLUID-1880 for more details.
FLUID-2086 Link text and title text should match.
FLUID-2099 A11y walkthrough.
Any other critical accessibility bugs raised from FLUID-2099 Filed into Jira. Nothing critical to be scheduled immediately.
Finalize community process, features, and begin work on it.
Jan 11 - Create a concrete draft of the proposed process and possible features.
Jan 12 / 13 - Prioritize issues in the draft.
Jan 12/13 to 16 - Revise then release draft to community for feedback.
Jan 19 - Revise draft based on community feedback.
Create Jira tasks.
Assign Jiras to individuals and iterations.
Jan 19 to Jan 21 (end of iteration24) - start planning work on community features (estimate resources).
Mid-Late January to Mid February 2009 (Design Iteration 24 to 27):
Polish existing patterns, create new patterns.
Work on Sakai and Fluid design patterns (while above development is still progressing).
Mid-Late January (Design Iteration 25 to 27):
With the site working and usable, may make sense to set up a more secure development environment:
FLUID-619 - Version control customized Drupal files
FLUID-591 - Routine backup of site databases into SVN. (dump to TXT and put into SVN).
Extended feature: Setup a dev site of Drupal (if time allows and easily + quickly done).
Continue development of workflow and community features.
FLUID-2140 - implement workflow
FLUID-2143 - sharing of content with other networks
FLUID-2144 - "stamping" of content as it progresses through workflow.
FLUID-2141 - invitation feature that integrates with workflow.
FLUID-2142 - notification system that integrates with email, workflow, and content posting
Improve the look and feel:
FLUID-1899 Modify the front page to emphasize the community process and pattern content.
FLUID-1904 - Put "Skip to Main Content" link in header (a11y)
FLUID-2096 - Card sort pattern categories and derive a new categorization for patterns.
FLUID-2133 - Combine OSDPL's 3 FAQs into a single link to improve navigation.
FLUID-2138 - Trim the left sidebar navigation. Too long to navigate and process (a11y concern).
FLUID-2149 - Look and feel of the comment system should be thoroughly tested and updated.
Improve the navigation of patterns
Other improvements:
FLUID-2074 - current pattern displays itself as a related pattern (makes for confusing cyclical navigation).
FLUID-2145 - Investigate and implement a module to flag comments and content for inappropriateness.
Early to Mid February 2009 (Design Iteration 26 to 27):
Increase community involvement.
with some community features in place, we can start bringing in more people to get involved. This will help inform any improvements to be made.
Re-engage existing partner communities: Sakai, uPortal, Moodle.
Engage new communities. Possibilities: Mozilla, Yahoo, Drupal.
Identify components within those communities that have followed a good pattern and create an OSDPL pattern based on that component
then, invite that community to comment and revise on the OSDPL
Adapt creative commons patterns from Yahoo and other CC sources