This is a cross-post of the following post in the Contributor Experience category: A new Member contributor role that can trigger CI
So far contributors to the Swift project on GitHub could have three roles: Everybody can participate the Swift open source project and become a Contributor. After creating a track record by creating 5 non-trivial pull requests that were accepted without modifications, contributors could request Commit Access, which allowed them to merge PRs and also trigger CI. Finally, contributors could become Code Owners.
With that structure, gaining the ability to trigger CI had quite a high bar and hinders new contributors from accelerating their contributions to Swift. We are thus introducing a new role: After contributing to Swift multiple times, contributors can request to become a Member, which grants them the ability to trigger CI but does not give them commit access yet. This way they can test changes on their own schedule and taking the burden to trigger CI off those with commit access.
The details of the new Member role can be found on swift.org.
We are looking forward to your feedback and real-world experience with the new role on the post in the Contributor Experience Category. Going forward, we are working on improvements and clarifications to the other roles as well and will post updates about these in the Contributor Experience Category. If you are interested in those updates, please subscribe to that category.