Project Coordination Update Sakai 2.3 and Beyond Peter A. Knoop Sakai Project Coordinator

Project Coordination UpdateProject Coordination Update Sakai 2.3 and Beyond Sakai 2.3 and Beyond

Peter A. KnoopSakai Project Coordinator

06-Dec-2006 6th Sakai Conference, Atlanta 2

Role of Project Coordinatorhttp://bugs.sakaiproject.org/confluence/display/MGT/Sakai+Projects+Coordinator+-+Position+Description

• Chuck’s Org chart– Project Coordinator – Me, face-in to designers and developers– Community Liaison - Anthony Whyte, face-out to representatives– Requirements - Mark Norton, face-out to community

• Track and report to the Sakai Community on the activities of the Community– Maintain the Sakai Project Coordination Summary– Update the Sakai Community at Conferences on community

activities

• Help bring parties with common interests together; match resources and requirements.


Sakai Community• Project Teams – 119 Committers• Community resources for the Community

– Collab – Virginia Tech– Jira/Confluence – University of Arizona– SVN – Indiana– Sakaiproject.org – University of Michigan– QA Servers – Indiana, Columbia, Amsterdam,

Cambridge, Boston, Cape Town, rSmart– Working Groups, Discussion Groups – many

• Always need more volunteers…• Production/Pilot/Demo Sites – 150-200+


Sakai Map


Sakai in Production

Text


Sakai 2.3 Highlightshttp://source.sakaiproject.org/release/2.3.0/release-notes.html

• Released November 2nd, 2006– Slowed down release cycle– May release for August/September use and Nov

release for early adopters

• 114 Enhancements/Tasks• 491 Bug Fixes• Promoted Tools – Wiki, Calendar Summary• New Provisional – Blog, LinkTool, Podcasts


Tool Enhancements

• Assignments -- link to previously-created gradebook items

• Gradebook -- selective release and import• Message Center -- option of a threaded view• Resources -- timed release and custom ordering• RWiki -- now includes commenting and RSS

notifications


More Tool Highlights…

• Roster -- new API for managing privacy • Tests & Quizzes (Samigo)

– attach any file to a question– bulk downloading of uploaded file answers – filtered views for grading– a pager/search box for grading– a new question type: numeric response– java.policy requirement for audio recording

questions removed


General Highlights• Limited API Changes – compared to past• Preserve Tool State – configuration property• Accessibility

– Site navigation and tool titles are now contained in the main document, which eliminates several iFrames, makes navigation more seamless

– Repaired bug with Help opening on tab– Accesskeys revised to reflect UK eCommerce standards

• CSS Changes– Site navigation and tool title content; same look, better behavior– Eases display resolution testing

• Portal– Left-hand buttons are now permissions-based– Enable more than one security function; implied AND


• Deep link URLs through Charon into tools• Course Management API – Test with it now,

tools coming in 2.4• Basic Authentication – any portal or access

servlet URL• Re-factored Import – limited support for IMS

Common Cartridge packages (moving target)• Partial Swedish translation

More General Highlights


Sakai 2.3 New Core Tools

• Promoted to Core Status– Wiki– Calendar Summary


Sakai 2.3: Wiki


Sakai 2.3: Calendar Summary


Sakai 2.3 New Provisional Tools

• Promoted Provisional Status– Podcasts– LinkTool– Blog


2.3 Provisional: Podcasts


2.3 Provisional: LinkTool


2.3 Provisional: Blog


~2.3 Contrib Projects• Page Order Helper – Joshua Ryan (ASU)• Mailtool – (BU, others)• Sakaibrary – (Indiana,U-M)• Config Viewer – Anthony Atkins (VT)• SiteStats – (Portugal)• Usermembership – (Portugal)• Evaluation System – (Virginia Tech, U-M)• Reset Password – (Cape Town)• Poll – (Cape Town)• ImageQuiz – Stephen Githens, U-M


Contrib: Page Order Helper


Contrib: Mailtool


Contrib: Sakaibrary


Contrib: ConfigViewer


Contrib: SiteStats


Contrib: UserMembership


Contrib: Eval System


Contrib: Reset Password


Contrib: Poll


Looking Ahead…

• Near-term – Sakai 2.4 – 3 months– Freeze 15-Mar-2007 / Release 01-May-2007

• Long-term – Sakai 2.5 – 9 months– Freeze 15-Sep-2007 / Release 01-Nov-2007

• Out-there – Sakai 2.6/3.0? – 15 months– Freeze 15-May-2008 / Release 01-May-2008


Sakai 2.4• Most sites will be running 2.4 Aug/Sep 2007

– May release is the “one” for most folks– November is mostly for folks living on the cutting edge

• Project Coordination Meeting (post-conference)– Solidify plans for 2.4; Preliminary discussions of 2.5

and beyond– Natural evolution of “Integration week” – getting too

complex to do it in one week; more lead time, discuss more than just the next release

– Schedule prior to conference to report out more appropriately


Preliminary Plans: Sakai 2.4 & Beyond

• JSR 168• TransformAble• CourseManagemetn-related tool changes• “Modular” Sakai release• Discussion/JForum/Message Center• TurnItIn• Forgot Password• ECL 2.0 and Licensing Compliance• and so on…


Project Teams: Best Practices• Different maturity levels for Project Teams• Mature projects can focus more on community-

driven needs (e.g., Resources)– Requirements as a route to increasing involvement– More than just development resources (UI, QA)

• Broad appeal attracts more resources (e.g., OSP, Samigo – Tests & Quizzes)– Evolving project team; new long-term resources from

the community participating– Needed help on specific tasks, approach community

with help of Foundation


Targeted Development• Focused on specific tasks; not open-ended,

general things• Foundation can be agile and share risk on behalf

of community• Software at risk to community, so foundation

steps up for community to help project teams for short-term on finite set of issues

• In the end reverts back to project team; however, hopefully pick up a more, well-trained, resources along the way…


Tests & Quizzes -- Samigo• Identify need and call out to community• Those helping Stanford out:

– Unicon – scripting (JMeter), testing, reporting– U-M – Glenn Golden– eTudes/Rutgers – beta testers, time and people– $ CSU, UC-Davis (?), eTudes, Rutgers (?)

• Approximate Timeline– Pre-Sakai 2.4 Help– Call out early November with commitment by 10-Nov-2006– Mid-December testing starts at eTudes– January production @ eTudes– Rutgers testing later on as time permits


Where to go for Information?

• Too many places to go! – Website (sakaiproject.org)– Collab (collab.sakaiproject.org)– Confluence– Jira

• Can’t always tell what is current…• Making it easier to find what you need

– Website BOF– Documentation BOF


Keep Track of What’s Going On?

• Summary– Management Confluence space

• Project level– Project’s Confluence space and Collab site– Jira – Filters, Subscriptions– SVN – Collab “Software” site

• Production and Pilot sites– Make sure your information is posted (and

kept up-to-date); security announcements


http://bugs.sakaiproject.org/confluence/display/MGT

http://bugs.sakaiproject.org/confluence/display/MGT/







• Sakai Installations (DG: Production)– Make sure your information is posted (and



http://bugs.sakaiproject.org/confluence/display/PROD/Implementations





• Sakai Installations (DG: Production)– Make sure your information is posted (and



http://bugs.sakaiproject.org/jira/secure/Dashboard.jspa


Roadmaps

• Snapshot Roadmap – “Sakai 2.4 Plans” in Summary Table– Difficulties gathering information from teams

that need to be heads-down and fighting fires– As project teams evolve and expand, more

resources join, someone has the time to disseminate information more often

• Jira Roadmap – too detailed for most• Roadmap BOF


Useful places to start…• START HERE (Volunteers?)

– Role provides path to information• Discussion Groups (email-lists on Collab)

– DG: Development (very high-traffic) – design and development discussions; and most everything else right now.

– DG: Announcements (low-traffic)– Open Fourm– Role-based, e.g., Pedagogy, User, Research, Librarian (low to

no traffic) – need volunteers to help direct and motivate • Lots of interesting WGs (spaces on Confluence)• Project Teams

– Reorganized in 2.2 to support distribution of work creation; able to do stuff in parallel now, in particular framework-related


Volunteer!

• Entry-level requirements vary significantly

• Project Teams– Maturing Teams– SVN modules

• Discussion Groups

• Working Groups– Website re-design BOF– Documentation BOF


What to See in Atlanta?

• Ian Boston – Sakai Architecture Update– Thursday, 1:15 – 2:45 pm– International 2

• Tool Carousels & Technical Demos

• Ask your peers for guidance and suggestions…

Documents

Project Coordination Update Sakai 2.3 and Beyond Peter A. Knoop Sakai Project Coordinator