The document discusses the future of Sakai 3, emphasizing the need for new technologies, improved functionality, and a unified content repository to enhance user experience and academic workflows. It highlights the importance of community involvement in developing and promoting Sakai 3, while also addressing ongoing support for Sakai 2. The need for balanced resource allocation between maintaining Sakai 2 and advancing Sakai 3 is critically noted, alongside the urgency of transitioning to accommodate evolving user expectations.

1. Sakai EuropeMichael KorcuskaExecutive DirectorSakai Foundation(for a bit longer)(Still)

2. OutlineLooking forwardSakai 3My advice toSakaiSakai in Europe

3. The Future: Sakai 3

4. Sakai 3: Why?Changing expectationsGoogle docs/apps, Social Networking, Web 2.0Success of project sites = Sakai beyond coursesNew technologiesStandards-based, open source projectsJCR (Jackrabbit)Open Social (Shindig)Client-side programmingJavaScript/AJAXFluid Project (fluidproject.org)Years of hard-won knowledge4

5. And so…Proto by Hubert StoffelsThe time to repair the roof is when the sun is shining.John F. Kennedy

6. What?Photos by Hobvias Sudoneighm, Massimo Valiani, and Mathieu PlourdeFunctionality & User ExperienceTechnology and Developer ExperienceCommunity Practices and Culture

7. End User perspectiveSakai 3

8. Content Organization, Searching & TaggingSakai 3 Themes8Learning Space ConstructionBreaking the Site BoundaryCustomizable Workflows (No Tool Silos)Academic NetworkingThe unSakaiOpen Teaching

9. Learning Space Construction1Photos by Cyprien LomasReally “Scholarly Space”Teaching & Learning plus….Research, collaboration and portfoliosPrinciplesEveryone creates contentSimple integration of interactive optionsAuthor(s) control presentation and workflow

10. Academic Spaces: Building BlocksSimple Content Authoring:Easy page creation (wiki-like)WYSIWYG EditingTemplates (page and site)VersioningEnhanced with Academic FunctionalityInteractive Widgets (e.g. assignments & feedback)Allows integration of content and activities10

11. TemplatesTemplates provide scaffolding for majority of usersBut can be bypassed for advanced needsPage TemplatesSections with (editable) contentSite TemplatesPredefined pages and dashboards

12. Everything is Content Not just files to shareClassic “resources” tool in Sakai (of course)Discussion post, user profile, test questionsTaggable, searchable, linkable, portable, shareableUnified content repositoryContent not tied to siteEverything in one storage areaBUT: Sakai is not a full Content Management SystemNo complex approval workflowsNo fancy layout capabilitiesEveryone is an author in Sakai122

13. Content ManagementSakai2Photo by Desirée DelgadoSite ASite BUsers find things by remembering what site they were in when they saw it.13

14. Content ManagementSakai3Photo by Amy VeeningaTags: System, Organizational & UserPermissions: Who has access, under what conditionsSmart FoldersSearch14

15. Workflow & Architecture155KernelToolKernelServiceToolToolServiceServiceKernelServiceServiceToolToolServiceToolFacilitates independent tool development

16. Resists intuitive workflows

17. Contributes to inconsistent user experienceWorkflow & Architecture16KernelWorkflowKernelServiceWorkflowWorkflowServiceServiceKernelServiceServiceWorkflowWorkflowServiceServices need to respond to more customers

18. UX oversight is more complicated

19. Workflows built across services

20. Encourages presentation & service separationWorkflow

21. Academic WorkflowBeyond Tool SilosAcademic work flows often cross tool boundariesAnything can be graded!Anything can be discussed!This exists in Sakai 2But it is too difficult and more needs to be doneExample: Instructor puts into syllabus an assignment to create a discussionpost that will be graded.4 tools for both instructors and students!17Photo by Zoom Zoom

22. The unSakai18KernelServiceServiceServiceiGoogleFacebookKernelServiceServiceServiceDocumented data feeds allow Sakai to appear anywhereMobile AppsWindows/Mac Widgets

23. Sakai 3 Functional ArchitecturePublicUsersGroupsCollaboration SpacesPersonal SpacesPLELearningResearchProjectPortfolioProfileMeaningful ArrangementsDynamic, Collaborative PagesDashboardsDefined & Custom WorkflowsFundamental CapabilitiesWiki-like Content EditingPage TemplatesInteractive WidgetsUnified Content RepositoryAuthored PagesMediaUploaded FilesContextual Content

24. Sakai 3 TechnologyWhy Sakai 3?

25. Using Open SourceDon’t write our own codeIf we can help itCriteria:FunctionalityLicense-compatible open sourceOpen standardApproachable community

26. Sakai and ApacheSakai 3 Kernel built on Apache SlingRESTful web development framework for content managementSling incorporates Jackrabbit and FelixEverything as contentDiscussion post, User profile information, etc.Components put Content into JCR Content storeSakai Kernel creates relational indices in DBComponent doesn’t need to do anythingAutomatic tracking of most events by kernel22

27. Community Practices

28. Community PracticesFunctional LeadershipDesign FirstMinimize Technology FrameworksQuality FocusedUnit (and other) TestsInternationalization & Accessibility

29. Timelines

30. What I hearSakai 3 needs to go faster. Why aren’t more people working on it?We’re getting pressure to switch to MoodleIt’s too hard to maintain/developWe’re in no hurry but are looking forward to Sakai 3Too much emphasis is being placed on Sakai 3. We need to work harder on Sakai 2

31. Why Sakai 3 is CriticalSooner or later your users will want moreSubstantial growth in the community will require something differentThe vision of a platform for local innovation requires different technologySakai 3: It is not a question “if”, but “when?” and “how?”

32. Balance of ResourcesMaintenance of Sakai 2?Minor features for Sakai 2?Major new features for Sakai 2?Sakai 3?The difficult question is feature development. Maintenance of Sakai 2 must continue. But the majority of new feature effort must move to Sakai 3 “soon”

33. My View2.8 is likely and importantGoogle integrationGradebook 2Assignments 2No 2.9!New tools/features built on Sakai 3Evolution of Sakai 2 tools as “independent release” on top of 2.8 core services

34. Timelines3020092010201120122013Sakai 2.5Sakai 2.6Sakai 2.7HybridModeSakai 3.0Official ReleasesPreviewsSakai 2.8

35. PlanSeveral institutions are begging to assemble a coordinated teamIncludes existing Sakai users and new UniversitiesCentralized project managementGoal:Basic hybrid version by JulyA usable release by March 2011Perhaps this is Sakai 3.0?Specialized tools still come from Sakai 2

36. Sakai 3 and Sakai EuropeGet involvedImmediate: Localizing SakaiSakai 3 team needs feedback on I18nYou know what happens if you leave this to the Anglo-Saxons.For Denver: Get organizedFind a way to provide resources to the projectRequirements, design, development, testing

37. Parting WordsAdvice for the Sakai Community

38. What the community needs to doDon’t wait for the Sakai FoundationLeadership needs to come from the communityThe Board does not control the productInvest in Sakai 3Sakai 2 works wellBut will not deliver the long-term vision