django-commons / django-commons/controls
Identify projects needing maintainers
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- Avg merge
- 18m
- Merged PRs (30d)
- 1
Description
If a project is identified as needing maintainers, the organization should identify that publicly. It could also help with recruitment.
Regarding identifying, if a project needs a maintainer, we could automate a check that looks for a release in the last 9 months.
Regarding recruitment, it might be possible to get the project listed in the Django News newsletter. Or we could post to the Django Forum.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are identified in the issue. First clarify how a project is judged to need maintainers, how the nine-month release check should work, and which public recruitment channel is in scope; done should include an agreed process or implementation with a clear way to identify and publish the projects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django
- Domain
- content, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100