Note: Linux Foundatio is implementing The Linux Foundation has implemented a new streamlined method for managing committers.  What's described below is the traditional method, which is the current practice of the O-RAN open source project.  

Further simplified process for committer changes in a repository of an O-RAN-SC subproject (starting 2021-June)

1. Modify the INFO.yaml file (add. Add/remove the committer entries and add information at the end about removal and promotion of committers (acting as additional log).
2. Start a review and have the majority of existing committers give a +1. Once that's done merge the review. This will kick of off the process on LinuxFoundation the Linux Foundation side to update the correct committer information in their system (they also check that the majority has vote +1).
3. once Once all udates updates are done, there's an automatic post-fact e-mail generated to the TOC mailing list.
4. To verify that the committer right is rights are set correctly, the committer needs to access the Gerrit site at http://gerrit.oran-osc.org and login.  After login to the Gerrit site, clicking on the committer name at the top right corner, select Settings then Groups, and check the list of group names.  This lists shows the repositories that the said committer has been granted committer rights for, each in the format of ldap saml/<repo-name>.

Simplified process for committer changes in a repository of an O-RAN-SC subproject (starting 2020-Mar-11)

1. Contact the PTL (project technical lead) of the project to which the gerrit repository belongs to. For example, the repository https://gerrit.o-ran-sc.org/r/admin/repos/ric-plt/vespamgr belongs to the near-RT RIC subproject. For example, the near-RT RIC maintains this list here. In the e-mail to the PTL include the list of new and/or to be removed committers.
2. In order to facilitate an "e-mail vote" the PTL assures that the existing committers are subscribed to the mailing list main@lists.o-ran-sc.org (you cannot reply to it unless subscribed).
3. The PTL will write an e-mail to the mailing list main@lists.o-ran-sc.org with the suggested change. Example: link
4. At least 50% of the repository voter pool must approve the change. The voter pool consists of existing committers of the repository plus the PTL of the project the repository belongs to.
5. If not approved, the PTL sends reminders or facilitates further discussion.
6. If approved, the PTL will update the INFO.yaml file of the repository and send the change for review. A non-PTL committer will publish the change. Example: link
7. Once the INFO.yaml file was merged into the main branch, LF (LinuxFoundation) tools will pick up the change and update the relevant LF tools. This is visible in the gerrit review as a LF jenkins CI job that runs after the change was submitted.  There is no need for an extra ticket towards LF developer support.

This simplified approach was discussed in the O-RAN-SC TOC call on Mar-11. Check the recording from minute 3:30 to minute 8:00

...