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.

Leggi la sezione del percorso di apprendimento Trusted Committer part 2 e l’articolo collegato sulla creazione della community di Apache Beam, in particolare la discussione sul contributo dei contributor alla revisione del codice. Decidi se il materiale debba essere aggiornato nel percorso di apprendimento o acquisito come InnerSource Pattern; il lavoro sarà completato quando saranno concordati la collocazione e l’ambito proposti e sarà stato revisionato il materiale di apprendimento pertinente.