How we pick beginner-friendly repositories without hiding risk

We start with license clarity and a documented code of conduct. Those two signals do not guarantee kindness, but they reduce the chance that a newcomer walks into an unmoderated pile-on.

Next we read recent pull request threads for tone. We look for reviewers who explain constraints, link to docs, and separate personal preference from project requirements. If every thread is one-line approvals, we dig deeper to see whether anyone is mentoring.

We also measure release cadence against cohort length. A project that ships once a year can still work, but only if maintainers agree to review windows that match our schedule. We decline quietly when timing would leave participants waiting without feedback.

Finally, we share a plain-language risk brief with each cohort. Some ecosystems move fast and break APIs; others are stable but sparse on issues. Participants should know which world they are entering before they invest their nights.