2020-06-23 Meeting notes

Date

23 Jun 2020

Attendees

• Nabeela Jaffer

• Rob Kaufman

• Mark Bussey
• Jon Cameron
• jen young
• Kate Lynch
• James Griffin
• Richard Green
• Simeon Warner
• Carolyn Caizzi
• Chris Awre
• Rosalyn Metz
• Jon Dunn
• Hannah Frost
• Robin Lindley Ruggaber
• John Weise

Goals

• Meeting with Steering to review the purpose and objectives of the Roadmap Council

Discussion items

Notes

Introduction

• Goal is to talk a bit about two topics
  • The recurring theme of Roadmap Council - what it is expected to do vs. what it is really chartered to address
  • If the council is doing what it is chartered to do, then how do we communicate this to the community?
  • Charter is not to create a single roadmap for the community, but instead to try and align various efforts within the community

Roadmap Council Purpose and Goals

• When the Council started, this was chartered to bring together representatives for service providers, representatives from interest groups, and working groups to align project goals
  • Coordinating and communicating regarding community sprints was also a significant undertaking of this group
  • Every IG and WG defined their documents differently - the Roadmap Council first saw to try and standardize this by offering templating
  • Beyond this, there was a whitepaper published addressing the state of the technology in the community
  • Roadmap Council meets every two weeks
• Project Management and Community Sprints
  • This Council was chartered to assist with managing and aligning these
  • 2020 saw an entire year of activity, along with a retrospective
    • Three Goals:
      • Analysis of roadmaps and planning cycles
        • The results of this will be presented during the next Partner Call
      • Facilitating to get code back into core
      • Communicating with the community at large
• When we discuss facilitating contributing to core, is this murky or problematic?
  • If so, what are the obstacles?
  • It comes with challenges given the size of the community, and it will never be trivial
    • There have, however, been real successes
    • User management pieces in Hyku were extracted into a Gem and shared with Hyku and Avalon
      • Who contributed to this?
        • Avalon Team contracted with Notch8, Northwestern paid for the feature with grant funding
      • Roadmap Council makes these efforts known, and interested parties could request involvement and contribute funding or resources
      • The Roadmap Council identified the requirements for work in this case
      • Another Feature: DataCite Integration
        • All community members with this requirement produced a solution for this independently
  • Some assumed that the Roadmap Council is to coordinate rather than create a roadmap
    •  To what extent should the Roadmap Council invest in aligning IG/WG roadmaps and project roadmaps?
    • What of individual institutions and their roadmaps for custom Samvera repositories or local Samvera projects?
    • Community Manager is supposed to be a member of the Roadmap Council
      • They are responsible for representing the interests of individual institutions and their roadmaps
      • Community Manager clarifies that there might be similar functional requirements for different Samvera projects undertaken by different institutions

Action items