Guide
What is an open-source apprenticeship?
A practical definition of an open-source apprenticeship: how it differs from casual contribution, what the maintainer provides, and what the developer practices.
An open-source apprenticeship is a structured way to learn through real work in an existing project. Instead of contributing alone, a developer works through scoped milestones, pull requests, review, and feedback with a maintainer's guidance. What you come away with is not only code: it is the record of how you worked with someone else on it.
How is it different from casual contribution?
Casual contribution usually starts with a public issue and leaves the developer to work out the context. An apprenticeship adds explicit scope, expectations, milestones, and review checkpoints.
- Where the work comes from: instead of finding an issue and trying it, you work from a scoped path of related milestones.
- Feedback: instead of depending on whoever has time, review expectations are agreed as part of the program.
- What you can show: instead of mostly the final pull request, the record includes how you responded to feedback and followed through.
What does the maintainer provide?
The maintainer provides project context, milestone boundaries, review, and guidance. They still own the repository's standards and every merge decision.
A good program does not remove maintainer work. It makes that work clearer, more repeatable, and easier to evaluate.
What does the developer practice?
Developers practice reading an existing codebase, asking clear questions, making focused changes, responding to review, and staying consistent over several pieces of work.
- Repository setup and local workflow
- Investigating an issue before changing code
- Focused, well-described pull requests
- Responding to review and resubmitting
- Communication and follow-through
How does Devprentice fit?
Devprentice runs open-source apprenticeships as programs in public GitHub repositories. A maintainer sets the milestones, the acceptance criteria, the reviewer, and the AI policy before anyone joins, and the code and reviews stay on GitHub. At the end, the contributor gets a Contribution Record they choose whether to share. See a sample Contribution Record.