search

camaraproject / Governance

Telco network capabilities exposed through APIs provide a large benefit for customers. By simplifying telco network complexity with APIs and making the APIs available across telco networks and countries, CAMARA enables easy and seamless access.
53 stars 44 forks source link

Update API-onboarding.md #86

Closed jordonezlucena closed 10 months ago

jordonezlucena commented 10 months ago

It is proposed to clarify some aspects with regards to API onboarding process. The concept of newly defined TSC is also added.

jordonezlucena commented 10 months ago

@jordonezlucena : In general ok, but I've findings in addition:

  • We have a legal terms of reference between OPAG and CAMARA. There's nothing in place for Open Gateway. For that we should keep OPAG but add Open Gateway in brackets.

Fixed.

  • Not all instances of "Steering Committee" are already replaced by "TSC".

The instances which were not replaced were "Steering Committee date" and "Steering Committee decision". Reason is that they still were part of the API backlog table terminology. I've fixed this in the API Backlog WG. It's also fixed here.

API Backlog WG participants have also asked how they can formally declare their willingness to become supporter of an API proposals. The following procedure has been agreed upon: "If a company wants to become supporter, the company name needs to be included in the "Supporters in API Backlog Working Group" column for that API. The WG participant representing that company will do this by submitting a Pull Request against the API backlog". This clarification has been also added in the .md file