...
- Sakai will exploit the concept of restful data apis to the full in order to support unanticipated mashups of information, ease of development for new UI functionality, and familiar technologies for design oriented developers.
- A published widget SDK which will ultimately aim to support lightweight component development by those not intimately acquainted with Sakai development, including instructors and students.
- Sakai will use industry-tested and supported back-end platforms that implement open standards, such as Sling (Jackrabbit JCR and Felix OSGi) and ActiveMQ (JMS) in order to provide a robust, scalable and maintainable core.
Q1: July to September 2010 - Academic Networking and Collaboration
The first development cycle is intended to provide the basic collaboration and content capabilities that will form the bedrock of Sakai 3. It will support general collaboration use cases that can be useful in a wide range of academic activities but will not include teaching-specific capabilities. At the end of this stage it should be possible to deploy a functioning system that supports basic people and group management, basic resource management, basic site management and basic person to person contact management and communication. It should also be possible to demonstrate the effectiveness of the hybrid approach to transition. A significant amount of time will be spent at the beginning of this stage to secure funding and recruit resources, and to set up the development process including the new design process under discussion.
...
1.10 Foundational global Sakai 3 capabilities:
A number of global capabilities will be created for the first release. Many of these are content-related, including searching, tagging, sharing, RSS syndication, etc., but also include miscellaneous global considerations such as page permissions and accessibility.
Q2: October to December 2010 - Experiencing Collaboration and Learning
...
The second development cycle will provide the foundation for more tailored, academic-specific activities and workflows such as homework submission. It will be suitable for web-enhancing classes but not for classes that require more advanced teaching-specific capabilities such as online testing. The cycle will also include further development of Sakai 2/Sakai 3 hybrid mode as well as initial work on accessibility and internationalization. At the end of this stage, it should be possible to pilot the simple learning environment. Requirements may need to be tuned if other institutions plan to go ahead with deployment of the SLE in early 2011.
...
2.10 Complete hybrid mode that includes items such as sharing data between Sakai 2 and Sakai 3 tools, deep linking Sakai 2 tool items on a Sakai 3 page, and searching and getting results from across both Sakai 2 and Sakai 3 (complete definition TBD).
Q3: January to March 2011 - Management of Collaboration and Learning
...
the third development cycle will layer on basic group coordination, learning management, and system administration capabilities. It should be suitable for use in some blended or fully online courses as well as research and administration collaboration that require more coordination among members. It should also be possible for adopters to run Sakai 3 as the primary LMS interface of a Sakai 2/Sakai 3 hybrid installation. Capabilities will include calendar and event integration, goals and rubrics and rich structured pages for scaffolded authoring (such as syllabus creation or portfolio development). Administration capabilities, including prototyping of multitenancy, will also be featured in this release. Finally, early developer-oriented documentation and contribution policies will be developed. At the end of this stage we should have the outline of a credible Sakai 3 offering, albeit with heavy reliance on hybrid operation. During this stage we would also develop policies around the testing and acceptance of widgets developed outside the directed project work using the widget SDK.
...
3.13 Widget SDK beta, with feedback from pilot developers
Q4: March to June 2011 - Integration and Enhanced Collaboration
The fourth development cycle will focus on integration (especially standards-based integration) and making Sakai 3 more approachable for developers outside of the core team. It should be suitable as a full LMS replacement for some institutions, depending on their needs and priorities. Highlights include support for integration standards such as LTI and Common Cartridge, richer templates and workflows for teaching-specific functionality such as assessment and learning activity sequencing, enhanced social networking, and mobile capabilities. Here areas of work are less specific due to higher uncertainty on progress in the previous cycles. Depending on successful delivery of the requirements for stages 1-3 and involvement of additional resources, significant progress towards more widgets to replace Sakai 2 tools and incorporate them into the tracking, grading, commenting infrastructure should be possible.
...