Page History

...

1. Component Name (Name of the repository): 
2. Component Description (To appear with the repository): 
3. Owners/ Maintainers List (provide include public GitHub-ids for GitHub repos):
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

...

GitHub Private Repository Access Request

...

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.

...

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.

...