Sakai Email collaboration lists are being migrated from our Collab server (aka Mailman) to Apereo Google groups. Stay tuned to this page for updates.
|firstname.lastname@example.org||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.|
|email@example.com||For Sakai technical administration discussions.|
|firstname.lastname@example.org||The email list for the Sakai Project Management Committee. Oversight and planning group for the project.||All are welcome to subscribe.|
|email@example.com||An email group for our Spanish speaking community.|
|firstname.lastname@example.org||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
|email@example.com||Sakai infrastructure discussions.||There is an Apereo Infrastructure group, firstname.lastname@example.org , which handles most infrastructure questions. After the move to Apereo Google groups, any Sakai specific infrastructure questions may be directed to the Sakai Core team.|
|email@example.com||Anything goes.||Any discussion items that don't fit anywhere else, or any general conversation, goes here. We will move this to a firstname.lastname@example.org Google group.|
|email@example.com||Teaching and Learning discussions.||This is one of our most active groups. Any teaching and learning, or any questions about tool functionality can go here. This will be merged into the sakai-user group when we move this list to Apereo Google groups.|
|firstname.lastname@example.org||Sakai users.||Any questions about using Sakai at a functional level go here. Will be merged with the pedagogy group in Apereo Google groups.|
|email@example.com||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.|
|firstname.lastname@example.org||List for developers and others working actively on Sakai.|
|email@example.com||The Sakai QA testing list.|
|firstname.lastname@example.org||The Sakai Help documentation group.||This group is primarily focused on the development and maintenance of Sakai online help documentation, which is available on the web and as a context sensitive system within Sakai. This group is not technical, and only focuses on end user documentation.|
Those are all caused by their own accounts. Generally it's because they are a Google Apps school, and their institutional settings do not allow them to post via the web forum. They are still able to send email to the list, just not post via the web.