...
- 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.
- 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).
- The PTL will write an e-mail to the mailing list main@lists.o-ran-sc.org with the suggested change (TODO-example-once-exists). Example: link
- 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.
- If not approved, the PTL sends reminders or facilitates further discussion.
- 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
- 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.
...