Samvera Community Wiki
Agenda: Wrap-up for Community Sprint December 1 - 5, 2025
12/5/2025 12PM Pacific / 3PM Eastern
Required roles: Host, note-taker
Host will use the list of topics in the wiki to call on each facilitator. Facilitators should summarize:
The focus of the group
What the group accomplished
Whether there are next steps or follow-up steps and how those have been captured
Host will lead a retrospective
proposed format: plus/delta
Give 3 minutes at the beginning to allow people to take notes on what they want to say
Host invites people to "raise hand" to contribute to the retro
Participants can speak to both categories at once to reduce the time spent calling on people.
Ensure the notes are open so people can add things later
Attendees:
@Chris Colvard
@Juliet Hardesty
@Daniel Pierce
@Nicholas Mark Homenda
@Tracy McCormick
@Praneeth Byna
@Sarah Cogley
@Mark Bussey
@Jon Cameron
Reports:
Rails 8 work (@Randall Floyd )
Released Hydra-editor and hydra-works this week.
Final status detailed on https://github.com/samvera/hyrax/issues/7214
Specifically, there is detailed info on a pattern I’m seeing where I’m unable to set things like the indexer class on classes inheriting from ActiveFedora::Base and that include Hyrax::WorkBehavior, but not sure yet why.
https://github.com/samvera/hyrax/pull/7233
Shared glossary (@Rebekah Kati )
Next steps: https://github.com/samvera/hyrax/issues/7305 which Rebekah will work on during a Hyrax Maintenance Sprint
Hyrax accessibility tickets (@Tracy McCormick, @Daniel Pierce, @Chris Colvard )
Made a number of PRs!
https://github.com/samvera/hyrax/issues/7108
https://github.com/samvera/hyrax/issues/7237
https://github.com/samvera/hyrax/pull/7296 (Still has failing tests)
hyrdra-editor (@Daniel Pierce working on finishing this)
https://github.com/samvera/hyrax/issues/7238
Hyrax VPAT (@Nicholas Mark Homenda )
Draft and ready for separating out the work for others to help out on
RIIIF Performance (@Daniel Pierce , @Mark Bussey )
Helped get @Max Kadel's PR for VIPS support merged
Bulkrax documentation alignment (@Juliet Hardesty )
Linked to Bulkrax end-user documentation in github to Hyrax and Hyku confluence wiki pages
https://github.com/orgs/samvera/projects/33/views/2?pane=issue&itemId=140766381
Hyku metadata guidelines documentation (@Praneeth Byna )
Started https://github.com/samvera/hyku/issues/2596 .
Next steps: Hope to finish next week.
Hyku theming and branding documentation (@Praneeth Byna )
Hyrax wiki documentation updates (@Sarah Cogley, @Rebekah Kati , @Daniel Pierce )
How to select work types (@Sarah Cogley )
https://github.com/samvera/hyku/issues/2666
Removing old developer focused pages (@Rebekah Kati , @Daniel Pierce )
https://github.com/samvera/hyrax/issues/7143
Future work: Hyrax developer documentation move to github wiki? Will bring up at Documentation WG
Hyrax test suite performance (@Mark Bussey )
IIIF manifest test speedup
https://github.com/samvera/hyrax/pull/7298
Handle some Blacklight deprecation warnings
https://github.com/samvera/hyrax/pull/7301
Deprecations gem dropping messages
Override in Hyrax to display messages
https://github.com/samvera/hyrax/issues/7303
https://github.com/samvera/hyrax/pull/7309
QA uses it’s own deprecations process suppressing all internal warnings in the test suite
Next steps: get all core components back to standard rails deprecation warnings then bring back into hyrax/hyku
https://github.com/samvera/maintenance/issues/175
Future work: each individual test run is reinstalling gems?
Hyrax Getting Started web page (@Jon Cameron, @Praneeth Byna )
Links to github fixed
https://github.com/samvera/hyrax/issues/7158
Future work: Customizing metadata wiki page could use an update
ActiveFedora 16 with Fedora 6 support (@Chris Colvard )
Added post-install message to Fedora 6 support PR, merged, and released ActiveFedora 16
Note: F4 support is ActiveFedora 15.x;
https://github.com/samvera/active_fedora/pull/1504
Browse Everything (Avalon team)
Working to bring Avalon’s fork back into main
Reached out to Jonathan Rochkind to review Dananji’s PR … he hopes to get to it eventually
Mason updating things in Avalon’s fork to prepare for contributing back upstream
https://github.com/samvera/browse-everything/issues/427
Next steps: continue work on bringing Avalon’s changes back upstream in the next couple weeks
Retrospective:
Plus (things that went well):
+ Everyone was helpful and responsive to help me along with my first sprint.
+ Super timely PR reviews
+ Helpful to have folks to sound ideas off
+ Facilitator ensured everyone had a task to work on.
+ Helpful to have daily standup/check-in (vs. working alone and asynchronously)
+ Awesome to have new folks in the community sprint, helped continue shaping up how we run these!
+ Having a critical mass of people working on coding tickets AND documentation tickets!
+ Having a pre-seeded board of tasks to work on
+ Glad many (most?) issues seemed to be sized appropriately for the sprint length
+ Well-defined issues
+ Appreciate the help received from the community members/slack channels whenever I hit any blocker or needed more clarity.
+ I appreciated the quick feedback on updates to the Hyrax wiki.
+ Good to meet and work with new folks, and reconnect with everyone else
Delta (things that could be improved next community sprint):
Might have liked a stronger “theme” for the sprint with more smaller tickets queued up for the theme (i.e. like more of the Accessibility tickets)
Consider having a Code Reviewer role that a participant can be assigned to each day?
Consider tagging PRs for new devs to review to get comfortable with the process. (or paring - see above about reviewer)
Have point folks available for questions (Hyrax, Hyku) - we sometimes had to guess or move ahead the best we could (or not work on things)
Could have scheduled some discussion times during sprint kick off to talk through tickets needing design work
It would be helpful if documentation tasks were prioritized - it can be difficult to determine what needs to happen first.
Maybe having more planning ahead of time on what tickets I could work on would make deciding what to focus on earlier would be helpful.
Consider avoiding time conflict between sprint checkin and tech call
Having sprint right after holiday break made it hard to do planning during tech call
If possible have next community sprint dates and facilitator picked out to be announced at the end of sprint
Have a sprint specific project board for documentation
5 minutes for Plus/Delta reflection