...
- Summarize the naming of all project artifacts as it appear in Gerrit, Jenkins, JIRA and Wiki. Linux Foundation uses these information to create all projects artifacts.
- Provide the list of contributors and committers with first and last name, LFID, email, and location. See the differences between and Contributors and Committers in TSC Charter, Section 3.1 Project Roles.
| Note | ||
|---|---|---|
| ||
Information contained here is maintained by the PTLs for the purpose of community convenience only. The INFO.yaml file associated with each repo is considered the authoratative source of information. |
In the Release Artifacts table the requested info are:
- Project Technical Lead: first and last name of
...
- PTL
- Jira Project Name: Project name as it appears in JIRA project list
- Jira Key: JIRA Key as its appear in Jira Key list
- Project ID: Unique ID identifying the project. Project ID is used to compose the "Components Repository name" and "Maven Group ID". Project ID can (but not necessarily) be the same as the JIRA Key.
- Gerrit Repository (ies) URL: This will be filled out after Linux Foundation has created all repositories.
- Link to Wiki Space: This will be filled out after a Space in Wiki is created to handle project specific artifacts.
In the Release Components table the requested information are:
- Components Name: name of the component as it is usually actually used in the day to day conversation. Components name can be composed of multiple words separated by a - (dash).
- Components Repository name: name of the repository as it appears in Gerrit. Formed by: Project ID/folder/Components Name. All words in lowercase and separated by a / (slash). For simple project (flat repo structure) the folder is optional.
- Maven Group ID: this name is used to uniquely identify the component in Nexus, and to define dependency between components. Formed by: org.onap.project-ID.folder.components-name. All words in lowercase and separated by a . (dot), except for the components name who remain unchanged.
Note: groupId is not distinct for all projects - some need the artifactId appended like (sdc, logging-analtyics, pomba)
Example
...
Component Name: deployment-handler
...
:
...
Maven Group ID: org.onap.dcaegen2.platform.deployment-handler.
The above example does not match reality - as of 20180806 we see the following for a DCAEGEN2 jar
<groupId>org.onap.dcaegen2.platform</groupId>
<artifactId>servicechange-handler</artifactId>
- Components Description: describes in 1 or 2 sentences the purpose of the component.
In the "Resources committed to the release" section enter all requested information. This will expedite Linux Foundation activities and speed up committers credentials assignment.
| Table of Contents | ||||
|---|---|---|---|---|
|
Usage
...
| title | Usage on adding Repositories |
|---|
Note to PTL for adding repositories.
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
...
Note: The Infrastructure Coordinator will review the completeness and the accuracy of the information and will proceed with the formal request to Linux Foundation
...
| title | Usage on adding or removing committers |
|---|
Note to PTL for adding or removing committers.
For each project, update accordingly all the sections to support your project needs.
...
Active and Available Inventory
...