Samvera Tech Call 2018-03-07

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

Time: 9:00am PDT / Noon EDT

Moderator: Steve Van Tuyl

Notetaker: James Griffin

Attendees:

• Steve Van Tuyl (oregon state uni)
• Michael Joseph Giarlo (Stanford)
• Glen Horton (Cincinnati)
• Jim Coble (Duke)
• tamsin woo (DCE)
• James Griffin (Princeton University)
• Justin Gondron (Notre Dame)
• Lynette Rayle (Cornell)
• LaRita Robinson (Notre Dame)
• Chris Colvard (Deactivated) (Indiana University)
• Collin Brittle (Emory)
• Jennifer Lindner (DCE)
• Chris Diaz (Northwestern University)
• Andrew Myers (WGBH)

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. Information gathering & discussion for feature specs refactor (LaRita Robinson)
      1. I created some starting notes and questions to begin the thought process
      2. Link to the notes page is on this issue: https://github.com/samvera/hyrax/issues/2738
   3. Hyrax 2.1 Release Update (Steve Van Tuyl et al.):
      1. 15 open blocking issues: https://github.com/samvera/hyrax/projects/4
      2. QA testing will finish up this week
   4. Hyrax 2.0-stable support? (tamsin woo)
      1. The build has been broken due to bad dependencies whose fixes haven't been backported.
         1. https://github.com/samvera/hyrax/pull/2765
         2. This blocks bug fixes to 2.0-stable
      2. What is the support timeline for 2.0-stable?

1. Notetaker and moderator for next time
   
   1. Notes:
   2. Moderate:
2. After call, this week's notetaker should create the agenda for the next call.
3. If desired, stay after the call to assist in grooming PR backlog

Notes

Information Gathering and Feature Specs

Robinson

• Working with collection sprints
• Document (rather than refactor) for feature specs
  • Pull them out into a separate route
  • Linked to Documentation WG
  • Created an issue in response to these needs
  • Easier to publish a page outlining the feature spec. refactoring proposal
  • Collaborated with Giarlo and Rayle
• Rayle
• Basic proposal is that the feature tests woiuld be extracted out of main test suite
• Own