Technical Initiatives Documentation Updates
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 152
- Forks
- 86
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 9
Description
We have completed an audit of the documentation for all current OpenSSF Technical Initiatives, reviewing for Project Lifecycle documents, codes of conduct, security policies, contributing guides etc, for consistency across our projects.
For TIs that had something missing, like a sandbox/incubating/graduated lifecycle doc in the TAC repo, we have opened issues in the respective project's repo.
Here is the list of issues for tracking purposes and for the TAC to review with the respective working groups in their next TAC updates:
- Best Practices Badge https://github.com/coreinfrastructure/best-practices-badge/issues/2538
- Criticality Score https://github.com/ossf/criticality_score/issues/823
- Fuzz Introspector https://github.com/ossf/fuzz-introspector/issues/2259
- Malicious Packages https://github.com/ossf/malicious-packages/issues/1109
- Minder https://github.com/mindersec/minder/issues/6027
- Model Signing https://github.com/ossf/model-signing-spec/issues/7
- OpenVEX https://github.com/openvex/community/issues/22
- OSPS Baseline https://github.com/ossf/security-baseline/issues/454
- OSV Schema https://github.com/ossf/tac/pull/456
- Package Analysis https://github.com/ossf/package-analysis/issues/1125
- RSTUF https://github.com/repository-service-tuf/repository-service-tuf/issues/917
- Security Assessments https://github.com/ossf/security-assessments/issues/18
- Security Insights https://github.com/ossf/security-insights/issues/148
Contributor guide
No contributing guide indexed for this repository
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 reviewing the audit summary and the linked issues for the listed Technical Initiatives, then check the TAC updates with the respective working groups. This issue is done when the tracking checklist reflects the status of the listed documentation gaps and the TAC has reviewed them.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100