[New Process Improvement Need]: Guidance on GitHub organization / sub-projects
Open
Nobody has claimed this yet.
governance
low complexity
more requested
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Checked for duplicates
Yes - I've already checked
Category
Software Lifecycle - the creation, change, and release of software
Describe the need
We have a need for guidance on overall structure of GitHub Org and sub-projects (+1'd by @kgrimes2 @mcduffie @galenatjpl)
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 guidance request in issue #45 and review the repository’s existing software-lifecycle and governance context. Done means documented recommendations for structuring the GitHub organization and its sub-projects, with scope clear enough for the listed stakeholders to review.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100