⚖️ get real about license guidance in contribution guidelines
Open
Nobody has claimed this yet.
claimed
content
documentation
markdown
question
wip
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 23h 54m
- Merged PRs (30d)
- 29
Description
The contribution guidelines surrounding licensing are too simplistic and unclear.
This is also not the whole story about what we currently do. Expand and clarify.
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
Open CONTRIBUTING.md in the OpenINF/.github repository and start at lines 77–79. Review the surrounding contribution and licensing guidance, then verify the current licensing practices referenced by the organization. Done means the guidance accurately reflects those practices and is clearer and less simplistic for contributors.
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
- 45/100