Topic suggestions for work during the November 2021 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 on the first day of the Congress.
Proposing Topics
You can...
add a topic to the table of proposed topics below
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 (to issues, branches, documentation, etc) | Time Estimate (For example: 3hrs, (2) 8hr days, etc.) | Proposed By | Facilitator | Add your name to this column if interested in this topic |
---|---|---|---|---|---|---|
Update Hyrax Install Documentation |
|
| ||||
Hyrax-valkyrization testing | Help test nurax-pg which is a Hyrax application using a postgres valkyrie adapter. | nurax-pg app | All the time that is available. | |||
Hyrax-valkyrization coding and bug fixes | Help address issues uncovered by the testing process. | nurax-pg app | All the time that is available. | |||
Samvera introductory technology documentation refinement |
| Will review Samvera.org and wiki pages |
| |||
Hyrax::Ability Hardening | Most samvera apps use CanCanCan to handle authorization for actions throughout the application. Hyrax provides a mixin module (Hyrax::Ability) setting up baseline authorization rules for Hyrax’s feature set. What does Hyrax::Ability permit/deny and for which users/groups? If you want to find out, you have to read the code. How can apps understand how changes will impact authorization? They can’t. Let’s fix this by documenting, testing, and refactoring Hyrax::Ability with clarity in mind. | Hyrax::Ability todo item. | 2 hours of group review of current code & discussion. probably as long as we care to take as individuals or in in pairs/swarms to implement changes. | |||
Hyrax container and chart publishing --- automation edition | Hyrax’s codebase has Dockerfiles and a Helm chart, which are occassionally manually published to the Samvera GitHub OCI registry (ghcr.io). Publication of these artifacts could and should be automated! | |||||
Rails 6 support | Do a gap analysis to figure out what is left to get all of the core compenents working on rails 6 then do the same for Hyrax. Then do the fun part of doing the work! | As long as people want to work on upgrading core components and Hyrax to Rails 6. | ||||
Ruby 3 support | Try to get all core components working on ruby 3 or at least make a plan. | 0.5-1 day | ||||
Hyrax Onboarding | Helping anyone who needs it to get Hyrax up and running locally (probably via Docker). | 2-3 hours | ||||
Samvera gem ownership | How do we manage gem ownership in the community? Linked examples show many owners, not all of them part of the community anymore. | 1 hour |
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:
...