InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
InnerSource @ Intuit | InnerSource Repository Scanner
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
The project description of https://github.com/intuit/innersource-scanner is:
A java api and command line tool for scanning, reporting and fixing a git repository's InnerSource Readiness based on a supplied specification which defines the files and file contents necessary for a repository to be considered ready for InnerSource contribution.
I am wondering if this idea represents an entirely new pattern, or if it is tooling that might any of the existing patterns?
Might be related to Standard Base Documentation or Good First Project for example?
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 reviewing the InnerSource Repository Scanner description and comparing its stated scanning, reporting, and fixing capabilities with the linked Standard Base Documentation and Good First Project patterns. Done would be a documented decision on whether it represents a new pattern or fits an existing one, with the relevant pattern relationship recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100