Topic List - Developer Congress May 13-17, 2024
- Heather Greer Klein
- Randall Floyd
- Chris Colvard
Topic suggestions for work during the DATE Developer Congress. Please follow checklist below for submitting your proposed topic. If your topic has related github issues they can be added to the Developer Congress Project Issue Board. --link
Topic Proposal Checklist
- Short Title
- Description
- Link to Issues, Branches, Documentation, etc.
- Duration, estimate how long the session will last (For example: 3hrs, (2) 8hr days, etc.)
- Proposed By (Samvera Slack Channel Handle)
- Facilitator (Samvera Slack Channel Handle)
Example
Title: Update ActiveFedora to work on Fedora 5.
Description: We have a branch sitting around that almost gets ActiveFedora working with Fedora 5, we could work together to get this passing.
Links: https://github.com/samvera/active_fedora/tree/fedora_5
Duration: 6 hrs
Proposed By: name here
Facilitator: Seeking a facilitator.
NOTE: Put this information in the Proposed Topics table below.
Proposed Topics
You can...
- add a topic to the table of proposed topics below (See Topic Proposal Checklist and example above for guidance on proposing a topic.)
- identify yourself as a facilitator for a topic you propose or a topic proposed by others (See Facilitator Guide below.)
- indicate your interest in one or more topics
| Title | Description | Links | Time Estimate | Proposed By | Facilitator | Interested in |
|---|---|---|---|---|---|---|
| Samvera documentation: Review it / Work on it | Samvera Developer On-boarding Working Group has ported Samvera KB docs from legacy site over to the Confluence wiki. Can this be used now as a central documentation area? We can test this by considering something like Bulkrax documentation and if/how that could be provided or connected through the Confluence wiki Samvera KB. Other documentation questions or tasks can also be proposed and organized for future IG/WG work. | Samvera Development Knowledge Base Samvera Developer Onboarding Working Group Meeting Tuesday, May 14, 3pm Eastern: https://iu.zoom.us/j/82763838554?pwd=RW13YnRieHFDN1V5QmptTFozTVBFUT09 | Time box: 4 hours | Juliet Hardesty | ||
| Hyrax/Valkyrie/Fedora 6 | Wrap up any issues blocking official F6 support. Includes:
| Draft Valkyrie PR for pairtree IDs: | Daniel Pierce | Daniel Pierce | Randall Floyd | |
| Freyja Migration Adapter (Fedora 6) | Walkthrough and fixup the valkyrie migration adapters Freyja and Frigg. Create list of changes needed to configure a legacy hyrax to use Freyja/Frigg | Daniel Pierce | Daniel Pierce | |||
| Hyrax Accessibility Audit (continued) | Finish Hyrax 5.0.1 accessibility audit for WCAG AA Look at EU accessibility directive guidelines to determine overlap with WCAG AA, create tickets where applicable. Start ticketing ARIA issues identified in SiteImprove (if time) | EU Web Accessibility Directive Guidelines and WCAG 2.1 Comparison | Rebekah Kati | Rebekah Kati | Juliet Hardesty | |
| Change ordered_aggregation relationships for Avalon and possibly Hyrax (with ActiveFedora) | Ordered_aggregation relationships are a major source of slowness when creating and editing works with many members. This is the case for Avalon and Hyrax applications. While converting applications to use Valkyrie will solve this problem it would be nice to have an interim solution. Avalon is pursuing replacing the ordered_aggregation with an array of ids serialized as a JSON string similar to how Valkyrie stores relationships. Work to be done is proving the approach works, writing a migration, and doing some benchmarking. | https://github.com/avalonmediasystem/avalon/pull/5778 | Chris Colvard | Chris Colvard | Daniel Pierce | |
Facilitator Guide
- Propose or claim a topic in the Proposed Topics table above
- You will be asked to introduce your topic with a brief summary (minute or less) during the kick off meeting
Contributor Resources
Goal of this checklist is to enable leaders of specific issues to be able to collect resources for those interested in contributing; aiming to provide a shared knowledge base before beginning the work together. While optional, if you're facilitating a topic we recommend you provide these resources to attendees ahead of time:
- Prepare zoom link or slack room link that will be used for contributors to gather
- Prepare short list of languages the work will be coded in
- Prepare list of any tutorials a contributor can complete to familiarize themselves with the work ahead
- If similar work has occurred in other repositories please include links to those repositories as well