/
Hydra Tech Call 2017-04-05

Samvera Community Wiki

Hydra Tech Call 2017-04-05

Jun 16, 2017

 

Time: 9:00am PDT / Noon EDT

Call-In Info: 1-641-715-3660, access code 651025

Moderator: @Jeremy Friesen

Notetaker: @Steven Ng

Attendees: 

  • @Steve Van Tuyl (oregon state)

  • @Former user (Deleted) (University of Alberta)

  • @Leah (University of Alberta)

  • @Aaron Collier (California State)

  • @cam156 (Penn State University)

  • @Steven Ng (Temple University)

  • @Esmé Cowles (Princeton)

  • @Jeremy Friesen (Notre Dame)

  • @justin (Stanford University)

Agenda/Notes

  1. Roll call by timezone per following order - ensure notetaker is present

    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

  2. Call for additional agenda items (moderator)

  3. Approaching Code Review with Compassion (Jeremy Friesen)

    1. How do we ensure that we are welcoming contributions? Examples of positive code review experience? How to replicate that. (http://www.zeespencer.com/effective-code-critique/)

      1. Due to concerns about people afraid of harsh critique when submitting contributions.

      2. We should address it directly and add it into project documentation.

      3. Would be a good pre-conference session for Hydra Connect - Expectations of new contributors and providing constructive code review comments.

      4. Partners desire healthy environment for community contributions.

      5. Short comments, due to shared time with other work, may come across as sounding harsh.

      6. Pull Request reviews - feel free to ask how to do something if you're not sure how.

  4. Protocol for getting broader community input for big decisions (@Esmé Cowles)

    1. We do good on Slack, tech call, partners meetings, etc, but not able to get people's attentions who aren't regulars on these channels.

    2. Suggest from LDCX - Add tags to indicate feedback needed.

    3. @Esmé Cowles will add something to the Wiki page.

    4. Growth of community has made it more difficult to communicate.

  5. (STANDING) Update on Sufia/CurationConcerns Consolidation Plan (@justin or @Michael Joseph Giarlo)

    1. Vote on a release of Hyrax 1.0?

      1. Tacitly approved: Release It!

    2. Upgrade guide would be good to have before release.

      1. Changes needed to upgrade from Sufia are in the release notes.

      2. As upgrade issues are found, please amend the release notes or engage with someone on Slack.

  6. Moderator/notetaker for next time:

    1. Moderator: @Steven Ng

    2. Notetaker: @Steve Van Tuyl