getsops / getsops/sops

[CNCF TOC] Health Issue - SOPS

Open
#2,244 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
23.1k
Forks
1.1k
Avg merge
1d 11h
Merged PRs (30d)
9

Description

Hello project maintainers 👋,

I'm creating this issue to highlight ongoing discussion around a health issue from the CNCF. Largely the current objective is to move forward on discussions around licensing and determine the next steps.

Separately I believe this would then provide a fork in the road for closing out remaining items in the onboarding issue.

Any and all input/context is appreciated.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked CNCF TOC health issue 2098 and the SOPS onboarding issue 157 to understand the licensing discussion and outstanding onboarding items. Done means the licensing next steps are agreed and the remaining onboarding work is identified for closure.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.