InnerSourceCommons / InnerSourceCommons/managing-innersource-projects
Use the learning path author extraction tooling
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 15
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Hi, some good stuff around here.
Saw that you're attributing authors and reviewers, but apparently manually.
"This section was drafted as a discussion starter and is open for contributions. If you would like to be listed as an author or reviewer, please open a pull request or get in touch via Slack." says https://innersourcecommons.github.io/managing-innersource-projects/innersource-and-ai/authors.html
The learning path had the same issue for its rendered version and @tsadler1988 had built automated & reviewer author extraction tooling using the GH API & commit info back when. That might come in pretty handy here. Probably some changes required, but those shouldn't really be an issue given that @claude is working here too.
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 with the authors.html page and the learning path's rendered version to identify where authors and reviewers are currently attributed. Then locate the existing author-extraction tooling built by @tsadler1988, including its GitHub API and commit-information inputs. Done means the learning path uses that tooling to extract and display authors and reviewers automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100