InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Pattern idea: Scoring Grid
Open
Nobody has claimed this yet.
:book: Type - Content Work
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
Question from the Sept/2021 community call:
Curious to know if we have a source code score/ranking format, which can tell us how much behind we are from being called InnerSource project?
One idea proposed was a scoring grid, that would assign grades (from A-F) for each project based on vectors like:
- README.md
- CONTRIBUTING.md
- LICENSE
- PulL Requests
- CODEOWNERS
- CI
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
Review the proposed README.md, CONTRIBUTING.md, LICENSE, pull requests, CODEOWNERS, and CI vectors in the issue. First establish an agreed grading model and project scope; done means the community has a documented, actionable scoring grid with defined grades for each vector.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100