...
Fedora is designed, built, used, and supported by the community. An easy and important way that you can contribute to the effort is by helping resolve outstanding bugs. If you have an interest in gaining a better understanding of the Fedora code base, or a specific interest in any of these bugs, please add a comment to a ticket and we can work together to move your interest forward.
Software development
...
| title | Draft notes |
|---|
4.6.2 and 4.7.2
...
Releases
Earlier this month, two common Java library vulnerabilities surfaced:
- https://issues.apache.org/jira/browse/VELTOOLS-163
- https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-0114
Although related libraries have historically been included in Fedora's deployable artifacts, investigation confirmed that Fedora is not subject to the vulnerability; in fact, Fedora is not actually making use of the affected libraries. Because of this, and to eliminate any doubt of a potential vulnerability, the libraries have been removed from the codebase and a patch release has been issued to the 4.7 line and backported to the 4.6 line.
Release notes for Fedora 4.6.2 and 4.7.2 are available on the wiki.
...
Standards
Fedora API Specification
The Fedora community is working to establish a clearly defined specification for the core Fedora services. This specification details the exact services and interactions required for a server implementation to be verified as "doing Fedora".
Community members raised issues around implementing Batch Atomic Operations in a distributed architecture, leading to a decision to separate this element into its own specification document. We are also seeking further input on supporting different kinds of external content.
The draft specification has been published and is looking for community comments. Following this round of input, we plan on an initial release of the specification in the spring of 2017.
Fedora API Adopters Guide
An inaugural meeting for creating organized documentation targeting developers of applications and frameworks that currently interact with Fedora 4 was held on February 10.
As the formalization of the Fedora API Specification matures, it will be increasingly important for existing applications and frameworks over Fedora to adjust client/server interactions to the specification. The services defined in the Fedora API Specification are the same ones that are currently provided by Fedora 4, but the interaction models in some cases are changing to be more in line with broader standards. The effort of this group is to facilitate the adjustment of client-side tooling by detailing the "deltas" between the current Fedora 4 implementation and the emerging specification.
...
The Performance and Scale group met on February 20 to review outstanding issues related to the Fcrepo performance tool. The group plans to submit a grant proposal for AWS Cloud Credits for Research to secure resources for testing infrastructure. Tests are also being defined to address particular issues raised by the community, such as resources with many links to other repository resources, migrating large amounts of data from Fedora 3 to 4, and maintaining referential integrity within the repository.March 20
If you would like to participate in the Performance and Scale group please attend the next meeting on Monday, March 20.
...