Friday, January 28, 12 PM Pacific/3 PM Eastern
GitHub project
Group Updates
- Update to Bootstrap 4 in Hyrax
- Adam - decent progress - addressing non-JS issues (CSS and markup)
- Margaret - more work to do, talking to tamsin - main Bootstrap issues have been addressed
- branch should remain in place - still outstanding JS issues and testing needs to be fixed
- there are issues for most of this but there are still some issues to be created
- finishing up seems pretty manageable but hard to estimate things like file uploader without more investigation
- Blacklight work almost entirely done in that branch
- everything that depends on Blacklight and Bootstrap is out of alignment and needs to be adjusted
- Hyrax-Valkyrization
- Lynette - excellent progress this week; still things to do to consider MVP done; getting files to show in all of the places they are supposed to show; tamsin and Alexandra made lots of progress but not quite done
- permissions work today and close but still testing weird; very complex Solr query is needed right now; hoping to wrap this up today
- Chris working on deletes
- collection-specific deleting
- clean up when deleting collection/admin set/work, deletes access control list (current work)
- these are huge chunks out of MVP
- updated UBER issue with this work
- Alexandra - nurax-pg, can upload object with file attachments, get characterization, see it on show page, fileset show page still missing info and might not work at all
- on deploy (nurax-dev and dassie) still using Fedora and Wings - nurax-pg is only place to see these changes working with non-Fedora (postgresql)
- Next community effort: March 7-18 - Princeton team joining in for some work
- Hyrax Onboarding (M1-specific)
- new firepower image
- PR nokogiri - comment to maybe move away from alpine linux but PR would be fix for now
- Jon C tested and might have fully worked for him but there were possible network issues with docker
- Fixing feature tests for docker-compose - didn't end up happening this week
- Sharing steps for infrastructure - Hyrax Infrastructure Maintenance Steps - January 28, 2022
- README update CONTAINERS might not have come through - no PR? follow up with tamsin
- VSCode and Hyrax
- Data Seeds Improvement
- Michael - having trouble getting hyrax running locally; have idea on what to do but not able to make progress to do this work
- might join up with HMWG next week?
Retro (Plus / Delta)
| Plus | Delta |
|---|
| Great teamwork on Hyrax-Valk work | use breakout rooms for topic work instead of separate zooms (host likely has to pre-set) |
| pre-work by Margaret on Bootstrap helped to make a lot of progress this week | make sure facilitator reviews retro from previous dev congress |
| smooth timing for check-ins and meetings across time zones; could do work locally and contribute to dev congress |
|
| group size seemed good, not too small (3-4 per topic seems good for momentum) |
|
|
|
|
|
Questions
Wrap-up Instructions
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