-
Notifications
You must be signed in to change notification settings - Fork 699
[HEALTH]: SOPS #2098
Copy link
Copy link
Open
Labels
kind/reviewItem related to a governance, tech, or other reviewItem related to a governance, tech, or other reviewneeds-groupIndicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)Indicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)needs-triageIndicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)Indicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)review/healthProject Health ReviewProject Health Reviewtoctoc specific issuetoc specific issue
Metadata
Metadata
Assignees
Labels
kind/reviewItem related to a governance, tech, or other reviewItem related to a governance, tech, or other reviewneeds-groupIndicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)Indicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)needs-triageIndicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)Indicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)review/healthProject Health ReviewProject Health Reviewtoctoc specific issuetoc specific issue
Type
Projects
Status
New
Status
No status
Status
No status
Status
No status
Status
No status
Project name
sops
Project Health Notification Link (issue, message to mailing list etc)
cncf/sandbox#157
Concern
The SOPS project is active but has some health issues: https://insights.linuxfoundation.org/project/sops
There's also been an issue with licensing and onboarding: cncf/sandbox#157
The TOC should evaluate to see if the SOPS project can relicense away from MPL, if not, the project can potentially be archived or moved to a new home outside of CNCF (e..g, Linux Foundation, OpenSSF etc)
It would also be nice to hear from the community on any hard dependencies on SOPS etc before any decisions are made by the TOC.
Prior engagement
No response
Additional Information
No response
Archiving Checklist (If project is determined for archival)
NOTE: Only applicable if the project opts to self-archive, or is initiated as a last possible option following a TOC vote.
To proceed with the archival checklist, add the
level/archivelabel and assign: caniszczyk, mrbobbytables, idvoretskyi, jeefy, castrojo, krookDetails
Archiving Checklist
PRs
Mailing lists
maturity-level-projects@cncf.io (google groups)Send emails
Other: