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
Dial by your location
Meeting ID: 940 3021 4208 Find your local number: https://notredame.zoom.us/u/aPls29JbL Join by SIP 94030214208@zoomcrc.com Join by H.323
Meeting ID: 940 3021 4208 |
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)
- Hyrax Containers (tamsin woo )
- Dev Environment:
- `git clone git@github.com:samvera/hyrax.git; cd hyrax; docker-compose build; docker-compose up`
- Published, reusable containers:
- Kubernetes/Helm
- fcrepo4 chart
- hyrax chart
- draft documentation: https://github.com/samvera/hyrax/commit/6d61df9557c4a066a16397f6ab07ed4a17e50d5d
- Dev Environment:
- Samvera Connect presentation submissions
- Samvera Dev Congress update
- <add open agenda items here>
- Samvera help follow-up
- Pull request review
- 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:
...
- Containers for Hyrax
- Tom has been providing updates on this work in the #dev Channel
- There is now a docker-compose environment which Tom is using as a development system
- Tom has also been exploring strategies for reusable containers
- Quite a lot of progress for finalizing a Kubernetes environment and Helm in order to ensure that Hyrax can be deployed into a reference environment
- PostgreSQL, Solr, and Redis would be deployed into this
- Can this be used to provide a test environment?
- There shouldn't be much additional labor needed in order to structure this as a test environment
- Reusability
- There is a single Dockerfile specifying a multi-stage build
- First provisions a deployment directory, along with a base Hyrax setup
- Second and third provide environments for Rails Engine development
- Synchronization uses a local working copy for supporting development in the container
- There is a separate plain Hyrax image useful as a base image for the developer's own Hyrax application
- Hyrax Container is used for deployments using Helm
- There is a single Dockerfile specifying a multi-stage build
- Tom is still working on this, and please welcomes individuals who might want to experiment with or test this using Kubernetes environment
- Feedback for working with Kubernetes and Helm is definitely desired
- Samvera Connect Presentation Submissions
- Presentation and lightning talk submissions can still be submitted
- Everyone is encouraged to submit their proposals please!
- Jeremy proposed to present a lightning talk discussing the structure and role of the Samvera Tech. Call
- Guiding interested parties in how to contribute/get involved will be very helpful
- There might be two lightning talks: the Samvera Tech. Call and a separate talk addressing getting involved
- People may be more likely to attend lightning talks (as opposed to any call-to-action)
- Specificity in the lightning talk is also preferred
- Presentation and lightning talk submissions can still be submitted
- Samvera Dev. Congress Update
- Is there an update from the group planning this?
- Jeremy is on this group
- Presently there is a Wiki Page: Developer Congress - November 16-18 2020
- Want CfPs to first finalize for Samvera Connect
- Dev. Congress is scheduled for Nov. 16-18th, and it will be all virtual
- October 1st an e-mail announcement shall be issued
- This will also be discussed during the next Partners Meeting
- There will be a request for developer resources in order to try and ensure that enough organizations participate
- How might others support Dev. Congress planning?
- Please consider topics worth focusing upon
- Perhaps Docker-related work? Ensuring that there is a collective understanding of the requirements for this at the Congress?
- Any amount of pre-planning which we can address will only be better
- Given that this is 3 days in length, it will only ensure that the time is used more efficiently
- Lyrasis Wiki
- Requesting an account used to be possible with a main page where one could request an account
- How would one do this now? This page needs to be inaccessible
- It was recommended that one contact Richard Green with a request
- Samvera Help Follow-Up
- Linda Sato had a question regarding AdminSetCreateService
- https://samvera.slack.com/archives/C0F9JQJDQ/p1598896022011600
- Might anyone be available to respond to Linda who is familiar with the scope of this question?
- It may be related to the database and/or Solr not being entirely clean while trying to debug this
- Samvera-Tech Mailing List
- Alice had general questions regarding how Samvera works
- Answering some of the questions, following a request to the community to answer others might be the best approach
- Linda Sato had a question regarding AdminSetCreateService
- Pull Request Review
- https://github.com/samvera/hyrax/pull/4493
- Authored by Jeremy, but a pull request against Lynette's PR
- Adding human_readable_type into the Solr index requires that the anonymous class-building for Valkyrie/Hyrax support this
- Do we need an anonymous class builder in the RSpec tests?
- Resistance to adding a builder pattern; It is explicit regarding the dependencies if one must manually derive a child class from Hyrax::Work
- For this PR, one needs to have an ActiveModel name, without the Class being an explicitly-named
- Perhaps have a default for #human_readable_type also
- It should be a reasonable assumption for the ecosystem that an ActiveModel#name be present for the object
- With an alternate default, maybe `self.class.to_s` could suffice?
- Agree that ActiveModel#name should be acceptable, the concern related to indexer dependencies
- Proposed changes to the PR are welcome, but one approval was issued
- PR was rebased and merged for Lynettes PR (4488)
- Hyrax::Work is a Valkyrie model
- Chris has been working off of GenericWork for a plugin
- Is there a correlation between the GenericWork#name and the ActiveModel#name on Hyrax::Work?
- ActiveModel#name uses a class-level method `.name`, uncertain if there is a mutator for this
- Class method `.name` is a Ruby feature for all Classes
- ActiveModel#name might use an override for this
- ActiveModel#name returns an object, Hyrax::Name object in this case
- Hence, to get a string, one needs to invoke `Hyrax::Name#name`, so `my_model.name.name`
- There are also helper methods on `Hyrax::Name`, such as `#humanize`
- Chris has been working off of GenericWork for a plugin
- What is the difference between `Hyrax::Name` and `ActiveModel::Name`? Are these compatible?
- These should be compatible Class APIs
- Merge is welcome from others
- https://github.com/samvera/hyrax/pull/4493
- Next Scheduled Call
- Moderator: Jeremy
- Notetaker: Tom
- Call concluded at 09:41 PDT/12:41 EDT