Topic List - Developer Congress October 26, 2023
- Daniel Pierce
- Adam Ploshay
- Johannes Frenzel
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 |
|---|---|---|---|---|---|---|
| Developer Onboarding Documentation: Moving the Samvera KB | The Samvera KB is a somewhat known but mostly out of date and not easily maintained resource that has just enough helpful info on it to cause confusion. The Developer Onboarding Working Group is working on moving the good info over to the Samvera Confluence wiki. We thought this would be a great thing to work on as part of the Dev Congress! | Samvera KB (not everything here is good info): https://samvera.github.io/ New location on Samvera Confluence Wiki: Samvera Development Knowledge Base | Timebox at 3 hours max | Juliet Hardesty | Juliet Hardesty | Bradley Watson Johannes Frenzel |
| Promoting Bulkrax out of Samvera-labs | Bulkrax is used by several institutions as part of Hyrax/Hyku implementations but the Bulkrax code is still living in Samvera-labs in Github. There seems to be only a little bit of effort remaining to finish the list of things needed for promoting this gem from Samvera-labs to Samvera. | Current Bulkrax code: https://github.com/samvera-labs/bulkrax Steps for promoting code out of Samvera-labs: https://samvera.github.io/samvera_labs.html | 1/2 day? | Juliet Hardesty | Brandon Straley | |
| Enhance Hyrax IIIF API | Enhance the builtin IIIF components of Hyrax. Ideas:
| https://github.com/sul-dlss/riiif | Daniel Pierce | Daniel Pierce | ||
| Hyrax Onboarding | Helping anyone who needs it to get Hyrax up and running locally using Docker (dassie, koppie, and sirenia) | https://github.com/samvera/hyrax/blob/main/CONTAINERS.md (dassie and koppie) | 2 hours | Juliet Hardesty | Juliet Hardesty | Paul Walk |
| Wings as separate gem | Since Wings is on its way to being deprecated, pull this out into its own gem | Chris Colvard | ||||
| Core Components review in light of Valkyrized Hyrax | Core components - which ones should be folded into Hyrax and can any be deprecated? any used outside of Hyrax and require maintenance? | Chris Colvard | Paul Walk | |||
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