How to connect: https://notredame.zoom.us/j/94030214208 (link will launch Zoom client – if you do not have Zoom, expand the instructions below)
Expand | ||
---|---|---|
| ||
Meeting ID: 940 3021 4208 One tap mobile
|
Time: 9:00am PDT / Noon EDT
...
Roll call by timezone per following order - ensure notetaker is present (moderator)
folks outside North and South America
Eastern timezone
Central timezone
Mountain timezone
Pacific timezone
folks who were missed or who dialed in during roll call
- Remind everyone to sign in on agenda.
- Welcome all newcomers!
- Agenda (moderator)
- Call for new agenda items (moderator)
- Supporting Rails Engine Development (James Griffin)
- Should we continue to actively use https://github.com/cbeer/engine_cart?
- This is very integral to the current development process of Hyrax.
- Can have docker image with a dummy app that wraps the engine cart generation
- Engine cart provides test of the app generation process
- Is there a path that would let us test the app generation
- We do need to vet the provenance of committers to Engine Cart
- EngineCart is a bit outdated in terms of its strategy; There is space for improvement but its not urgent
- Perhaps there are alternative approaches for developing and testing Rails Engines
- Rails Dummy App: https://guides.rubyonrails.org/engines.html#generating-an-engine
- There seem to be patterns for this
- Rails Dummy App: https://guides.rubyonrails.org/engines.html#generating-an-engine
- Paths forward
- Bring EC into Samvera
- Come up with a different pattern for Engines
- Do nothing (aka pay attention to it)
- Action Item - bring this up for review in next Maintenance Sprint window (attn James Griffin )
- Should we continue to actively use https://github.com/cbeer/engine_cart?
- Samvera-CircleCI-Orb release coming soon (Collin Brittle)
- 1.0.0! Backwards incompatible! Testing coming soon!
- There are deprecations coming!
- Brief update for planning group on Dev Congress (Anna Headley )
- Promoting Bixby (bess )
- Action Item - James Griffin will be working through this today
- Samvera help follow-up
- Pull request review
- https://github.com/samvera/hyrax/pull/4373 - Stuck in an odd build state
- Moderator & notetaker for next time
- Moderator:
- Notetaker:
- After call, this week's notetaker should create the agenda for the next call:
Open template agenda titled "Samvera Tech Call 2020-xx-xx"
- Click on ... in the top right corner, and select copy.
- Popup will open for location. It should contain:
- Space: Samvera
- Parent page: 2020
- Select copy. New page should be created.
- Modify the title to remove "copy of", update it with the next date, add moderator, notetaker, and any carry-over agenda info. Click Publish.
- PR Review
- Review issues:
- PR review coordinator for next time:
...
- Array in a CSV, need these to arrange this as table of contents values
- Tom: This is a complex case without a straightforward answer - baseline is that, there is no order for metadata attributes, and one cannot rely upon indexing to preserve the order of the values
- Anna: Trey is trying to point someone to Hyrax Metadata Ordering Working Group
- Are there other places where this topic has been discussed?
- Tom: Finishing the Valkyrie work will provide Hyrax to persist ordered metadata attributes
- No notion of addressing this within the active_fedora space
- No technical solutions will be pursued, but those who reported this will be directed to documentation
Pull Requests on Hyrax
- https://github.com/samvera/hyrax/pull/4373
- Do not know what to do to get the tests unstuck
- Chris retriggered the build - CircleCI and GitHub notifications are having difficulties
- Tom: It might just be a rebasing issue, and it may just be safe to merge this
- Do not know what to do to get the tests unstuck
- https://github.com/samvera/hyrax/pull/4330
- Upgrade 2.
- x–stable branch to Rails 5.2 and ActiveFedora 12
- Michigan is wanting to take over this PR and branch
- Tom: Please!
- https://github.com/samvera/hyrax/pull/4363
- Fixes user interface behavior where a proxy user is not rendered after a deletion
- There are questions regarding the parsing of route strings at the controller level
- Test needs to be adjusted, as it does not test the feature itself
- Fixes user interface behavior where a proxy user is not rendered after a deletion
...