Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »


Meeting Logistics:

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

Meeting ID: 773 959 1625

One tap mobile

  • +13017158592,,7739591625# US (Washington DC)

  • +13126266799,,7739591625# US (Chicago)

Dial by your location

  • +1 301 715 8592 US (Washington DC)

  • +1 312 626 6799 US (Chicago)

  • +1 646 558 8656 US (New York)

  • +1 253 215 8782 US (Tacoma)

  • +1 346 248 7799 US (Houston)

  • +1 669 900 6833 US (San Jose)

  • 888 788 0099 US Toll-free

  • 877 853 5247 US Toll-free


Meeting ID: 773 959 1625

Find your local number: https://princeton.zoom.us/u/abfeKpHD7T

Join by SIP 7739591625@zoomcrc.com

Join by H.323

  • 162.255.37.11 (US West)

  • 162.255.36.11 (US East)

  • 115.114.131.7 (India Mumbai)

  • 115.114.115.7 (India Hyderabad)

  • 213.19.144.110 (Amsterdam Netherlands)

  • 213.244.140.110 (Germany)

  • 103.122.166.55 (Australia Sydney)

  • 103.122.167.55 (Australia Melbourne)

  • 64.211.144.160 (Brazil)

  • 69.174.57.160 (Canada Toronto)

  • 65.39.152.160 (Canada Vancouver)

  • 207.226.132.110 (Japan Tokyo)

  • 149.137.24.110 (Japan Osaka)


Meeting ID: 773 959 1625

Agenda (meeting notes below)


Moderator: Lynette Rayle

Notetaker: Michael Johnson

Attendees:


Meeting Process

 Moderator and Note Taker - click to see meeting process...
  1. Standing pre-agenda items (moderator)

    1. Welcome

      • "Welcome everyone, please add your name to the Attendees list.  If you are unable to do so, please let us know, and someone will add you. To any newcomers, Welcome, and please feel free to ask questions. Likewise for all attendees. We strive for an open and accessible conversation around Samvera technology."

    2. Call for new agenda items

  2. Follow Agenda from above (facilitated by moderator) and record notes in Notes section below (note taker)

  3. Standing post-agenda items (moderator)

    1. call for next moderator and note taker (moderator)

      1. Moderator:

      2. Notetaker:

    2. Samvera help follow-up (moderator)

    3. Pull request review (moderator)

  4. Post-meeting action (note taker)

    1. After call, this week's notetaker should create the agenda for the next call:

      1. Open template agenda titled "Samvera Tech Call 2021-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: 2021

      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

TOPIC: Modernizing Hyrax JS build/package process

Led by tamsin johnson , kibigo

  • Tamsin introduces Margaret Kibi who has been heading up the work on this. New dev at UCSB.

  • Working on Blacklight migration - necessary to get Hyrax onto Rails 6

    • Upgrading Blacklight requires some other changes

      • Upgrading Bootstrap

        • But upgrading Bootstrap breaks some components in our front end

        • Things that need to happen on the frontend and a lot of our infrastructure is out of date

          • Sprockets currently required

          • But Rails in general has moved away from using Sprockets - -a lot of the transpiling/bundling solutions are out of date/not maintained for Sprockets

          • Uses Babel for transpiling, but it uses Babel 5, which was last released in January of 2016 - 7 years out of date

        • We want to move to more contemporary JS development anyway

        • This PR was an exploration in using Deno, which sidesteps a lot of these issues. This allows us to use Rake tasks to build JS bundles

          • JS bundle gets built and added to the view

          • Application JS works the same but gets loaded after ours

        • 2 concerns:

          • Getting Deno to work on Alpine Linux is tricky (no glibc, and Deno needs glibc) - we have a fix for doing it within Docker, but if anyone runs Alpine outside docker, it won’t work out of the box

          • Makes development a little more cumbersome – have to manually run the rake task every time a change is made (not hooked into rails

        • Tamsin: is glibc a runtime dependency?

          • Margaret: no, it’s a build-time dependency. Deno binary uses dynamic linking that requires glibc.

          • You can run Deno binary on another box and copy the bundle over

        • Tamsin: That coupled with fact that we're not married to Alpine linux seems ok

          • Build existing images using Alpine, but that could change

        • Maybe we take a step back and think about building on Debian-based images instead?

          • But this shouldn't be a determining factor for the JS builds

          • Good topic for next Dev Congress - jan 24-28?

            • Tamsin: Can this wait until then?

            • Margaret: Yes.

TOPIC: Hydra derivatives

Led by Chris Colvard

  • hydra-derivatives has some hoops you have to jump through to get build to pass

    • Dependencies on tools used to generate derivatives

    • One is Kakadu

      • Some of the files needed to build were missing, had to find them an alternative way

    • Hydra Derivatives has this as an ongoing problem

    • Suggestions?

      • Trey - like integration tests existing, but don't need to deal with this then

        • In case of Kakadu, we've left it behind and they've been stricter about licensing.

        • But there is not a great alternative

      • Chris: In short term want to cut a release of hydra-derivatives

        • have a PR - dropped testing on Ruby 2.4 b/c EOL and there are issues with the docker images

        • does dropping testing of Ruby 2.4 require a major version bump? Still works but not getting tested

        • Trey: No.

        • Tamsin: strictly speaking it's a nice thing to do but not super important. But sometimes things that are

          • What is downside to dumping major version?

            • Chris - if stricter versioning in gemfiles, will have to bump them to get the new version.

          • Tamsin: Don't feel it's super important either way. Do it how you want.

  • No labels