Proposal to remove OSPS-LE-01.01
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 166
- Forks
- 44
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 13
Description
Removal Suggestion
OSPS-LE-01.01: While active, the version control system MUST require all code contributors to assert that they are legally authorized to make the associated contributions on every commit.
This is going to be true for nearly every project. For example, any contribution on GitHub requires this per https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#6-contributions-under-repository-license and I expect other platforms to have similar language. I would stay out of this as I don't think contribution litigation is of sufficient (if any) volume to represent an availability threat to projects.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating OSPS-LE-01.01 in the security baseline and review the linked GitHub contributions policy. Compare the requirement with the stated rationale and project context; the work is done when the proposal has a documented disposition and the baseline reflects that decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 30/100