Skip to content

Commit

Permalink
Merge pull request #145 from TEF-RicardoSerr/patch-2
Browse files Browse the repository at this point in the history
Adding description for "support of an API" within API-onboarding.md
  • Loading branch information
MarkusKuemmerle authored Jun 11, 2024
2 parents fe6b2b1 + 349cfc8 commit e47ed06
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions documentation/API-onboarding.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,8 @@ The whole procedure (steps 1-4) should be done within 2 regular meetings of the

In parallel, the API proposal is formally registered in CAMARA by adding it to the [CAMARA API overview list](https://github.com/camaraproject/APIBacklog/blob/main/documentation/APIbacklog.md) The WG chair creates a new line in the table and fills in API family name, API family owner, API family proposal registration date, the link to the application template and the supporters for it.

NOTE: Supporting an API proposal means that the supporting company must provide at least 1 (one) Maintainer at the time of the Sub Project creation. This applies not only to new API proposals but also for those Scope Enhancements of a Sub Project in which the creation of a new repository is required.

## TSC decision on API proposal

Upon receiving the API proposal and notification from the WG chair, the TSC studies the proposal and votes it at the TSC meeting.
Expand Down

0 comments on commit e47ed06

Please sign in to comment.