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.
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 | Details | Proposed By | Facilitator | Interested in |
|---|---|---|---|---|
| Description: Want a community review and audit of the Samvera and Samvera Labs teams. Make sure that settings are applied properly, and that those who are no longer members of the community are not IDed as gem owners, etc. Need to clarify who has access and who to contact to push to Ruby gems and to do releases Will recommend that Admins must have 2FA enabled Will notify the community and do this organization discussion and implementation during the May Dev congress. Links: Time Estimate:
| Roadmaps Alignment Group | ||
| Description: Discussion and strategizing and possibly development work around performance issues experienced using Hyrax 3.x. At least one example is what happens when trying to delete a work with many filesets (see issue link). Identify other issues / create issues Possibly review identified performance issues with Valkyrized Hyrax as well and see if there are differences or improvements. Links: Time Estimate:
|
|
| |
OAI-PMH feeds in Samvera Tech | Description: Providing harvestable OAI feeds for content is necessary for sharing to DPLA. Maybe this is just relevant for Hyrax but this might also be something to work on in the context of Hyku. Unclear if this is something that can be added to Hyrax or if this should be providing documentation of options for local implementation. Links:
Time Estimate:
| |||
Hyrax Batch Edit Review/Design-a-thon | Description: Batch Edit is a specific interface for Works with a set of actions that is part of Hyrax. It is not behind a feature flip and is separate from the Bulkrax batch round-tripping that is a possible gem to add on to Hyrax. Batch Edit for Works could benefit from a redesign or a decision to remove it from Hyrax altogether. UX, design ideas, wireframes, use cases and opinions all welcome! Links: Time Estimate:
| |||
Hyrax upgrade work for Blacklight 7/Rails 6 | Description: Upgrade work might still remain to support Blacklight 7 and Bootstrap 4, both of which are needed to upgrade Hyrax to use Rails 6. Currently, Hyrax uses Rails 5.7.2 and that is reaching end of life on June 1. Links:
|
| ||
| Description: Helping anyone who needs it to get Hyrax up and running locally (probably via Docker). Links: Time Estimate:
| |||
| Description: Hyrax is still using the deprecated This might also bring dropping support of EOL Ruby versions (< 2.7) into question. Links:
Time Estimate:
| |||
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.
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: