Sprint Participation
From April until December of 2020, the first week of every month will be used as a one-week-long sprint with the top-level objective of releasing a Fedora 6.0.0 Beta this calendar year.
See the Fedora 6 Feature Tracking wiki page for progress updates.
To the degree possible, it is helpful to know who is able to commit to the sprint for any of the months in this period. Please list your name if you are available to participate in any of the sprints!
April 6 - 10
2020-04 Fedora 6 Sprint
Participants
- Jared Whiklo
- Danny Bernstein
- Ben Pennell
- Peter Winckles
Objectives
- Containment Index
- The containment index is designed to be used for:
- Keeping track of which Fedora resources are contained by which Fedora containers (resources)
- Facilitating the generation of 'ldp:contains' triples for responses to Fedora requests
- Success will be defined by:
Storing containment relationships in index- Storing containment relationships in OCFL
- Adding containment relationships when Fedora resources are added to a Fedora container
- Deleting containment relationships when Fedora resources are removed from a Fedora container
- Rebuilding containment relationships on application startup (if the index is empty)
- Providing ldp:contains triples in HTTP responses
- Ensuring the HTML UI renders contained resources
- Ensuring the HTML UI navigates containment relationships
- The containment index is designed to be used for:
- Initial JMS Messaging infrastructure
- The JMS messaging feature is designed to:
- Implement the Notifications section of the Fedora API Specification
- Per the Fedora messaging documentation
- Success will be defined by:
- Deciding on which message bus to use (was Guava)
- https://github.com/greenrobot/EventBus (Jared suggested this, but more reading indicates this is primarily for Android and maybe not a good choice)
- Guava
- https://github.com/bennidi/mbassador → benchmarks compare to Guava (https://github.com/bennidi/eventbus-performance)
- Wiring the bus into the code such that events are put on the bus
- Marshaling messages into the message format
- Publishing of messaging via JMS
- Deciding on which message bus to use (was Guava)
- The JMS messaging feature is designed to:
- Long running transactions
- Implement start and commit operations on transaction endpoint
- Implement cancel transaction on transaction endpoint
Tickets
May 4 - 8
Objectives
- HTTP PATCH
- Simple Search
- ? Rebuild from "Plain Vanilla" (Non-Fedora) OCFL
Participants
June 1 - 5
Objectives
- WebACLs
Participations
July 6 - 10
Objectives
- ...
Participations
August 3 - 7
Objectives
- ...
Participations
September 7 - 10
Objectives
- ...
Participations
October 5 - 9
Objectives
- ...
Participations
November 2 - 6
Objectives
- ...
Participations
December 7 - 11
Objectives
- ...
Participations
Standups (please post update by 10am EST)
Slack Standup Template
[Fedora 6 Standup]
Finished yesterday:
{ticket titles and associated JIRA links}
{AND please include brief textual description}
Working on today:
{ticket titles and associated JIRA links}
{AND please include brief textual description}
Blockers:
{brief textual description}