Sakai Foundation

Release Date: 29 January 2010

The Sakai Foundation is pleased to announce the latest maintenance release for Sakai 2.6.x and 2.5.x.

-----------------------------
The Sakai 2.6.2 maintenance release provides a set of bug fixes that improve upon the Sakai 2.6.1 release. Over 80 issues have been addressed by 2.6.2.

November - The Sakai CLE 2.9.0 contains significant performance improvements, updated technical infrastructure, hundreds of bug fixes (over 500 bug fixes and over 20 security improvements), and it sports a new, updated look and feel, including smoother navigation, with a new neo-portal skin. Significant features have been added to the Resources, Gradebook, and Section Info tools in core Sakai. Major additions and improvements have been made to the “Indies,” including Lessons, which is now turned on by default, Samigo Test & Quizzes, Profile 2, Forums and Messages.

The proposal to develop a mobilized Sakai is now an official project of the Sakai Foundation. A steering committee made up of representatives from the University of Florida, Leaning Forward Technology LLC, University of Notre Dame, the University of North Carolina Chapel Hill, and Oxford University will provide oversight for the project. 

With funding provided by the University of Florida, the mobile project targets four goals:

The membership of Jasig and Sakai, pioneers in the development and adoption of open source software to support education, have voted overwhelmingly to merge their two organizations. The new non-profit entity formed by the merger, Apereo, will continue to foster the creation and sustenance of open source software in support of education and research - but with a significantly enlarged membership and reach.

October 2012 

Introduction

This Memorandum of Understanding describes the relationship between the ESUP-Portail consortium, Jasig, the Sakai Foundation, and their successors. It represents a reciprocal agreement between equal partners, and has the primary aim, over time, of developing a closer practical working relationship between the signatory organisations.

Principles

The relationship the signatories seek to build focuses around the development of shared -

October 19, 2012 - The Sakai Foundation is pleased to announce the results of the search for a new Foundation Treasurer. Charles F. Leonhardt, Chief Technology Officer at Georgetown University, was appointed to the position at the October meeting of the Foundation Board. The Foundation Treasurer plays a critical role both in monitoring financial performance, and informing strategic priorities.

Early this year, Jasig, the parent organization for uPortal, CAS, Bedework and other open source software serving higher education, and the Sakai Foundation, which supports the Sakai Collaboration and Learning Environment, formed Board-level groups to examine ways the two organizations could collaborate more closely. These Strategic Alliance Committees, led by Jasig Chair Aaron Godert, and Sakai Foundation Chair Josh Baron, met in New York in September to consolidate the outcomes of their discussions and bring proposals to their respective Boards.

I am very pleased to announce that Alan Marks will join the Sakai Foundation staff as project director for the Sakai 3 project. Alan’s hire is an important milestone for the project and for our community.

Alliance to Support Exceptional Technology-Enhanced Teaching and Learning

Richmond, Virginia, U.S. – June 9, 2010 – SoftChalk, LLC, a leading developer of content authoring software for eLearning, and the Sakai Project, an educational community renowned for innovation in open teaching, learning and research software, today announced an integration and collaboration partnership. SoftChalk has become a member of the Sakai Foundation and introduced integration between the SoftChalk authoring solution and the Sakai Learning Management System.

Economies of scale was a critical reason to start the Sakai project. Several universities working together on software development could produce a final product much less expensively than each of us working on our own. (And, of course, build the software we wanted to use.) Because we could eliminate redundancy, aggregate costs would be lower, and the cost to each university would also be lower. This equation paid off for Stanford. We developed about 20% of the original Sakai code base, which meant that we received 80% of the product in return.