Topic suggestions for work during the Developer Congress, in addition to the introductory Hyrax and Community Code work. 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.
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 participants |
|---|---|---|---|---|---|---|
Running Hyrax locally | Install and run Hyrax locally using provided Docker instructions. | Instructions: |
| Julie Hardesty | Daniel Pierce Julie Hardesty - Mac (application-based/Docker Desktop) Linux? Windows? |
|
Implement data seeds | Add data seeds to non-production Docker install of Hyrax so there are collections with works in place, ready for testing and development work. | Data seed needs for dev: https://docs.google.com/spreadsheets/d/1b93me1Gh614eQEWzeqzsSw32PDr_ymIfJ-PvrR7zxDM/edit?usp=sharing Previous data seed code work: https://github.com/samvera/hyrax/blob/main/lib/generators/hyrax/templates/db/seeds.rb 11am Eastern Tuesday, Dev Congress Zoom |
| |||
Extend metadata.yml to ActiveFedora::Base work models | Make the pattern for specifying the attributes of a work type in a yaml file that was introduced in Hyrax 3 work with ActiveFedora::Base models and backport to Hyrax 2.x | Exploratory work done in a branch: More work done in a hyku context specific to certain models: | Chris Colvard | Chris Colvard | ||
Make feature tests runnable in docker environment | Feature tests are not able to connect to the external chrome in docker making all of the tests fail. |
| Chris Colvard | |||
Documentation on code base patterns to help educate new contributors | Pattern documentation started at… https://github.com/samvera/hyrax/wiki/Development-Patterns |
| ||||
Implementing a CLA checker |
| |||||
| Open Hyrax issues that (we think) are relatively small or good places to start. Available for trying out a new local Hyrax install and help improve the developer/contributor workflow. | Add bibliographic_citation to the form - https://github.com/samvera/hyrax/issues/4632 CC4.0 license configuration - https://github.com/samvera/hyrax/issues/810 Reports show as “Unfiltered” when they are, in fact, filtered - https://github.com/samvera/hyrax/issues/1335 Tab selection lost when changing locale - https://github.com/samvera/hyrax/issues/3766 |
| |||
Hyrax-Valkyrization | Continue efforts to move Hyrax to fully use Valkyrization as the backend storage mechanism. | Project Board: | ||||
File Visibility PRs to Hyrax | HykuAddons has PR work that makes it possible to set file-level visibility (public, institution, embargo, lease, private) separate from work visibility |
10am Eastern Tuesday, Dev Congress Zoom |
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