This project plan is a living document and is reviewed and updated regularly in order to accurately reflect the community's state of progress.
This page provides an at-a-glance view of the current activities and goals of the Fluid Project. We are currently working on Fluid Infusion 1.0 and beginning work on Fluid Engage.
Fluid's release plans reflect a layered approach; the core framework team breaks work up into regular iterations, usually two weeks in length, to ensure our progress is visible to the entire community and to better respond to the needs of our user experience stakeholders. Packaged, documented versions of the software are released quarterly.
We try to keep our planning process as light and simple as possible, recognizing that priorities and tasks shift over time, and that we'd prefer to spend our working on great designs. The Fluid team has three levels of plans:
More information on Fluid's planning process.
The approach we've taken to prioritizing which components we work on and when is based on combining known issues in Sakai, uPortal, and OpenCollection with ongoing user research and a strategic direction towards re-envisioning how content is managed in both applications. We will continue to collect suggestions for components from stakeholders and experts in the communities. Early prioritization of these suggestions will be based on educated guesses and identifying clearly problematic yet manageable areas to improve. As progress is made on the UX Walkthroughs, usability studies, and user research, our priorities will be driven by the results of this research. We'll also make some key component choices based on the desire to address critical accessibility customizations and accommodations where necessary, allowing us to explore runtime adaptations of the user interface.
The Fluid technologies will be closely integrated into essential aspects of the Sakai, uPortal, and OpenCollection applications. We will work closely with existing teams and project stakeholders to do this in a highly collaborative, community-led manner. While the details may shift based on the need to responsively target high priority problems, we expect to see Fluid's largest impacts in the following areas:
---------------------------------------------------------
This is a map that was presented at the Fluid Monthly Teleconference September 3, 2008 to demonstrate upcoming work, community participation, and how our work tied in with the larger project goals. It is a snapshot of those details from that moment in the project.