Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


Scope & Objectives

This is to serve as the fifth, recurring, phase of this working group, seeking to continue the ongoing maintenance of identified core components in the community, via planned sprints and communication with product owners. Work for these features on components is considered out of scope. Working group members will plan and participate in these sprints, as well as communicate that planning and welcome contributions from the larger community. The core components supported for this phase are identified within the following: http://samvera.github.io/core_components.html.  It should further be noted that our efforts shall be coordinated with the appropriate Samvera governance bodies.

During the sustaining phase of this working group, the group will re-evaluate the WG charter on a yearly basis roughly aligning with Samvera Connect in a time, to be determined, in the summer or autumn of 2022.


Deliverables & Timeframe

Deliverables:

  1. Review and update Core Components list http://samvera.github.io/core_components.html

  2. Deprecate relevant projects in the samvera GitHub organization to samvera-deprecated
  3. Ensure the projects in the Samvera GitHub organization meet the standards to be there as defined at http://samvera.github.io/samvera_labs.html
  4. Promote relevant projects from samvera-labs to the Samvera github organization if they meet the requirements (or make them meet the requirements if they should)
  5. Run a yearly dependency report against Partner repositories to help support deprecation, promotion, and prioritization.

  6. Identify 1 member from the group to represent them on the Samvera Roadmaps Alignment Group

  7. Respond to any security alerts
  8. Review successes and failures of the group to review and renew charter.
    1. Provide a written report on the status of core components in regards to Ruby/Rails compatibility or any security/technical issues we've been able or unable to deal with. "2020 Technical Health Report"

Timeframe: 1 year


Meeting Times & Communication Channels

Meetings times are to be determined using a Doodle Poll
URL: To be determined


Current Members

  • James Griffin (Princeton University Library) (Chair)
  • Please add your name here


Meeting Notes

  • To be determined

Community Sprints

  • (No sprints have been held)


Previous Phases


  • No labels