Topic List - Developer Congress 2020
Topic suggestions for work during the November 2020 Developer Congress. Please follow checklist below for submitting your proposed topic. If your topic has related github issues they can be added to the 2020 Developer Congress Project Issue Board.
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) (Topic Facilitator Guide - Developer Congress 2020)
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: Trey Pendragon (Slack: @tpendragon)
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 List - Developer Congress 2020#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 Topic List - Developer Congress 2020#Facilitator Guide below.)
- indicate your interest in one or more topics
| Title | Description | Links | Time Estimate | Proposed By | Facilitator | Interested in |
|---|---|---|---|---|---|---|
Review Samvera Labs for Promotion Candidates (or Archive Candidates) Count(0) | We have quite a few repositories in Samvera Labs. Some of these may warrant promotion into Samvera; Others may be something to move to samvera-deprecated | https://samvera.github.io/samvera_labs.html | Duration of the Dev Congress | Jeremy Friesen (per discussions in 2020-09-10 - Samvera Branch Renaming Working Group | ||
What are we going to do about the cloud?! Count(0) | Some steps have been taken toward containerization and orchestration support for Samvera components, but we're missing a clear vision for what support would be useful, what containers and other resources we should publish and maintain, etc... Can we fulfill the vision of "Hydra in a Box" (a box is a type of container, after all)? | immemorial | tamsin woo @no_reply | |||
React IIIF Media Player Count(5) | Build and extend a IIIF powered audio/video player with React, JavaScript, Rollup, and Styleguidist. | Github: Github Project: NPM (coming soon...) | Dev congress and extending into a community sprint Nov. 19-25, 2020. Join us for some pre-Thanksgiving fun. | slack @adam.arling | ||
Hyrax-Valkyrization Count(5) | Continue work on moving Hyrax toward being able to switch over to Valkyrie as the data layer. | https://github.com/samvera/hyrax/projects/20 | Dev congress and beyond | Lynette Rayle | Lynette Rayle (if needed - happy for someone else to lead) | |
M3 Metadata Parser for Hyrax/Valkyrie Count(1) | Hyrax's Valkyrie based models have config-driven schema loading. To support Allinson Flex, we'll want that to have M3 support. Let's work on it | Maybe a day to get a base implementation? Probably more follow-up work after that. | @no_reply | |||
What the Front Door? Providing guidance to try out Hyrax Count(2) | Hyrax's documentation provides a variety of ways to get Hyrax up and running, sometimes all in the same place. We can probably sort that out to provide clearer guidance. | Documentation that still seems relevant: https://github.com/samvera/hyrax/blob/master/README.md https://github.com/samvera/hyrax/wiki/Hyrax-Development-Guide#setup-development-environment https://github.com/samvera/hyrax/wiki/Hyrax-Development-Guide#quick-start-for-hyrax-development https://samvera.github.io/getting_started.html Documentation that is still available but doesn't seem relevant anymore: https://github.com/samvera/hyrax/wiki/Configuring-an-OS-X-Samvera-Dev-Environment https://github.com/samvera/hyrax/wiki/Production-Installation-Overview Meeting Notes (2020-11-16): https://docs.google.com/document/d/16DKxq1e3c_pcbF-d3TQF9Ek641QmOYaaYDwpXqvOkfc/edit?usp=sharing | Maybe a day to talk through the options, how to provide guidance for which option to use, and how best to provide those options in our documentation. Follow-up work will be needed to actually update documentation. | Juliet Hardesty | Juliet Hardesty | |
Rails 6.0 / Blacklight 7.0 Support Count(3) | Hyrax and most core components currently only support up to Rails 5.2 which is facing the possibility of losing support with the looming release of Rails 6.1. Let's review what needs to be done and make a plan. If there is interest then start the work! | https://github.com/samvera/hyrax/issues/4016
Open PRs on Blacklight integration that helps ease the transition to 7.0: Working document: https://docs.google.com/document/d/1HFysWClpJk0tWgGwGnrxiUZxr_dkrfAEwDIlCAA73RE/edit# | 2 hours to make a plan and document it. Working on the plan could fill as much time as there is interest. | Chris Colvard (Deactivated) | ||
Circle CI Orb updates, release 1.0, and promote to core? Count(1) | The Samvera CircleCI orb has unreleased improvements and unmerged PRs. A new release might need to be 1.0 to avoid breaking existing users. We should also look at what it would take to promote the orb to samvera core. | https://github.com/samvera-labs/samvera-circleci-orb/pulls https://github.com/samvera-labs/samvera-circleci-orb/issues https://github.com/samvera-labs/samvera-circleci-orb/issues/19 | 2-4 hours depending on goals | Chris Colvard (Deactivated) | ||
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