...
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 |
| Developing Your Hyrax-based Application Running Hyrax-based application in local VM Wednesday, Dec 1, starting 9am Eastern (join when you can): https://iu.zoom.us/j/88944228014?pwd=WGFBVktDU044blp5UVYxQ0xsU1NSZz09 |
| |||
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 in need of a refresh and assign based on interest |
| |||
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! | Duration: 0.5 - 1.0 hours | ||||
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). |
Friday, Dec 3, 2pm Eastern: https://iu.zoom.us/j/88944228014?pwd=WGFBVktDU044blp5UVYxQ0xsU1NSZz09 | 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. | https://rubygems.org/gems/hyrax https://rubygems.org/gems/active-fedora Thursday, Dec 2, 11am-12pm Eastern: https://iu.zoom.us/j/88944228014?pwd=WGFBVktDU044blp5UVYxQ0xsU1NSZz09 | 1 hour | |||
CircleCI build image update | CircleCI is deprecating it’s circleci/* images at the end of this year. This should be a fairly easy change in the samvera orb but we’ll probably need to upgrade core components to use the 1.x version of the orb. | https://github.com/samvera-labs/samvera-circleci-orb/issues/43 | 2 hours |
...