Frequently Asked Questions

What is Devprentice?

Devprentice is a platform for structured open-source mentorship programs. Developers contribute to real projects with milestones and review, while maintainers guide contributors and build a visible record of mentorship.

How does a Devprentice program work?

A program gives a real open-source repository a clear contribution path. Maintainers define the scope, developers contribute through pull requests, and the collaboration record grows as the work moves forward.

• A maintainer creates a program around a public repository.
• The program describes scope, stack, expected time, and milestones.
• Developers join programs that fit their goals and current skills.
• Work happens through issues, pull requests, reviews, and feedback response.
• Devprentice turns that activity into a public record of contribution and mentorship.

Who is Devprentice for?

Devprentice is for developers who want presentable experience from real open-source work and maintainers who want a structured way to grow reliable contributors through mentorship.

What becomes public?

A public record can show milestones, pull requests, review threads, feedback response, contribution consistency, mentorship activity, and completion outcomes. The goal is to show how people work together, not only the code that merged.

Is Devprentice free?

Devprentice is free during beta. Developers and maintainers can sign in with GitHub and choose how they want to participate.

How does Devprentice relate to GitHub?

GitHub remains where repositories, issues, pull requests, and reviews live. Devprentice adds program structure around that work so milestones, mentorship, feedback response, and progress are easier to follow and present.

How does AI fit in?

AI helps summarize patterns across reviews, communication, feedback response, consistency, and mentorship. The program itself is built around real human contribution and human guidance.

Who's behind Devprentice?

Devprentice was founded by Joseph Knickerbocker, a software engineer building a practical way for open-source contribution and mentorship to become more structured, visible, and useful to both sides.

What projects qualify for Devprentice?

Any public open-source project on GitHub can run a Devprentice program when an active maintainer is ready to define milestones, review pull requests, and guide contributors through real project work.

What does a Devprentice program look like for maintainers?

A maintainer creates a program around a repository, describes the contribution path, defines milestones, and reviews work as developers move through the program. Devprentice records the mentorship and collaboration around that work.

What do maintainers do?

Maintainers define the work, explain project context, review pull requests, answer technical questions, and decide what gets merged. Devprentice helps structure the program and make progress visible.

How are milestones defined and who sets them?

Maintainers define the initial milestone path, usually from onboarding to a first pull request and then deeper project work. Developers and maintainers can refine milestones as the program progresses.

What do maintainers get from the public record?

Maintainers can show program design, review quality, mentorship, contributor growth, and completion outcomes. That record helps make technical leadership and mentorship visible through real open-source work.

Can a maintainer run more than one program?

Yes. A maintainer can run programs for different milestones, different repositories, or different contributor levels when they have enough review and mentorship capacity.

Who owns code contributed through Devprentice?

The project owns contributed code under the project's existing license and contribution rules. Developers contribute through normal pull requests to the repository.

What skill level do I need? Do I need prior open source experience?

You should be comfortable writing code in at least one language and ready to work in a real repository. Prior open-source experience helps, but the program structure is designed to make expectations clear.

What does a Devprentice program look like for developers?

Developers join a program, work through milestones, open pull requests, respond to review, and build a public record of how they contribute, communicate, and improve through feedback.

What proof do developers build?

Developers build presentable experience from real pull requests, review threads, feedback response, consistency, communication, and completed milestones. The record shows how they work on a real team.

How long does a program take?

Program length depends on repository scope and milestone design. Most programs are structured around a clear weekly time expectation so developers and maintainers can plan the work.

What communication is captured?

Devprentice can surface how developers ask questions, respond to feedback, explain tradeoffs, follow up on reviews, and keep progress moving through normal project channels.

What do developers leave with?

• Real open-source pull requests tied to program milestones.
• Review and feedback response history.
• A public record of contribution consistency and collaboration.
• Mentorship experience from working with an active maintainer.

Are Devprentice records shareable?

Yes. Devprentice records are designed to be public and shareable so developers can point to the work, the review process, and the collaboration behind their contributions.

Can developers join more than one program?

Yes. Each completed program adds more evidence of real contribution, mentorship, communication, and consistency across open-source work.