Attending
Time:12:00PM PDT/03:00PM EDT - 01:00PM PDT/04:00PM EDT
Zoom: https://princeton.zoom.us/j/281265700
Participants
- Trey Pendragon (Princeton University Library)
- Mark Bussey (Data Curation Experts)
- Noah Botimer (U. Michigan)
- James Griffin
Agenda
- Check out the GitHub Board Review Column
- Consider updating LICENSE to Apache2 #227
- DONE
- Deprecate Solrizer #19
- Is it worth putting out a final call for Solrizer deprecation before next Wednesday's Samvera Tech call, or just let it quietly fade away?
Only 1 response to the e-mail thread giving a qualified thumbs up.
- Is it worth putting out a final call for Solrizer deprecation before next Wednesday's Samvera Tech call, or just let it quietly fade away?
- Consider updating LICENSE to Apache2 #227
- Sprint in a little over a week
Notes
browse-everything#227 was merged
Active Fedora release 12.2.0
There was some discussion, James felt like there were some concerns with Hyrax compatibility
James will ping Colvard
Solrizer
Send out reminder next week?
E-Mail went out, and Jim Coble alone responded, felt that it was fine to deprecate the Gem
Trey:
It's probably best to still send out another reminder
Mark: Reminder on Tuesday, and will offer an agenda item for the Tech. Call on Wednesday
Next Sprint
Bess and Mark are looking to contribute to up to 0.5 FTE each
Noah will see if they are available
Tom is continuing Valkyrax work during that week, but does intend to run on both sprints
Our board is very empty
If Product Owners don't fill the board, we can address this in a few ways:
- We can populate the board ourselves
- We can cancel the sprint
- We can address what issues there are and take less than one week
Mark:
Test coverage sufficiency seems to be an open question
What does that mean for the community moving forward?
If we got through the issues and it did not consume the entire week, that might be acceptable
Trey:
Product Owners aren't necessarily responsible for ensuring that the code coverage is high enough for a component