Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Pattern idea: Scoring Grid

Open
#351 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
content, documentation

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.

Description

:book: Type - Content Work

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
Dominant language
HTML
Stars
853
Forks
206
Avg merge
1d 23h
Merged PRs (30d)
2

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.

More from InnerSourceCommons/InnerSourcePatterns

All issues in InnerSourceCommons/InnerSourcePatterns

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.