Pulling contributors in as reviewers

In the learning path for the Trusted Committer (part 2) we explain how it's the trusted committers that are reviewing code. In a first approximation this is correct and matches what I see in many open source projects.

When it comes to recruiting new committers and onboarding them I have seen a different approach:

https://blogs.apache.org/comdev/entry/an-approach-to-community-building (pretty much at the bottom) - contributors at Apache Beam are encouraged to do code reviews as well - in particular if the original patch comes from a committer, the idea is that such a review is enough for merging the code.

Maybe this is something for an InnerSource Pattern instead of the LearningPath though.

Leia a seção do caminho de aprendizado Trusted Committer part 2 e o artigo vinculado sobre a construção da comunidade do Apache Beam, especialmente a discussão sobre os colaboradores revisarem código. Decida se o material deve ser atualizado no caminho de aprendizado ou registrado como InnerSource Pattern; considera-se concluído quando a localização e o escopo propostos forem acordados e o material de aprendizado relevante for revisado.