With each repository that gets added your build, release and Rel-Eng support times get slower.
...
Requesting a new repo
For each project , update accordingly the PTL is responsible for updates all the sections to support your their project needsaccordingly .
To request a new repository, you have to:
1) Fill out the required information in the table below
...
- The PTL go to the Resources and Repositories section for their project
- The PTL fills in the required information for the new repo(s) they are requesting in the Release Components Name table. Please highlight the newly requested repo using fill colors and/or bold or colored font.
- The PTL emails infrastructure-coordinator@onap.org
...
- with a pointer to the data they just entered. This email must include:
- The LFIDs for the committers for the new repo(s)
- The justification as to why an existing repo cannot be used.
...
- The Infrastructure Coordinator will review the completeness and the accuracy of the information
...
- .
- If there are no perceived issues with the request, the Infrastructure Coordinator will open a repo creation request via support.linuxfoundation.org without engaging the TSC.
- If there are perceived issues
- the Infrastructure Coordinator will contact the PTL for clarification.
- If following the conversation between the PTL there are still unreconciled issues, the Infrastructure Coordinator will escalate the request to the TSC for review and approval.
The INFO.yaml file
Every ONAP repository is required to have an INFO.yaml file in it. It is standard open source practice for every repository to contain key information regarding that repo and the people responsible, which is readily available to any developer anywhere at any time. Not having such a file is the equivalent of saying to a perspective contributor or user, “Go away. We don’t want you here.” Beyond the open source norms perspective, having such files provides opportunities for automation where they can be leveraged.
...