Child pages
  • Samvera Tech Call 2018-09-12
Skip to end of metadata
Go to start of metadata

How to connect: https://psu.zoom.us/j/613720745 (link will launch Zoom client – if you do not have Zoom, expand the instructions below)

 Click to view telephone/H.323/SIP connection instructions

Telephone:

Meeting ID: 613 720 745

+1 646 876 9923 (US Toll)
+1 669 900 6833 (US Toll)
+1 408 638 0968 (US Toll)
International numbers available: https://psu.zoom.us/zoomconference?m=UZ_PRwQ56TNX1pDIsdDInAu8XPVqzlX3

H.323:

Meeting ID: 613 720 745

162.255.37.11 (US West)
162.255.36.11 (US East)
221.122.88.195 (China)
115.114.131.7 (India)
213.19.144.110 (EMEA)
202.177.207.158 (Australia)
209.9.211.110 (Hong Kong)
64.211.144.160 (Brazil)
69.174.57.160 (Canada)

SIP: 613720745@zoomcrc.com

Time: 9:00am PDT / Noon EDT

Moderator: Phil Suda

Notetaker: LaRita Robinson

Attendees:

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. Remind everyone to sign in on agenda.
    8. Welcome all newcomers!
  2. Agenda (moderator)
    1. Call for new agenda items (moderator)
    2. Deprecate hydra repository? (Trey Pendragon)
      1. All it has is the `grant_revoke_gem_authority.rb` script which gets edits - can we move that elsewhere?
    3. Reminder: Samvera permissions working group report back (LaRita Robinson)
      1. Webinar coming up 9/21/18 at 2pm EDT
      2. Details and calendar invite posted on samvera-tech https://groups.google.com/forum/#!topic/samvera-tech/IOdnD4ek5BY
    4. CI for Hyrax (Tom Johnson
    5. add agenda item here
  3. Notetaker and moderator for next time
    1. Notes: Phil Suda
    2. Moderate: Kevin Musiorski
  4. After call, this week's notetaker should create the agenda for the next call:
    1. Open template agenda titled "Samvera Tech Call 2018-xx-xx"

    2. Click on ... in the top right corner, and select copy.
    3. Popup will open for location. It should contain: 
      1. Space: Samvera
      2. Parent page: 2018
    4. Select copy. New page should be created.
    5. Modify the title to remove "copy of", update it with the next date, add moderator, notetaker, and any carry-over agenda info. Click Publish.

Notes

  1. Agenda item 2b... Trey Pendragon - Should Hydra repository be deprecated
    1. The core component working group is finishing its last sprint before Samvera Connect. Hydra came up as one of the core components. In the past, the idea was that installing this one gem would install add dependencies, but it was never kept up with. The general recommendation now is to either use Hyrax or individual components. Normally this would mean we would propose deprecation of the gem, but it has one script that is regularly used - grant/revoke gem privileges, which gives everyone permission to release things. What do we want to do with this repository and this script? Should we keep just this script in the repository, or is there a more reasonable place to put this one piece of code?
    2. Tom suggested moving the script to hyrda-head and deprecating Hydra, and suggestion received general consensus. The code will be moved, and an email will be coming soon.
  2. Agenda item 2c... LaRita Robinson - reminder re: Permissions analysis working group webinar
    1. Webinar coming up 9/21/18 at 2pm EDT
    2. Details and calendar invite posted on samvera-tech https://groups.google.com/forum/#!topic/samvera-tech/IOdnD4ek5BY
  3. Agenda item 2d... Tom Johnson - CI for Hyrax
    1. Hyrax working group has been having trouble with Travis and CI throughput for Hyrax in general. Working to deal with flappy tests in suite, but big part of issue is flaky Travis infrastructure causing problems lately, as well as concurrency issues. Case on Monday led to 12 hour backlog on PR's. 
    2. Expect to see Circle CI build come into Hyrax very shortly... Daniel Pierce is working on it now. Once in place, also working to pay for more concurrency. This may also help with build-length issues because we can cache engine cart builds for internal test app. Looking into questions on how to invalidate that cache when needed. 
    3. Rob Kauffman has offered to set up some gitlab CI infrastructure for evaluation as well.
    4. At some point we will probably come back to community to propose switching… this is for evaluation at this point. 
  4. Notetaker and moderator for next time
    1. Notes: Phil Suda
    2. Moderate: Kevin Musiorski



  • No labels