New Repository Request

If you require a new repository on RDK Central or RDK Central GitHub you must supply ALL of the following information in a CMF-SUPPORT ticket.

If you select Ticket Type "New Repository Request" then the Jira Ticket will list these fields as mandatory. 

Note each repository requires a unique ticket.

  1. Component Name (Name of the repository): 
  2. Component Description (To appear with the repository): 
  3. Owners/ Maintainers List
    1. If Github (include public GitHub-ids for GitHub repos)
    2. If Gerrit (include ldap groups owners/approvers)
  4. Master Location & Sync (if applicable):
  5. Master Git URL (if applicable):
  6. History (Can history be shared?): No
  7. License (Apache 2.0, RDK License etc):
  8. Required Branches (Default/Other):
  9. Initial Access Restriction (if any) (No / Restricted to Comcast, another partner name)
  10. Export Compliance (Does the code contain any SSL, Encryption or Security related implementation?):
  11. CI Support (Yes/No): 
  12. Integrate on Reference Platform (Yes/No):
  13. Profile(s) (RDK-V and/or RDK-B and/or RDK-C):

If the request is for a GitHub repository the owner and maintainers must also have done the following:

  1. GitHub Repo Access Setup Complete (Yes/No):
  2. Users accepted GitHub Invite(s) (Yes/No):
  3. Ensure to specify the public GitHub id's who require access and what level of access they should have, refer to https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-[…]anaging-repository-roles/repository-roles-for-an-organization 

New repos created on GitHub https://github.com/rdkcentral/  should be created privately initially and only open sourced when license and copyright issues have been resolved. This is because Open Sourced repos on Github will not allow direct push. 

  • All contributions to Open Sourced repos have to be made using a Pull Request which in turn triggers various checks for licensing and copyright issues.
  • Private repos will allow for direct push by the component owner.
  • When a private repo is to be open sourced the repo will first be scanned to ensure no license or copyright issues exist. Any that are found must be resolved before the repo is opensourced.
    So if a component owner wishes to populate a new repo using direct push then the new repo request should stipulate the repo be created privately with initial access restricted to the component owners.
  • Once the initial population of the repo is complete a new ticket should be opened requesting the repo be open sourced - this will then be scanned allowing licensing issues to be resolved prior to open sourcing.

If the request is for a Gerrit https://code.rdkcentral.com then the owners and approvers must be specified:


GitHub Private Repository Access Request

If you require access to a private (restricted) RDK Central repository then please follow these steps.

  1. Follow the steps in RDK Central Github Profile Setup for Private Repository Access
  2. Raise a CMF-SUPPORT ticket specifying which repositories you require access to ensuring you include the approval from the repository owner and your public GitHub ID
  3. Please specify the public GitHub id's who require access and what level of access they should have, refer to https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-[…]anaging-repository-roles/repository-roles-for-an-organization

Refer to RDK Central Github Access Issues FAQ if any questions about the repository access process.


GitHub Elevated Privileges Request

If you require elevated privileges on a private (restricted) RDK Central repository then please follow these steps.

  1. Follow the steps in RDK Central Github Profile Setup for Elevated Privileges on a Repository
  2. Raise a CMF-SUPPORT ticket specifying which repositories you require privileges, what privileges you require and ensure you include the approval from the repository owner and your public GitHub ID
  3. Please specify the public GitHub id's who require elevated access and what level of access they should have, refer to https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-[…]anaging-repository-roles/repository-roles-for-an-organization

Refer to RDK Central Github Access Issues FAQ if any questions about the repository access process.


Gerrit Repository Access Request

Gerrit repository access is managed via LDAP.

Please check with the repository owner for approval and to determine what the LDAP group is. Once you have approval for access then raise a ticket with RDKM Support support@rdkcentral.com to get added to the relevant LDAP group.

If you can't find out who the repository owner is then please raise a CMF-SUPPORT ticket and we can check.


  • No labels