Alpha-Omega minor inconsistency
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 152
- Forks
- 86
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 9
Description
We seem to have some minor inconsistencies regarding our description of Alpha-Omega (among other things).
This slide:
https://docs.google.com/presentation/d/1ZQ7WjNH5fQL7qvpFN3jTFt-iQHqPpUc5of_azQc8iic/edit
has Alpha-Omega listed as an "associated project" reporting directly to the TAC.
https://github.com/ossf/tac lists Alpha-Omega as an "affiliated project", I think that's old terminology, and it should be an "associated project".
https://github.com/ossf/alpha-omega doesn't say anything, it probably should.
This isn't world-ending, but it'd be good to have consistent terminologies.
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
Review the TAC page, the Alpha-Omega repository description, and the linked presentation for how Alpha-Omega is described. Align the terminology on the referenced project pages and add the missing description where appropriate, then verify that all references consistently use “associated project.”
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100