Sakai Email collaboration lists are being migrated from our Collab server (aka Mailman) to Apereo Google groups. Stay tuned to this page for updates.
|Developersemail@example.com||Our largest and most active group. Intended for technical and software development discussions||Prefix the email subject as [a11y] for Accessibility issues, [i18n] for Internationalization and Translation issues, [portal] for responsive design, inlining, and portal issues, and [contrib] for contrib tool questions, like Evaluation and Gradebook2.|
|Production - System Admins and DBAsfirstname.lastname@example.org||For Sakai technical administration discussions.|
|Users - Teaching and Learning, plus Research and other users of the email@example.com||For users of the system including teaching, learning, research and more. Tends to focus on functional aspects of using Sakai.|
|QA firstname.lastname@example.org||For our QA testing community. Often emails sent to the QA testing community are also sent to the Development list, sakai-dev.|
|Help Documentationemail@example.com||This group works on keeping the Sakai online help documentation up to date.|
|Sakai Core Teamfirstname.lastname@example.org||The Sakai core team. This is the main group of "doers" in the Sakai Community. Developers who actively contribute code to Sakai. QA testers sometimes join in to ask questions of the Core team. The group is open to all.|
|Sakai PMC (Project Management Committee)||email@example.com||The email list for the Sakai Project Management Committee. Oversight and planning group for the project.||All are welcome to subscribe.|
|Sakai Spanish Communityfirstname.lastname@example.org||An email group for our Spanish speaking community.|
|Apereo Licensing Groupemail@example.com||The Apereo Licensing group handles processing of all licensing agreements and fields licensing questions, for Sakai and all other Apereo projects.|
Lists still using Collab
|firstname.lastname@example.org||Anything goes.||Any discussion items that don't fit anywhere else, or any general conversation, goes here. We will move this to a email@example.com Google group.|
|firstname.lastname@example.org||Portfolio project.||The portfolio project continues to evolve. OSP was the open source portfolio system in Sakai through Sakai 10. Karuta is now it's own separate open source project under Apereo, using IMS LTI for integration with Sakai and other systems.|
If you are part of an institution that uses Google Apps, and your institutional settings do not allow them to post via the web forum, you are able to send email to the list, just not post via the web.