This is the March 2016 edition of the Fedora Newsletter. This newsletter summarizes the most significant activities within the Fedora community over the last month.
Call for Action
Fedora is designed, built, used, and supported by the community. Here is an easy and important way that you can contribute to the effort:
- Add a comment to any of these tickets  if you are interested in inching into Fedora development.
Fedora API Specification
The Fedora community is working to establish a clearly defined specification for the core Fedora services. This specification will detail the exact services and interactions required for a server implementation to be verified as "doing Fedora".
The primary benefits of this specification include:
- Concrete and common understanding of Fedora's role in an institution's infrastructure ecosystem
- Stable, independently versioned Fedora RESTful API
- Opportunity for alternate Fedora implementations to support different use cases
Alternate Database Support
By default, Fedora 4 is configured to store metadata in LevelDB; however, this can be changed via Infinispan configuration. The next official release of Fedora 4 will include configuration options for alternate databases: MySQL and PostgreSQL. You can review some performance comparisons  between the different database options in the latest documentation.
API Extension Architecture
API-X stakeholders have created two proof-of-concept (POC) implementations to illustrate the API-X framework: a PHP POC  that demonstrates validation, and a wireframe POC  that demonstrates service discovery, binding, and proxying using Camel. These POCs, along with workflow diagrams, were discussed during the last meeting .
If you are interested in the API Extension Architecture, please join the discussion on the fedora-community mailing list  and attend the next meeting on March 4.
Performance and Scalability
A JMeter test has been added to create test data on-the-fly and upload binary files. Several stakeholders have access to large memory machines that can be used for testing. More tests will be added and run over the next few weeks.
Conferences and events
The next Code4Lib conference  will take place in Philadelphia, PA on March 7-10. The event will feature a Fedora 4 workshop  led by Andrew Woods, a Fedora 3 to 4 migration workshop  for Hydra users led by Ben Armintor and Andrew Woods.
LDCX  will take place in Stanford, CA on March 21-23. The objective of the gathering is to bring together institutions and developers with shared needs, and assemble around a shared set of solutions and technical components. With technology contributions from peer institutions, shared products for digital cultural heritage offer the critical building blocks for a complete suite of solutions -- from digitization workflow to digital asset management, from preservation to discovery and delivery.
Major topics at LDCX will be image interoperability and IIIF, Hydra technical architecture, Fedora 4 and linked data (e.g., PCDM), discovery and exhibits (e.g., Blacklight, Spotlight), DevOps practices, and "Geo" for cultural heritage.
West Coast Fedora Camp
The West Coast Fedora Camp , hosted by the Caltech Library, will take place April 11-13 in Pasadena, CA. It is based on the inaugural Fedora Camp  that was held at Duke University in November. Training will begin with the basics and build toward more advanced concepts–no prior Fedora 4 experience is required. Participants can expect to come away with a deep dive Fedora 4 learning experience coupled with multiple opportunities for applying hands-on techniques working with experienced trainers and Fedora gurus. There are only a couple seats left so register now  to secure your place!