...
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.If you would like to participate in the Performance and Scale group please attend the next meeting on Monday, March 20. March 20 and discussed progress on the "many members" performance issue, which affects retrieval times for resources with a large number of members. Danny Bernstein pursued a number of optimization strategies and found that a combination of parallel processing streams and increasing the size of the ModeShape cache produced significant performance gains of 5-8x.
Conferences and events
In an attempt to simplify the task of keeping up with Fedora-related meetings and events, a Fedora calendar is available to the community as HTML and iCal .
Upcoming Events
CNI Spring Meeting and DuraSpace Summit
...
IFLA International News Media Conference
Hydra Camp
Islandora Conference
Previous Events
Code4Lib
The annual Code4Lib conferenceFrom printed newspapers to born-digital news, libraries and other cultural heritage institutions have a central role in ensuring future access to news content. The IFLA News Media Conference, which takes place March 6April 27-9 28 in Los AngelesReykjavík, CA, is an annual gathering of technologists from around the world, who largely work for and with libraries, archives, and museums and have a commitment to open technologiesIceland, will examine issues and challenges in collecting and preserving the news and making it available to users. The conference will feature several Fedora-related workshops, including Fedora Import/Export, Islandora in the Wild, and Performance and Scale Testing of Fedora. Please register in advance if you plan to attend.
DC Area Fedora User Group Meeting
The Washington D.C. Area Fedora Users Group meets twice annually to share project updates, exchange ideas, and collaborate on Fedora-related activities. The next meeting will take place March 22-23 at the Library of Congress. The meetings are open to anyone who would like to attend.
LDCX
LDCX is an annual unconference that brings together leading technologists in the libraries, archives and museums (LAM) spaces, to work collaboratively on common needs. The event will take place March 27-29 at Stanford University. Registration is complimentary, and please register at the LDCX 2017 Eventbrite if you are interested in attending.
Hydra Developer Congress
include a Fedora workshop delivered by David Wilcox.
Advanced Hydra Camp
Data Curation Experts is offering an Avanced Hydra Camp on May 8-10 in Minneapolis, MN. This camp is for developers with a year or more hands-on Hydra development experience who have already attended Hydra Camp or have equivalent knowledge. Please register in advance to attend.
Islandora Conference
The second Islandoracon will be held in Hamilton, Ontario from May 15 - 19, 2017. The conference schedule will take place over five days, including a day of post-conference sessions and a full-day Hackfest. Please register in advance to attendThe Hydra Developer Congress emphasizes community code exchange and moving community development goals forward. This can include, but is not limited to, the topics listed in this year's agenda, as well as development issues and recommendations that may surface as priorities from the Hydra community, working groups, and interest groups. If you are a developer with a signed Hydra contributor license agreement (CLA) -- or are confident that you can submit a signed CLA by mid-March -- and you're available to attend the meeting, please register online. Registration is complimentary.