theupdateframework / theupdateframework/community
Label repositories with maturity and other attributes.
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 9
- Forks
- 8
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
We should label the repos in the org with information about the maturity and other aspects (experimental, etc.)
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
The issue does not name files, tests, or entry points. Start by reviewing the repositories in the organization and determining which maturity and other attributes are needed. Done means the repositories have an agreed, consistently applied set of labels.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100