...
| Home |
| Developer Resources | Check-in Notes |
| Expand | ||
|---|---|---|
| ||
|
Topic suggestions for work during the DATE 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. --link
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
...
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
...
Hyrax-Valkyrization MVP
The goal was to have a functional MVP (minimal viable product) prior to this Community Effort. The MVP for Hyrax using a postgres Valkyrie adapter is defined as: CRUD (i.e. create, read, update, delete) operations for the major components (i.e. admin sets, collections, works, file sets, files) can be successfully accomplished through the UI. This includes additional functionality that is required to load the forms that support these operations.
The status of the MVP organized by major component is described in Issues #5326. Any incomplete functionality for the MVP has the highest priority.
What to work on?
The Project Board lists issues related to the Valkyrization effort and includes columns:
- Ready - issues that are ready to be worked on (no known blockers) and are not already assigned to a developer
- In Progress - issues currently being worked on - when you move an issue to this column, assign it to yourself and any other developers working on it with you
- Ready for Review - there is a PR that fixes the issue, tests are green (passing), and it is ready for review
- DONE - completed issues
There are two additional columns that are used by organizers.
- Back Log - issues with known blockers OR issues that are older and needing review
- Archived - issues closed prior to this community effort
NOTE: You can also see issues related to this effort using the Valkyrization label on the GitHub Issues page for Hyrax.
Reference Documentation
References for Hyrax Development:
- Hyrax Development Guide - for development setup with solr_wrapper, fedora_wrapper, etc
- FAQ for Dassie Docker Test App - for development setup using docker environment
- Hyrax Valkyrie Usage Guide
References for Understanding Hyrax & Valkyrie Code: