Samvera Tech Call 2025-12-17
Meeting Logistics:
Time: 9:00am PDT / Noon EDT
Zoom Meeting URL: https://iu.zoom.us/j/87635137325?pwd=YhVGftEpANzAwgk84swAyF53edj31x.1
(link will launch Zoom client – if you do not have Zoom, expand the instructions below)
Agenda (meeting notes below)
PR for QA to use native ActiveSupport::Deprecation functionality: https://github.com/samvera/questioning_authority/pull/410
There is some conditional code for different levels of Rails support since QA is tested against Ruby 3.0+Rails 6.0 through Ruby 3.4+Rails 8.1. ActiveSupport::Deprecations was added in Rails 7.1. The README says “This gem works with Rails 5.0-7.0 and Ruby 2.5-3.1”. What are the oldest versions of Rails we want to support? Could we remove support for the older Ruby and Rails Versions in the next major version QA release - i.e. 6.0.0?
This PR will generate lots of new deprecation warnings during test runs (they were previously silenced). Is this OK?
Hyku Wiki Updates - @Mark Bussey reviewed all the pages on the Hyku Wiki and came up with a list of recommendations for pages to move or delete: https://docs.google.com/document/d/1rmAgXVa-Z7srh7MyYldBi_PU-KQQgWhEk9_YvOe1lZs/edit?tab=t.0#heading=h.pd3dibmk18lm. The Samvera Documentation Interest Group has given the go ahead to move relevant documents into confluence. Would folks here be supportive of this PR https://github.com/samvera/hyku/pull/2859 to commit relevant pages to the /docs directory in the Hyku repo?
Hyku releases - A non-update
Moderator: @Rob Kaufman
Notetaker: @Randall Floyd
Attendees:
@Daniel Pierce
@Max Kadel (Notch8)
@Sarah Proctor
@Praneeth Byna
@Tracy McCormick
@Mark Bussey
@Chris Colvard
Meeting Process
Notes
PR for Questioning Authority
Informational, got merged
QA had suppressed deprecation warnings in test runs
So test runs could get noisier with warnings
May have to drop testing matrix below Rails 7.2 because the ActiveSuppor::Deprecations not available
Wiki updates
Trying to find overlaps and consolidate and targeting either Wiki or repo per the list ???
How do we deal with the wiki pages that need to be removed
Consensus was that we should just disable the Wiki in the repo entirely
If anyone objects to that, we can find a way to automatically create/sync the wiki after the fact
Hyku update
Wrapping up the last open issues for 6.1.2 release
Needs some more internal infrastructure to keep all releases up for testing
Mark found a Hyku testing plan during documentation sweep, kept it - Hyku team should review and consolidate
FITS
The opinion from tech/dev interests is that the time and effort would be better spent refactoring for a better replacement versus
Open PRs
Dynamic sitemaps https://github.com/samvera/hyrax/pull/7315
Would also like to do something for robots.txt in conjunction with sitemaps
Jan 7th 2026
Daniel moderate
Chris notes