... | ... | @@ -27,25 +27,7 @@ This page describes the kinds of roles that interested parties can take on. |
|
|
# 1. Technical Committee #
|
|
|
|
|
|
The Technical Committee (TC) is composed of representatives of OSA Members who are technical experts and have in depth experience of the OAI code.
|
|
|
The TC is responsible for the following tasks:
|
|
|
|
|
|
1. Review ticket upon creation to ensure [Ticket Policy Guidelines](policy/ticket-policy) are followed
|
|
|
2. Add a new project card in the “In Progress” projects in OAI Weekly Developers Meeting to track progress of Issue opened in the Ticket
|
|
|
3. In OAI Weekly Developers Meeting, track progress of all open issues and manage lifetime of [branches ](policy/branch-policy)
|
|
|
4. In case of a [Merge-Request(MR)/Pull-Request(PR)](policy/merge-request-policy), monitor CI outcome of the MR/PR
|
|
|
- Coordinate with contributor/developer to resolve conflicts in case of failure
|
|
|
5. In case of successful CI result of a MR/PR,
|
|
|
- one or several TC members are tasked to perform a "human" code review to ensure that policies / guidelines are followed:
|
|
|
* Especially the ones that cannot be reviewed/checked by an automated script.
|
|
|
* TC review topics can be found at [OAI TC Code Review Guidelines](guidelines/tc-code-review-guidelines).
|
|
|
- Accept MR/PR into the latest `develop` branch state.
|
|
|
- Coordinate with contributor/developer in case of conflicts.
|
|
|
6. Close tickets and delete branches upon task completion.
|
|
|
7. Review all the policies to be in-line with state-of-the-art development tools
|
|
|
|
|
|
TC Members are using a private dedicated Slack channel as a communication tool.
|
|
|
|
|
|
If you represent an OSA Member and wish to participate in the Technical Committee, please contact Raphael Defosseux at <a href="mailto:raphael.defosseux@openairinterface.org" target="_top">raphael.defosseux@openairinterface.org</a>
|
|
|
|
|
|
|
|
|
# 2. Contributor / Developer #
|
|
|
|
... | ... | |