Samvera Tech Call 2022-02-16

Owned by Chris Colvard
Last updated: Feb 16, 2022 by Anna Headley
2 min read

Meeting Logistics:

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)

  • Solr Support Group (@Thomas Scherz)

  • Bixby’s future (@Chris Colvard)

    • Should we upgrade to rubocop 1? https://github.com/samvera-labs/bixby/pull/57

      • E.g. Hyrax offenses on bixby rubocop1 branch:

      • Should we promote bixby from labs to core?

      • Line character limit of 120 ( )

      • Can we turn off DisabledByDefault so we get all of the standard cops instead of just those enabled by bixby?

        • E.g. Hyrax offenses on bixby rubocop1-plus branch:

    • Should we ditch bixby for standard?

      • E.g. Hyrax offenses on standard:

    • Is there a lighter-weight way to having a community style guide without maintaining a gem?



Moderator: @Thomas Scherz

Notetaker: @Max Kadel

Attendees:

  • @Chris Colvard (Indiana University)

  • Anna Headley (Princeton University)

  • @Max Kadel (UNC Chapel Hill)

  • @Thomas Scherz

  • @Lynette Rayle



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 2022-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: 2022

      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

Solr 6 to 8 upgrade notes

  • Symlink current version to /opt/solr - how would solr know which version to start?

    • Anna Hedley’s suggestion - set up a separate box with Solr 8, and then cut over

    • Update solr restart script (system cutl script)

    • - changes in schema and config (not in production - for 8.9 right now, which is vulnerable to log4j)

    • Backups!

    • Dissuade the double-solr setup - leads to a non-standard Solr install

 

Bixby

  • Is there an easy way to compare the ruleset of Standard to the Bixby ruleset?

  • Carrying over for next week