Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Community contributors are managed by selected team members from the CPS project

In order for the CPS team to regularly review the code commits from external contributors the following process and rotational schedule is created. 

Code review process

  1. Members of the community shall submit their code as work in progress (WIP) initially on gerrit.
  2. Always do a self-review first and use the CPS Code Review Check List to minimize the number of peer review iterations required!
  3. CPS team member that manages the team will do an initial review and once done with a +1 - the code submitter can then change the status to active.
  4. Once active, then selected team members based on the review schedule of the CPS project can review the code. 


Relevant tools

Slack - slack channel is used to coordinate between the community and the CPS team members regarding the code reviews. Contact Lee Anjella Macabuhay  to be added.

Review Schedule

Current rotation period: 2 weeks

  • Note to reviewers: Once you start reviewing a code, it is expected that you review this code as neccessary until code is merged.

Community Contributors

TeamContributorsNotes
Deutsche Telekom (TechMahindra)

Deutsche Telekom (TechMahindra) Team Calendar

Capegemini Team ( 5G SON Use Case )Vishal Varvate  murali parthasarathy k 
  • No labels