Pulling contributors in as reviewers

Lee la sección de la ruta de aprendizaje Trusted Committer part 2 y el artículo enlazado sobre la creación de comunidad de Apache Beam, especialmente su análisis de cómo los colaboradores revisan el código. Decide si el material debe actualizarse en la ruta de aprendizaje o documentarse como InnerSource Pattern; se considerará terminado cuando se hayan acordado la ubicación y el alcance propuestos y se haya revisado el material de aprendizaje correspondiente.

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.