OpenNESS helps to securely on-board and manage new edge services on the On-Premise & Network Edge:
- It abstracts out the complexity of the network to cloud developers
- It enables secure on-boarding and management of applications with an intuitive web-based GUI
- It enables functionalities such as access termination, traffic steering, multi-tenancy for services, service registry, service authentication, telemetry, application frameworks, appliance discovery and control
- It is built on top of consistent and standardized APIs exposed to the developer community
OpenNESS originated with Intel looking to enable Service Providers and Enterprises with an easy-to-use software platform for the edge. We are happy to be delivering this into the Open Source community to help accelerate the adoption of edge computing.
OpenNESS aspires to build an industry open source community that welcomes contributions from everyone to help ease the creation of services for the edge.
Technical Steering Committee Charter
The scope of this body is limited to the questions directly related to the development in the following organization:
The decision making process will be based on a simple vote majority from the TSC members. In the event of a deadlock the Technical Board Chair shall have the casting vote.
- Any new project repositories must be approved by the Technical Board
- Resolving any technical disputes. Anybody who is unhappy with the resolution of a technical issue can request that the Technical Board review the issue and make a decision on it. This is only expected to happen in exceptional cases. Before escalating to the Technical Board it is required that all reasonable steps to resolve the dispute via consensus are taken. If the Technical Board Chair does not feel that this has happened, they can refer the issue back to the complainant for further action to be taken before escalating it to the Technical Board. The decision of the Technical Board on any technical disputes will be final and all project contributors are expected to comply. If a Maintainer fails to comply with a decision of the Technical Board, the Technical Board will be empowered to take any necessary steps to enforce its decision.
- Voting on all matters requiring a decision from the Technical Board.
There will be a 2 Maintainers for the OpenNESS project – one Maintainer for the Edgenode and one for the Edgecontroller
Act as a gatekeeper to the code - ensuring coding standards, quality, and functionality of code is maintained by the developers. Any additions to the source code must be approved by the relevant maintainer before they are added. The role includes:
- Ensuring any code submitted is of the appropriate quality
- Ensuring that any code submitted has been reviewed by peers
- Ensuring that the relevant documentation is kept up to date with the code
- Ensuring that any identified bugs in the relevant code is captured in the JIRA backlog
- Ensuring that the unit, integration, and regression tests are appropriate for the relevant components
- Educate users on Warranties, IP, and the implications of the open source license
- Answer questions/emails on the relevant areas of the OpenNESS code base