GitHub milestones?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 229
- PR merge metrics
- No merged PRs in 30d
Description
Would GitHub milestones https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/about-milestones ease the long time coordination of project initiatives?
Making the long term goals transparent would also help to:
- enable people to contribute in a controlled manner (aligned with your long term goals)
- enable people to estimate how good long term goals align with internal needs (which could be different and would require forking)
Long term goals do not have to be created as github tasks + assigned to github milestones. Alternatively they could be stated in some Roadmap section in the README.md e.g. This would not allow people to have the link to the implementation state however.
@izar What do you think about this topic?
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 by reading the linked GitHub milestones documentation and the repository's README.md, then review the issue discussion about coordinating long-term goals. The issue presents milestones and a Roadmap section as alternatives but does not define a chosen approach or concrete completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100