Versions Compared

Old Version 4

changes.mady.by.user dmoles

Saved on

compared with

New Version 5

changes.mady.by.user dmoles

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

Expand
titleModerator 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)

      1. Recent Samvera PR list

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

      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

  1. Hyrax PR #6917 & other PRs

    1. How to get pull requests reviewed in general—mention in Samvera slack (#dev, #hyrax, etc. as appropriate), or request review from someone in particular through GitHub (e.g. Daniel Pierce, or whoever seems appropriate)

    2. Daniel Pierce to review Hyrax #6917

  2. Current sprint

    1. Trying to upgrade dependencies:

      1. in particular Bootstrap 5 after Blacklight community brought up security concerns

        1. Bootstrap 5 on Blacklight 7 may be tricky, might lead to needing to upgrade to Blacklight 8

      2. Rails 6.1 → 7.2

    2. David Moles suggests doing the Rails upgrade before Bootstrap first based on past trauma; Daniel Pierce to discuss w/Randall

    3. Q how difficult the upgrade will be for Hyrax apps—hoping to avoid a major release; generated apps will likely need CSS changes at minimum

    4. Chris Colvard reports core components upgraded to Ruby 3.3, Rails 7.2; Valkyrie needs a release and Bulkrax is waiting on Hyrax

      1. ActiveFedora 15 recently released; previously discussed having this be the last major release for Fedora 4, w/Avalon team merging Fedora 6 code into ActiveFedora 16

      2. Q: is ActiveFedora still using CircleCI?

        1. A: yes; all core components are on CircleCI, Valkyrie might be on GitHub Actions

      3. Suggestion: ActiveFedora 16 might be a good time to move to GitHub Actions

    5. Q: should Chris Colvard take over as ActiveFedora product owner from Tamsin? Product owners for core components have kind of fallen off lately

      1. Q: how involved is Tamsin likely to be in this stuff going forward? what about ActiveTriples?

  3. Other UCSB folks

    1. Margaret Kibi to try to come to these more often

    2. Alex Dunn considering stepping back from the Valkyrie product owner role, might be worth looking for someone else

      1. Alex may talk to folks at the northwest meeting

      2. Daniel Pierce will talk to people at northeastern regional meeting, see if there’s somebody who’s familiar with / knows more about the full Valkyrie feature set beyond how Hyrax uses it

  4. PR review

    1. Already discussed Hyrax #6917

    2. Various draft PRs in Hyrax re upgrades

  5. Next week: postpone to 23rd

    1. Chris, Daniel, & Brad will be at northeast regional meeting

    2. Daniel will moderate on the 23rd