Apereo OAE Phoenix is now available!

The Apereo Open Academic Environment (OAE) project team is pleased and excited to announce the first release of the Apereo Open Academic Environment; OAE Phoenix. This release consists of the first production ready release of Apereo OAE and focusses on providing support for various forms of academic collaboration.


Apereo OAE is designed as a multi-tenant platform that can be run at large scale, allowing for a single installation to support multiple institutions at the same time. OAE Phoenix is a first and important step and attempts to provide a basic, but solid foundation that can be used as the basis for many more collaborative scenarios.


We'd like to invite everyone interested in Apereo OAE to get involved during these early and exciting times and help drive contributions, adoption and direction.


Try it out

It is a project goal to make a community instance of Apereo OAE available for everyone to sign up to and play with or even use for real collaborations. We are currently targeting for this instance to be available by the fall, informed by the gathered production experiences.


In the meantime, OAE Phoenix can be seen and tested at http://oae.oae-qa0.oaeproject.org/, where anyone can sign on. Note: this environment is also used for QA purposes, and will be wiped and re-deployed every night, so no data retention and some downtime is expected.


The source code has been tagged with version number 0.2.0 can be downloaded from the following repositories:


Back-end: https://github.com/oaeproject/Hilary/tree/0.2.0

Front-end: https://github.com/oaeproject/3akai-ux/tree/0.2.0


Documentation on how to install the system can be found at https://github.com/oaeproject/Hilary/blob/master/README.md.


The repository containing all deployment scripts can be found at https://github.com/oaeproject/puppet-hilary.


Get in touch

The project website can be found at http://www.oaeproject.org. The project blog will be updated with the latest project news from time to time, and can be found at http://www.oaeproject.org/blog.


The mailing list used for Apereo OAE is oae-dev@collab.sakaiproject.org. You can subscribe to the mailing list at http://collab.sakaiproject.org/mailman/listinfo/oae-dev.


Bugs and other issues can be reported in our issue tracker at https://github.com/oaeproject/3akai-ux/issues.


Thanks to ...

The release of OAE Phoenix wouldn't have been possible without the support and hard work of a number of exceptional institutions and individuals.


We'd like to thank the following institutions for supporting, funding and driving the design and development of Apereo OAE, and in particular the people that have put a lot of time and effort into driving this forward at their respective institutions:

  • University of Cambridge - John Norman
  • Georgia Institute of Technology - Clay Fenlason
  • Marist College - Josh Baron

A massive thanks goes to the project team, which has gone above and beyond the call of duty to design and develop the solid foundation that OAE Phoenix represents:

  • Bert Pareyn (UI development)
  • Branden Visser (back-end development)
  • Sam Peck (design)
  • Simon Gaeremynck (back-end development)
  • Stuart Freeman (development and integration)

We would also like to thank the people that have provided code contributions and translations:

  • Frederic Dooremont (French translation)
  • Yildiray Ogurol (German translation)
  • Samuel Gutiérrez Jiménez-Peña (Spanish translation)
  • Toni Devís López (Valencian, Spanish and Italian translation)
  • Mark Breuker (Dutch translation)
  • Tim De Groote (Widget development and bug fixes)
  • Mathieu Decoene (Mobile UI)
  • Dieter Casier (oEmbed)
  • Yeng Qi Chao (Bug fixes)

Last but not least, a special thanks also goes to Lucy Appert (NYU) and David Goodrum (Indiana University) for their leadership in the early days of the project and the breadth of knowledge and insights they have brought to the design process.


Obviously, it is not possible to list all of the individuals that have made this possible, so we'd like to thank everyone else who contributed to this exciting milestone ...


What's next

We will follow up with a more detailed report of the OAE Phoenix features, capabilities and performance characteristics.