Summer 2020 Community Sprint Planning Meeting

Date: 06/08/20

Time: 12:00 PDT/03:00 EDT -01:00PDT/04:00EDT

Zoom: https://princeton.zoom.us/j/7739591625

Participants

• @James Griffin (Princeton University Library)

• Rachel Kadel (Data Curation Experts)

• @bess (Data Curation Experts)

• @max (Data Curation Experts)

• @Randall Floyd (Indiana University)

• @Jeremy Friesen (University of Notre Dame)

• @Collin Brittle (Emory University)

• Dylan Salay (Notch8)

• Kait (Notch8)

• Shana Moore (Notch8)

• @tamsin johnson (UCSB)

• @JP Engstrom (Notch8)

Agenda

• GitHub Board Review Column

  • @James Griffin is looking to be available to walk with people through the onboarding tasks.

  • For onboarding tasks we want to follow the guidelines, stepping through those, and then ensure the documentation reflects the process. https://samvera.github.io/core_components.html

  • We won't be tracking daily stand-ups, but plan to have a retrospective

  • The Core Maintenance sprint is for this week (2020-06-08 to 2020-06-12)

Notes

• Onboarding Issues

  • Should not be used for changing the website

  • James would like to propose an onboarding session, but create separate documentation issues

    • Want to avoid pressuring anyone to take on documentation issues

• James can proceed with schedule onboarding meetings tomorrow

  • jrgriffiniii [at] gmail.com

  • There may be several groups for this

• Pairing Sessions

  • Rails and Ruby CircleCI configuration

  • Pairing Sessions for CircleCI

• Backporting

  • Code from one version and backporting these to older releases of the Gems

  • One example: https://github.com/samvera/active_fedora/issues/1392

• Pairing Up

  • One long-time contributor and two new-time contributors

  • Fixing build matrices as an example, find a time on the calendar, anyone who wants to join me, here is the Zoom link

  • Junior collaborators: find someone

  • Senior collaborators: find tickets, get them on the calendar, and lead someone through it

• Licensing

  • Everyone belongs to an organization with an active CLA

Calendar

For the person scheduling the work, announce on the Slack channel when work is going to happen.