Public Article
How Do Mentorship Milestones Work in Open Source?
Mentorship milestones work by breaking open-source contribution into visible steps. A milestone can define setup, first pull request, review response, deeper project work, or completion criteria. The point is to make progress and collaboration easier to see.
What should a milestone contain?
A useful milestone is specific enough to guide work but flexible enough for real project feedback.
- Goal
- Repository context
- Acceptance criteria
- Expected pull request scope
- Review expectations
- Evidence captured when complete
How are milestones different from tasks?
A task is usually a unit of work. A milestone describes progress in a program. It can include multiple tasks, review cycles, and communication expectations.
| Task | Milestone |
|---|---|
| Fix one bug | Complete first contribution path |
| Update one component | Demonstrate codebase orientation |
| Respond to one comment | Show feedback response pattern |
How do milestones support mentorship?
Milestones give maintainers a clearer way to guide contributors. They also give developers a clearer way to show how they handled feedback and improved.
Without milestones, good mentorship can disappear into scattered comments and private context.
How does Devprentice fit?
Devprentice is a beta platform designed to connect milestones, GitHub work, review response, and public collaboration records. The process page, developer beta, and maintainer beta pages explain how the model is intended to work.
Any public example before approved real programs exist should be labeled as sample, demo, or example.