Child pages
  • Samvera Tech Call 2017-12-06
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: Michael J. Giarlo

Notetaker: Jim Coble

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. Welcome all newcomers!
  2. Agenda (moderator)
    1. Call for new agenda items (moderator)
    2. Hyrax IIIF implementation question (Michael J. Giarlo)
      1. Requesting feedback on WIP PR: https://github.com/samvera/hyrax/pull/2311
    3. Hyrax 2.1 release plan update (steve van tuyl)
  3. Notetaker and moderator for next time
    1. Notes: steve van tuyl
    2. Moderator: Justin Coyne
  4. After call, this week's notetaker should create the agenda for the next call.

Notes

2.a. Call for new agenda items

  • Request was made for update on collections extensions work if someone could provide that.  LaRita Robinson noted that her nested collections work had been merged to the collections branch but that there was an issue uncovered on Nurax that needed clarification.  LaRita Robinson also created issues for the remaining nested collections pieces.

2.b. Hyrax IIIF implementation question

  • Michael J. Giarlo noted that work is underway to put the IIIF implementation work done in Hyku into Hyrax.  This involves the IIIF presentation API and image API.  He has a WIP PR on which he would like review and discussion – https://github.com/samvera/hyrax/pull/2311 .  He would prefer to pull in just the presentation layer first but currently there are some dependencies between the presentation layer and the image server implementation (RIIIF).
  • Justin Coyne noted that he thinks it is suboptimal to have RIIIF as a dependency in Hyrax; rather, an implementor should be able to use an image server of their choice.  Okay to have a dependency on an image server, just not on a particular image server.  Discussion ensued about ways to get around having a hard dependency on RIIIF in Hyrax.  No decision was made but review and comment on the PR referenced above would be useful.

2.c. Hyrax 2.1 release plan update

  • steve van tuyl noted that there has been follow-on discussion from last week's agenda item on this topic (whether to do a non-collections-extension 2.1 release and include collections extensions in 2.2 or stick with the plan to hold 2.1 until collections extensions was merged).  His take that was that the conversation was trending toward the original plan (hold 2.1 for collections extensions), primarily due to minor release testing considerations.
  • Justin Coyne spoke in favor of small, low risk releases even if they are are not as well tested.  Aaron Collier noted that some of the non-collections-extensions work that has been merged has been long-awaited.
  • Discussion ensued about the tradeoffs between the velocity of getting new work out in minor releases and having confidence in those releases as a result of thorough testing.  steve van tuyl and Michael J. Giarlo noted that the testing process is still relatively new and there there should be opportunity to try out some different models during the coming year.
  • No decision was made and conversation will continue.


  • No labels