Child pages
  • Samvera Tech Call 2018-02-21
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: steve van tuyl

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. Welcome all newcomers!
  2. Agenda (moderator)
    1. Call for new agenda items (moderator)
    2. Call for participants for Code Stability Working Group (Jennifer Lindner)
    3. 2.1 release update (Julie Rudder)
      1. Blockers for beta release and testing are: 
        1. Getting UV/IIIF installed on nurax
        2. Completing the "pre-test" (Julie and Chris D are working on this)
      2. Bugs
        1. CE bugs - top 4 (Lynette Rayle)
          1. Issue #2672 - Collection type creation loses settings if you add a participant before a save.  (moderate effort)

          2. Issue #2602 - Collections filter on Dashboard -> Works only shows admin sets  (moderate effort)

          3. Issue #2279 - Add an "add to collection" button on work showpage (moderate effort)

          4. Issue #2603 - admin sets should have the same icons as collections  (minor effort)

        2. Non-CE related bugs - Julie will call for help in slack and on tech calls
        3. 2.1 milestone has bugs reported and ready for people: https://github.com/samvera/hyrax/milestone/13
    4. Valkyrie Sprint Next Week (02/26/18 - 03/02/18) (Trey Pendragon)
      1. Sprint Planning Call After Tech Call: https://princeton.zoom.us/j/818692566
    5. Release QA 2.0.1 which includes a bug fix (Lynette Rayle)
  3. Notetaker and moderator for next time
    1. Notes:
    2. Moderate:
  4. After call, this week's notetaker should create the agenda for the next call.
  5. If desired, stay after the call to assist in grooming PR backlog

Notes

Call for Participants (Code Stability WG)

  • Coming out of recent discussion
  • Aspirational hope for processes
  • Backwards compatibility smoother
  • Guidelines for changing this
  • Short-lived...and benefit the community
  • Try to come up with some stuff...in the quickest amount of time
  • Invitation to all members of the community
  • Ideally, would address all of the Samvera Gems

2.1 Release Update

  • Two blockers for getting this done
  • Big testing by Monday
  • Rayle is going to be contacting collections-related bugs
  • Rudder will be contacting others for non-collections related bugs
  • https://github.com/samvera/hyrax/milestone/13
  • Invitation for any contributions
  • Rayle posted some top issue with no assignees
  • Contact Rayle on Slack for more information if you wish to contribute

Valkyrie Sprint Next Week

  • If you're interested in joining the sprint, please attend the call after this one
  • https://princeton.zoom.us/j/818692566
  • Identification of tickets being scoped for the sprint
  • Also, please join the #valkyrie Slack Channel if you wish to join the sprint later

QA 2.0.1

  • There was a bug in some of the linked data processing fixed by Rayle
  • Wants to offer a bug-fix release for QA
  • If anyone has questions, please contact Rayle
  • Please note that the configuration for encoding was updated
  • If you had a parameter which needed URL encoding...no way to configure this processing in the Gem
  • Now, it defaults not to encode (for backward compatibility)
  • If you're interested in trying out linked data authorities, Rayle can direct you to documentation


  • No labels