This is a cross-post of the following post in the Contributor Experience category: Revised Code Owner role
Over the last year, we have revised the Contributor Ladder for the Swift project to clarify the requirements and the nomination process as well as clearly describing the responsibilities and privileges that are expected of you at each level. This included the introduction of a new Member role that has a lower entry barrier and allows upcoming contributors to invoke CI without giving them merge access yet.
This work was recently concluded with a revised Code Owner role, which now reflects the lived practice of documenting Code Owners per directory in a .github/CODEOWNERS file. Importantly, it also standardizes the requirements and nomination process to become a Code Owner. We ask all current Code Owners to follow this new procedure when adding new Code Owners to a code area.
If you have any concerns or questions about the new definition of the Code Owner role, please share them in the post on the Contributor Experience category.