Project Charter • Code of Conduct • Working Language • Documentation • Support and Feedback • Contribute • Contributors • Licensing
A global collaboration can address much of the challenges in scaling API services across heterogenous operator architectures.
The development of open, global, and interoperable API solutions can benefit customers and developer ecosystems by giving access to operator capabilities in whatever network customers are in and therefore allow applications to run consistently between telco networks and countries. A new form of collaboration between various players (telcos, ISVs, device manufacturers, hyperscalers, etc.) could address much of the challenges in scaling API services across heterogenous operator architectures as well as advance the connectivity industry towards a more robust and faster core network, encourage the faster adoption of capabilities and as a result create value for the entire tech industry.
- Accelerate technology development
- Build sustainable ecosystems around collaborative projects across industries.
- Drive industry alignment by facilitating industry discussions with telcos, ISVs, device manufacturers, hyperscalers, etc.
- Harmonization of APIs
- Harmonize and convert APIs to a user understandable format called “Service APIs”.
- Achieve harmonization through working code vs. documents.
- Implementation experience should guide harmonization process.
- Enable interoperability (e.g. effortless portability of applications between different operators), compatibility (applicability to different network technologies) and interconnectivity (to enable interoperator collaboration).
- Education and promotion
- Actively promote Service APIs via various forums, events, conferences, training programs, ecosystems and social media.
- Promote best practices by aggregating and publishing lessons learned.
- Accelerate commercial adoption
- Create awareness around use cases and services.
- Minimize implementation effort though easy-to-consume Service APIs.
- Foster the API integration in relevant developer’s environments and ecosystems.
- Provide customer service and support for the design phase and experimentation.
APIs grouped by services and bundled up into “Service APIs” could reduce the complexity of accessing operator capabilities for developers and enterprises. CAMARA Project is an independent open-source project and not controlled by any single company. How each operator monetize the API is completely out of the scope of the project. Implementation is still on the operator responsibility. Only scope of the CAMARA Project is how APIs are designed or consumed technically.
The governance, voting rules, IPRs and policies of the CAMARA Project are documented in the Project Charter. The project structure and roles are documented in the Project Structure And Roles.
This project has adopted the Contributor Covenant in version 2.0 as our code of conduct. Please see the details in our CODE_OF_CONDUCT.md. All contributors must abide by the code of conduct.
We decided to apply English as the primary project language.
Consequently, all content will be made available primarily in English. We also ask all interested people to use English as language to create issues, in their code (comments, documentation etc.) and when you send requests to us. The application itself and all end-user facing content will be made available in other languages as needed.
The full documentation for the project can be found in the "documentation" subfolder.
The following channels are available for discussions, feedback, and support requests:
| Type | Channel |
|---|---|
| Issues | GitHub issues |
| Other Requests |  |
Contribution and feedback is encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines. By participating in this project, you agree to abide by its Code of Conduct at all times.
Our commitment to open source means that we are enabling -in fact encouraging- all interested parties to contribute and become part of its developer community.
- The current list of participants = contributors of the alliance can be found here PARTICIPANTS.
- The current list of maintainers of the overall project documentation can be found here Code Owners.
- The current list of maintainers of a sub-project can be found in the MAINTAINERS.MD file of the sub-project.
See the respective chapter in the Project Charter.