| Children Display | ||||||||
|---|---|---|---|---|---|---|---|---|
|
With each repository that gets added your build, release and Rel-Eng support times get slower.
There is more work for release engineering to do, more jerkins jobs that need to run and more compute resources utilized.
| Table of Contents | ||||
|---|---|---|---|---|
|
Requesting a new repo
For each project, update accordingly all the sections to support your project needs.
To request a new repository, you have to:
1) Fill out the required information in the table below
2) Email infrastructure-coordinator@onap.org specifying the repos you are asking creation of and the justification as to why an existing repo cannot be used.
Note: The Infrastructure Coordinator will review the completeness and the accuracy of the information and will proceed with the formal request to Linux Foundation
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.
The PTL is responsible for maintaining the INFO.yaml file in all of their repos.
Adding/Deleting Committers to a Repo
Note to PTL for adding or removing committers.
For each project, update accordingly all the sections to support your project needs.
For adding a committer, fill out this template.