Samvera Tech Call 2017-09-06

Time: 9:00am PDT / Noon EDT

Call-In Info: 1-641-715-3660, access code 651025

Moderator: Jim Coble

Notetaker: Esmé Cowles

Attendees:

• Michael Joseph Giarlo (Stanford University)
• Glen Horton (Cincinnati)
• Thomas Scherz (Cincinnati)
• LaRita Robinson (Notre Dame)
• Esmé Cowles (Princeton)
• Lynette Rayle (Cornell)
• Chris Colvard (Deactivated) (Indiana Univ.)
• Adam Wead (Penn State Univ)
• Former user (Deleted) (Alberta)
• Valerie Maher (DCE)
• Jacob Reed (Univ. of Utah)
• Trey Pendragon (Princeton)
• Michael Joseph Giarlo (Stanford)
• Michael B. Klein (Northwestern)

Agenda

1. Roll call by timezone per following order - ensure notetaker is present (moderator)

   1. folks outside North and South America

   2. Eastern timezone

   3. Central timezone

   4. Mountain timezone

   5. Pacific timezone

   6. folks who were missed or who dialed in during roll call

   7. Welcome all newcomers!
2. Agenda (moderator)
   1. Call for new agenda items (moderator)
   2. Hyrax/Sufia/CC usage survey heads-up (Michael Joseph Giarlo)
   3. Concurrent CI builds and Rails support testing (Michael Joseph Giarlo)
   4. Hyrax ActionCable PR needs review (Michael Joseph Giarlo)
      1. See: https://github.com/samvera/hyrax/pull/1624
   5. Release Hydra-PCDM that includes reversed relationship for collection nesting (Lynette Rayle)
   6. Call for help with "Nurax" (Michael Joseph Giarlo)
      1. If interested, reach out to Julie Rudder (@jrr on Slack)
3. Moderator/notetaker for next time (moderator)
   1. Moderator: 
   2. Notetaker: 
4. After call, this week's notetaker should create the agenda for the next call.

Notes

1. New Agenda Items?
   1. None
2. Hyrax/Sufia/CC usage survey (Mike Giarlo)
   1. Annual since ~2013 to get info on usage of Sufia, and expanded to CC and Hyrax
   2. Short, but useful data on future directions
   3. Will present results in a SamveraConnect lightning talk
3. Concurrent CI builds (Mike Giarlo)
   1. Because of build matrix (push/PR and Rails 5.0/5.1), one PR takes up 4 of 5 simultaneous build slots
      1. If there are multiple PRs, things can get backed up
   2. Disabled push builds to reduce this, and we could also stop building multiple Rails versions to reduce this more
      1. Can we do a nightly build to do other variants?
         1. There are nightly builds, not sure what features that has
   3. Can we pay for more simultaneous builds?
      1. Yes, for $500/month (prepaid yearly), we would get an additional 10 builds
      2. Have Q in to Travis to ask if that's per-org (samvera + samvera-labs)
   4. Can we work in our forks to reduce the impact?
      1. Worth considering, but we have advised people to push to samvera repos to make it easier to collaborate
   5. How painful would it be to only build on Rails 5.1?
      1. Esp. if we can do nightly builds on 5.0 or whatever, then it should be fine
   6. If we are interested in paying for better CI service, there are a lot of other options
4. Hyrax ActionCable PR (Mike Giarlo)
   1. PR to add Rails ActionCable notifications to Hyrax (replacing polling): https://github.com/samvera/hyrax/pull/1624
   2. Would like code review on the general approach before writing tests
5. Releasing Hydra::PCDM with reversed collection nesting (Lynette Rayle)
   1. Last release is 0.9, Aug/Sept 2016
   2. Vast majority of commits since then are cleanup, build matrix, docs, etc.
   3. So collection nesting with pcdm:memberOf is the only major change
   4. Are there any concerns before doing a release?
      1. Maybe this should be 1.0?
      2. Maybe object-object relationships should also be reversible?
         1. Probably — but not a high priority
      3. Will there be a data migration?
         1. There doesn't seem to be any usage of the old collection nesting, so probably not
         2. The old membership functionality is still there, so it should be backwards compatible (same as collection-object membership)
   5. We should do a 0.10 release
      1. Will also retroactively tag 0.9 because it's not there now
6. Call for help with Nurax (Mike Giarlo)
   1. Working on testing process for new releases — Nurax is a vanilla Hyrax instance with a bunch of features turned on, good seed data, continuous deployment, etc. to make it good for testing
   2. https://github.com/curationexperts/nurax
   3. Would like help maintaining this, please talk to Julie Rudder (@jrr on slack)
7. Call for next week's moderator/notetaker
   1. Moderator: Trey Pendragon
   2. Notetaker: Former user (Deleted)