...
...
...
...
...
...
...
Scope & Objectives
This is Originally intending to serve as the fifth, recurring, phase of this working group, seeking to continue the Core Component Maintenance Working Group, this Interest Group seeks to continue the efforts undertaken by Phase 4 (and previous phases) of the CCMWG in seeking to collectively labor to ensure that Samvera Community projects are well maintained for active use.
This Interest Group seeks 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
Objectives
Proposed Deliverables:
Review and update Core Components list http://samvera.github.io/core_components.html
Deprecate relevant projects in the samvera GitHub organization to samvera-deprecated
Ensure the projects in the Samvera GitHub organization meet the standards to be there as defined at http://samvera.github.io/samvera_labs.html
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)
Run a yearly dependency report against Partner repositories to help support deprecation, promotion, and prioritization.
- Identify 1
Identify 1 member from the group to represent them on the Samvera Roadmaps Alignment Group
Respond to any security alerts
Review successes and failures of the group
to review and renew charter, with the intention of defining a process for continuous, annual component project maintenance.
Provide
aan annual 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. "
2020Component Technical Health Report"
...
Resources
GitHub Repositories (Samvera)
GitHub Repositories (Samvera Labs)
Documentation
Ruby Maintenance Information (https://www.ruby-lang.org/en/downloads/branches/)
Rails Maintenance Policy (https://guides.rubyonrails.org/maintenance_policy.html )
Meeting Times & Communication Channels
Meetings times are to be determined using a Doodle Poll
URL: To be determinedHeld Weekly on Thursday at 09:00 PDT/12:00 EDT/16:00 UTC
URL: https://princeton.zoom.us/j/7739591625
Anchor | ||||
---|---|---|---|---|
|
James Griffin (Princeton University Library) (Chair)
Please add your name here
Meeting Notes
Community Sprints
(No sprints have been held)