You are here

Block title
Block content

Engineering Punchlist

By Dan Davis, Fedora Commons Chief Architect
The Fedora Commons engineering team has been hard at work preparing for both the Fedora 3.0 Beta 2 release in mid-March, and a maintenance release for Fedora 2.2.2 in early March. The team released Fedora 3.0 Beta 1 on December 21, 2007 introducing the first version of the Content Model Architecture (CMA). In many ways, the CMA will form the over-arching conceptual framework for future development of the Fedora Repository. Feedback from Beta 1 testers into Beta 2 is currently being incorporated, both for CMA and the other features introduced in the Beta release. Many thanks to the community for participating in testing.
An important new interface, the Fedora REST API, was incorporated as an experimental feature for Beta 1. Contributed by MediaShelf, the Fedora REST API will make it simpler for programmers who just want to use Web interfaces and languages like Ruby to build applications with Fedora. Please provide feedback on this experimental API to ensure that it has the right features before it becomes a Fedora Repository feature.
We have started a new project called Akubra with our Topaz teammates. The goal of Akubra is to provide a storage plug-in that supports transactions on common file systems plus the ability to provide a way to support multiple customized storage options at the same time. Starting Akubra was a result of realizing that a common need was found across multiple projects and working together was the best way to add to Fedora Common’s set of reusable components.
Fedora 3.0 Beta 2 introduces support for the Java Messaging System (JMS). The Fedora Repository will act as a publisher of API-M events using GSearch as the first message subscriber. Over time more features that enable Fedora to fit into large-scale enterprise installations while still supporting the rapid development of simple Web applications will be added. Keep in touch through the Fedora Commons users list at