Components Maintenance Working Group Update

Ongoing Commitment & Assessment for Core Components

Bess Sadler, Trey Pendragon, Tom Johnson, Ben Armintor�Spring 2018 Samvera Partners/Developer Congress Joint Session

Goals of Phase 1 of the working group

• Identify and prepare a list of core components for a second group which will perform maintenance work.
• Identify product owners for each component to better enable the second group to work.
• Audit existing components and their usage to help inform maintenance priority.

(Assess the maintenance capacity of the Samvera community by identifying 6 month custodians and plans for upcoming work on core components. Upon identification of the custodians of each component a second working group will be chartered to undertake the identified work and report on the success of this process as a whole.) (Pull from here?)

Phase I Deliverables

Phase I Deliverables

• Product Owner Role Definition
• Product Owner Selection Process & Roster
• Define requirements for a core component
• Select core components for the group to maintain
• Generate a process for deprecating components and utilize it.
• Audit core components to ensure they meet criteria previously defined.
• Measure use of components amongst Samvera partners.

​

Deliverables put on https://samvera.github.io

Product Owner Role Definition

http://samvera.github.io/core_components.html#product-owner-responsibilities

• Ensure releases are cut
• Own the backlog
• Act as point of contact
• Ensure documentation exists
• Participate as guidance in sprints.
• Report on whether the core component meets criteria to be one.
• Recruit necessary positions for better maintaining the product

Product Owner Selection Process & Roster

http://samvera.github.io/core_components.html#core-components-and-product-owners

• 16 components identified
• Call for product owners for each component was put out to Samvera lists.
• All but three have product owners now.
• If hydra-pcdm, hydra-works, or hydra do not have product owners for Phase II, we will initiate the deprecation process.

Core Components: Definition & Inventory

http://samvera.github.io/core_components.html#requirements-for-a-core-component

• Component is in Samvera github organization and meets criteria to be there.
• Component has a product owner
• Participant of the CCMWG has a vested interest in the component.

Components can be deprecated (not core) and still worked on - they just don’t have support from the CCMWG until enough institutions declare support for it.

Deprecation Process & Sunset Candidates

http://samvera.github.io/deprecation.html

Are three partners still committed to its maintenance at current versions?

Does it have a product owner to assess feature development plans?

Does it have support on the Component Maintenance WG?

Has it been active in this assessment cycle?

Code Repository Audit: What have we got?

What repositories are collected in the github organizations?

When were they last updated? Are they 'released' according to semantic versioning?

Do they have test suites? To what degree of coverage?

How do we estimate the work needed to support them?

What's the Freak Out Factor?

See the audit here.

Dependency Report: What's actually being used?

Discuss report on CSV�Discuss reporting scripts in samvera-labs

Discuss motivations and questions

Phase I WG Process Review

1. Meetings were well attended.
2. Working group process worked out well for this.
3. Deliverables were produced on time.
4. Wrapped up and planned for phase 2 on time.

Future Phases of WG

Phase II Goals and Charter

https://wiki.duraspace.org/pages/viewpage.action?pageId=96994860

1. Perform maintenance of core components via communicated sprints.
1. Current plan is to coordinate with the product owners (who are part of roadmap council?) regarding priority.
2. Deprecate relevant projects
3. Make projects in Samvera organization meet criteria.
4. Promote relevant projects.
5. Respond to security alerts.
6. Review group’s successes and failures and re-charter if appropriate.
7. Charter closes April 27th.

Ongoing Assessment/Report to Community/Partners

Installation/Deployment Audits�Maintenance sprint organization�Product Ownership commitments�Deprecation/Sunset evaluation�Re-constitution of the WG on a rolling basis

Thank you to the Phase I WG Members!

Julie Allinson�Ben Armintor�Noah Botimer�James Griffin III�Tom Johnson�Trey Pendragon�Bess Sadler

Questions