Page Comparison

Attendees

...

1. To close the agenda SEVEN DAYS BEFORE the conf. call.

   • In case a WG participant wants to include a point in the agenda (e.g., present a new API proposal), this participant shall ensure the corresponding issue is opened in Github by then.

   • Exceptional situations will be treated separately.

2. New schedule of conf. calls **The meetings are to be held by Linux Foundation (Links available at GitHub and Confluence Backlog front pages)

   • 2nd Thursday of the month (9-10:30 UTC)

   • 4th Thursday of the month (15-16:30 UTC)

3.  Send agenda to TSC mail list, to encourage more TSC member companies to join the call and provide comments when they identify APIs which are of interest for them. 

4. New API proposals are included in backlog table when template PR is created, linking to the pending PR

5. PR will be merged as soon as ready for TSC, and should be merged before TSC review

6. API enhancements requires existing group’s validation. TSC is informed accordingly to validate

7. Link and status in backlog table will be updated accordingly

8. Issue to track API onboarding will be opened once new API is confirmed in TSC.

Approval of minutes of last conf. call

...

• GSMA informed CAMARA Backlog that Open Gateway is considering certain Drop2/3/4 APIs that have been stuck in Backlog, “at risk”, due to lack of support. What this means is that GSMA is pushing our MNOs to actively reconsider within the next 2 weeks if they can support them. By raising it in the Backlog meeting we increase the chance to find enough support to “reactivate” progress. 

  • Best Interconnect

  • IMEI Fraud API

For clarity if any API is not a priority for OGW anymore at this point in time, we still expect they can progress independently in CAMARA.

...