|Developer Onboarding Documentation: Moving the Samvera KB
|The Samvera KB is a somewhat known but mostly out of date and not easily maintained resource that has just enough helpful info on it to cause confusion. The Developer Onboarding Working Group is working on moving the good info over to the Samvera Confluence wiki. We thought this would be a great thing to work on as part of the Dev Congress!
Samvera KB (not everything here is good info): https://samvera.github.io/
New location on Samvera Confluence Wiki: Samvera Development Knowledge Base
|Timebox at 3 hours max
|Promoting Bulkrax out of Samvera-labs
|Bulkrax is used by several institutions as part of Hyrax/Hyku implementations but the Bulkrax code is still living in Samvera-labs in Github. There seems to be only a little bit of effort remaining to finish the list of things needed for promoting this gem from Samvera-labs to Samvera.
Current Bulkrax code: https://github.com/samvera-labs/bulkrax
Steps for promoting code out of Samvera-labs: https://samvera.github.io/samvera_labs.html
|Enhance Hyrax IIIF API
Enhance the builtin IIIF components of Hyrax. Ideas:
|Helping anyone who needs it to get Hyrax up and running locally using Docker (dassie, koppie, and sirenia)
https://github.com/samvera/hyrax/blob/main/CONTAINERS.md (dassie and koppie)
|Wings as separate gem
|Since Wings is on its way to being deprecated, pull this out into its own gem
|Core Components review in light of Valkyrized Hyrax
|Core components - which ones should be folded into Hyrax and can any be deprecated? any used outside of Hyrax and require maintenance?