Page Comparison

Scope & Objectives

...

Charter:

The Roadmaps Alignment Group exists, as much as possible, to minimize conflicts Group (formerly called "Samvera Roadmap Council") works to identify conflicts and areas of alignment between the roadmaps of the of the Core Components Owners Owners, Hyrax, Hyku, Valkyrie, and Avalon. This group works in consultation with the Metadata Interest Group, the Repository Management Interest Group, and a Samvera Service Provider, while allowing the individual work-streams to progress at their own pace.  They will identify when Providers. The Group identifies cross-project development and opportunities, helps to arrange maintenance sprints need to be arranged and coordinate , and coordinates communication to the Samvera Community about these activities.  This group is chartered per the Governance Recommendations adopted by the Samvera Partners in April 2018.  More information about the Roadmaps Alignment Group can be found in Recommendation #4 of the Samvera Governance Next Steps document.

...

Meetings will be held at least monthly via conference call/video chat.  Meeting agendas and notes will be shared with the community via chat (Slack) and Samvera Lists (Google Groups).  Members of the group may wish to meet more often than monthly as needed.

...

...

Meeting Frequency: Biweekly

...

URL: https://northwestern.zoom.us/j/733419043 

Phone one-tap: US: +13126266799,,733419043# or +19294362866,,733419043#

Dial:  US: +1 312 626 6799 or +1 929 436 2866 or +1 301 715 8592 or +1 346 248 7799 or +1 669 900 6833 or +1 253 215 8782

Meeting Information

Roadmaps Alignment Group meets biweekly on Tuesdays at 11AM CST biweekly on Mondays at 2pm Eastern starting August 8, 2022

Slack: #roadmap-alignment

Chartered: October 2018

Facilitator:

...

rotating

Meeting Notes

Please see the Meeting Notes and Agendas

Members

In order to facilitate communication with various entities within the Samvera community, the initial membership of this group is pulled from Group includes the following placesCommunity Roles:

• Product owners of the current

  solution bundles

  technologies (Avalon, Hyrax,

  and

  Hyku, Valkyrie)

• 2 Representatives from the Core Components Maintenance Working Group

• 1 Representative from the Metadata

  Interest Group1 Representative from the Repository Management

  Interest Group

• 1 Representative from a Samvera Service Provider

• The

...

• Samvera Community Manager

The current membership of the Roadmap Council is:

• Jon Cameron – Product Owner

  for

  for Avalon

• Juliet Hardesty

  Rebekah Kati – Product Owner for Hyrax

• Rob Kaufman  – Product Owner

  for

  for Hyku

• Mark Bussey – member of Components Maintenance Working Group

• James Griffin – member of

  Components Maintenance Working Groupjen young – representative for the Metadata

  Component Maintenance Interest Group

• Nabeela Jaffer

  Juliet Hardesty – representative for

  the Repository Management

  the Samvera Metadata Interest Group

• Julie Allinson – representative for Service Providers
• Kate Lynch 

  Alexandra Dunn - representative for Valkyrie

Former members:

• Benjamin Armintor – member of Core Components Maintenance Working Group
• Steve Van Tuyl  – Product Owner for Hyrax

Meeting Notes

Please see the Meeting Notes and Agendas

Roadmaps

• Hyrax Roadmap (looked after by SIGHAR)
• Hyku Roadmap (looked after by the Hyku Interest Group)
• Avalon Roadmap (looked after by the Avalon team)

  Heather Greer Klein - Community Manager

The Group itself and/or the Samvera Steering Group may recommend adjustments to the membership to reflect changes in the community.

Samvera White Paper

• State of Samvera Technology in 2019

What We're Working On

• Community Feature Requests and Roadmap Planning

  • pulling

    Pulling together feature requests and developments from across the community to feed into roadmap planning for Samvera components and solutions

  • identifying

    Identifying community pain points that require community action

  • coordinating prioritisation of features

• Resourcing

  • coordinating

    Coordinating requests for community resourcing to deliver solution roadmaps and specific features

  • a time-limited exercise to look at how to better facilitate and sustain community resourcing, looking at:

    Identifying barriers to code contribution

    ,

    and to joining feature sprints

  • Exploring what adopters are already doing that might become community features

•  Communications

  • communicating into the work of the Council

    Communicating ongoing work from the groups we represent

  • communicating out from the Council to raise awareness of what's going on across the Samvera grass-roots community
  • a Samvera White Paper

    Communicating to the wider Community about resourcing, activities, and opportunities for collaboration

• Samvera Maintenance Issues