Child pages
  • Samvera Tech Call 2019-09-18
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: Julie Allinson

Notetaker: James R. Griffin III

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. Hyrax 3.0 release process (Tom Johnson)
    3. Wings updates (Tom Johnson )
  3. Moderator & notetaker for next time
    1. Moderator: 
    2. Notetaker: 
  4. After call, this week's notetaker should create the agenda for the next call:
    1. Open template agenda titled "Samvera Tech Call 2019-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: 2019
    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.
  5. PR Review
    1. Review issues:
    2. PR review coordinator for next time: 


Notes


Hyrax 3.0 Release Process

  • RC1 was released last week
  • There will definitely be an RC2
  • There is an ongoing QA process
    • A few notable things are in for RC2, most significantly a Valkyrie upgrade
    • There are a couple of other items which are expected to be closed out in the next cycle of the Hyrax WG
      • Starts in 12 days (a week from Monday)
  • At least 3 weeks from today until 3.0.0 release
    • Encourage those with Hyrax 2.x apps or on the 3.0 beta releases to try the upgrade
    • Please help with the release notes if you are available

Wings Update

  • Tom sent out an FAQ as a follow-on to the RC1 release
  • Addressed the relationship between Valkyrie and Hyrax 3
    • Since then, more substantial Wings work has been merged
    • Application-facing patterns and features have been finished
  • With that work progressing, there is a new Valkyrie usage guide for Hyrax
    • Primer for those interested in playing with Wings as a part of their app.
      • This is on the Hyrax Wiki
    • This is something which one can do, but this is still is in its experimental stages regarding support
    • Please take care to ensure that you are testing that your data is properly persisted


Next Call

  • Moderator: LaRita 
  • Notetaker: Thomas Scherz


Tech Call concluded at 09:10PDT/12:10 EDT


Hyrax Pull Request Review Session

Attendees:

  • Chris Colvard
  • Tom Johnson
  • Gordon Leacock


Pull Request 3996

  • README improvements
  • Chris approved of those changes


Rails 6 pull request is just a placeholder

Wings pull requests are ready for review, but other PRs are not ready


3969

  • Requires some additional attention
  • Build cache in CircleCI does not have 2.x/3.x separated by the cache key
  • This might be a good change to introduce in the CircleCI Orb
  • Wants to load sass-rails 5, but sass-rails is locked at 6
  • It is possible that backporting a CircleCI config. is needed


3945

  • Requires a bit more work or a test restart
  • Intermittent failure is what was blocking the tests from passing
  • Tom had some comments, requested to approve it as a result
  • It may still need to be rebased
  • Also request that the commit message be improved


4012

  • Pretty significant step on the migration of models away from ActiveFedora
  • Might be worth offering this for review by those uninvolved in the Wings work
  • hyrax-valkyrie Channel:
  • Names for classes `QueryServiceBook` and `QueryServiceImage`
  • Should namespace `Book` vs. `BookResource`
  • There were also errors in code documentation for the examples


There are ActiveFedora pull requests which also require review

ActiveFedora 13.1.0 release would be ideal


Pull Request review session concluded at 09:29 PDT/12:29 EDT


  • No labels