Page Comparison

...

• Heather Greer Klein

• Lynette Rayle

• Kevin Kochanski

• Juliet Hardesty

• Maxence Gévaudan

• Maria Whitaker

• Jeremy Friesen

• Kiah

Agenda

• Additions to the agenda?

• Updates

  • Pledge process so far

  • Fall Dev Congress

• Progress on our goals:

  1. Goal: A process and schedule for multiple Development Congresses to be held at regular intervals every year 

     • We have a 4x a year schedule and a template for holding them

     • How to ensure there is always a lead facilitator?

     • Other work to do for this goal?

  2. Goal: An evaluation of current contribution culture strengths and weaknesses

     • Completed

• Goal: develop new contributor support practices, including new practices for highlighting successful contributions and contributors and regular opportunities for new contributor support

  1. Completed or making progress on:

     1. Created maintenance pledge process

     2. Identified need for Community-managed training and improved onboarding processes

     3. Hyrax maintenance working group tasked to review one-off PRs

     4. Streamline the CLA as much as possible (still in atty review)

     5. Tried/are trying a 30 min session for newer devs

        1. Low uptake on facilitation so far

        2. Other ideas for this need?

  2. Other items identified in our evaluation:

     • Automate the CLA checking process

     • For plugins: There are call-backs. Could this be leveraged for some extensions? May not be well known. Could documentation help with this?

     • PRs across all Samvera repos reviewed in the weekly tech call?

     • How do we grow the pool of people who feel comfortable making a review? Could there be two levels:

       • first level review to capture obvious problems and provide feedback;

       • second level review by product owners/tech leads and other's with a lot of experience in the code

     • There is documentation that is a checklist for PR review. Is there a way to automate any of this?
       https://samvera.github.io/pr-checklist.html

     • Can we identify the major functional areas (e.g. collections, search builders, presenters, etc.)? Then developers can build expertise in a functional area, allowing them to feel more comfortable reviewing PRs in that area. First step would be to list out the functional areas and then identify a 'functional lead' for each area. This would reduce the cognitive load of trying to understand all the components.

     • Documentation on patterns can help educate new contributors/improve onboarding

     • make PR review better by being more positive and going a little way out on a limb to get the first one or two in. Shift the mindset from "why should this be accepted" to "how can we help you get this accepted"

  3. Next steps for this goal?

• Goal: A set of recommendations to Partners based on the above work, including but not limited to recommendations for practices and actions that require commitment from the institutional leadership level 

  • Can present this at the Partners Meeting Oct 12-13

    • Presenter

    • Draft presentation

• Goal: The group will present their work at Samvera Connect 2021 and sunset after that presentation

  • Presenter

    • Draft presentation

• Do we need another meeting?

• Onboarding Working Group to continue with some of this work?

...