This wiki space is archived.

The active wiki for the Samvera Community can be found here:

Child pages
  • Samvera Tech Call 2018-05-02

This wiki space is archived. The active wiki for the Samvera Community can be found here:

Skip to end of metadata
Go to start of metadata

How to connect: (link will launch Zoom client – if you do not have Zoom, expand the instructions below)


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:


Meeting ID: 613 720 745 (US West) (US East) (China) (India) (EMEA) (Australia) (Hong Kong) (Brazil) (Canada)


Time: 9:00am PDT / Noon EDT

Moderator: Kevin Musiorski

Notetaker: Glen Horton



  • Roll call by timezone per following order - ensure notetaker is present (moderator)

    • folks outside North and South America

    • Eastern timezone

    • Central timezone

    • Mountain timezone

    • Pacific timezone

    • folks who were missed or who dialed in during roll call

    • Welcome all newcomers!
  • Agenda (moderator)
    • Hyrax 2.1.0 update (tamsin johnson)
      • 2.1.0.rc1 was released last week
      • Going through the pre-release QA process.  Tickets to deal with new bugs are in progress.
      • There's still potential for more bugs to emerge.
      • RC2 may be released next week.  Followed by final release late next week or the week after.
      • Tom encouraged people to test on their end.
    • ActiveFedora and Rails 5.2 (Chris Colvard)
      • Rails 5.2 changed the ActiveModel::Dirty API.  This is causing problems with ActiveFedora.
      • Chris would like people to look over his PR.  Other gems like hydra_works are also failing until AF is fixed.
    • Remove relic git tags from Hyrax (leftover from Sufia, right?) We are about to bump into tags for 3.x. (Andrew Myers)
      • Old tags from the Sufia days have been deleted a couple of times, but they keep coming back.
      • People are likely accidentally pushing old tags up when they push a legitimate tag.
      • We will soon need a 3.0 tag for Hyrax, but there's already a 3.0 tag from Sufia.
      • An information campaign might be the best approach to resolve this.
      • We should make sure the Hyrax release process describes how to push tags properly (only one specific tag).
      • Idea: use the gemspec to get the current version and check for tags that are higher than that version.
    • Call for new agenda items (moderator)
  • Notetaker and moderator for next time
  • After call, this week's notetaker should create the agenda for the next call.


  • No labels