This is the source code for the Sakai CLE.
To build Sakai you need Java 1.8 and Maven 3.2. Once you have clone a copy of this repository you can build it by running:
mvn install
Sakai runs on Apache Tomcat 8. Download the latest version from http://tomcat.apache.org and extract the archive. Note: Sakai does not work with Tomcat installed via a package from apt-get, yum or other package managers.
You must configure Tomcat according to the instructions on this page: https://confluence.sakaiproject.org/pages/viewpage.action?pageId=75667828
When you are done, deploy Sakai to Tomcat:
mvn clean install sakai:deploy -Dmaven.tomcat.home=/path/to/your/tomcat
Now start Tomcat:
cd /path/to/your/tomcat/bin
./startup.sh && tail -f ../logs.catalina.out
Once Sakai has started up (it usually takes around 30 seconds), open your browser and navigate to http://localhost:8080/portal
Sakai is licensed under the Educational Community License version 2.0
Sakai is an Apereo Foundation project and follows the Foundation's guidelines and requirements for Contributor License Agreements.
See our dedicated page for more information on contributing to Sakai.
For filing bugs against Sakai please use our Jira instance: https://jira.sakaiproject.org/
For testing out the latest builds go to the nightly server page
If you have any questions, please join the Sakai developer mailing list: To subscribe send an email to [email protected]
To see a full list of Sakai email lists and the status of the migration to Apereo Google Groups check out this Sakai wiki page: https://confluence.sakaiproject.org/display/PMC/Sakai+email+lists
If you want more immediate response during M-F typical business hours you could try our Slack channels.
https://apereo.slack.com/signup
If you can't find your "at institution.edu" on the Apereo signup page then send an email requesting access for yourself and your institution either to [email protected] or [email protected] .
Sakai 10 is the recommended version for production use.
Sakai 2.9 is still supported, almost solely for security patches at this point in time.
[Sakai 11] (https://docs.google.com/presentation/d/1OaF04Kli51nYtsLw_0plmU829NarYUDtQkBnFJtB250/edit#slide=id.p4) is under development. Expected release is first half of 2016. Some of the key features include Responsive Design (code name Morpheus); spreadsheet entry Gradebook; improved Assessment (test and quizzes) delivery options to accommodate special needs; PA system for managing system-wide announcements; user interface enhancements to Lessons, a community favorite tool that allows instructors to organize their course activities the way they would like, by leveraging other Sakai tools and adding workflow and adaptive release options.
[The Sakai Accessibility Working Group] (https://confluence.sakaiproject.org/display/2ACC/Accessibility+Working+Group) is responsible for ensuring that the Sakai framework and its tools are accessible to persons with disabilities. [The Sakai Ra11y plan] (https://confluence.sakaiproject.org/display/2ACC/rA11y+Plan) is working towards a VPAT and/or a WCAG2 certification.
CKSource has created a GPL licensed open source version of their [Accessibility Checker] (https://cksource.com/ckeditor/services#accessibility-checker) that lets you inspect the accessibility level of content created in CKEditor and immediately solve any accessibility issues that are found. CK Editor is the open source rich text editor used throughout Sakai. Whlie the Accessibility Checker, due to the GPL license, can not be bundled with Sakai, it can be used with Sakai and the A11y group has created [instructions] (https://confluence.sakaiproject.org/display/2ACC/CKEditor+Accessibility+Checker) to help you.
A number of institutions have written additional tools for Sakai that they use in their local installations, but are not yet in an official release of Sakai. These are being collected at https://github.com/sakaicontrib where you will find information about each one. You might find just the thing you are after!