- This line was added.
- This line was removed.
- Formatting was changed.
Developer-related documentation for CORD/SEBA can be found at https://guide.opencord.org. The
This wiki contains information about how to engage with the projects.
All information on this wiki is publicly accessible. If you would like to contribute to this space, you will need a CORD account: https://opencord.org/registration
Peruse a dashboard reporting metrics about community involvement in CORD.
CORD is an open reference implementation constructed from commodity hardware and open source software. Our mission is to build an open reference implementation of CORD, bringing datacenter economies and cloud agility to service provider networks. A high level overview of the CORD project can be found here.
Domains of Use
CORD is a general-purpose service delivery platform. It can be configured to host a set of services in support of residential customers, enterprise customers, mobile customers, or any combination of all three.
From a technology perspective, the set of services that run in a given CORD installation is defined by a configuration parameter – the service graph. It is possible to configure a service graph that draws elements from across access technologies and edge applications.
From a community perspective, work is being organized around a set of usage Domains. These domains sometimes correspond to market segments or access technologies (e.g., residential, enterprise, mobile), they sometimes correspond to cross-cutting capabilities (e.g., monitoring and analytics), and they sometimes correspond to emerging edge applications (e.g., IoT, gaming, VR). The plan is for each of these domains of community activity to be anchored at this home page. To date, the following domains are active:
Key People & Communication Channels
Governance of the CORD project is intended to foster a technical meritocracy within the context of stewardship by the CORD Chief Architect and the ONF Board of Directors. The over-arching governance principle is To act in the best interest of the broader community.
The technical steering team is responsible for all technical decisions in the project. They are responsible for the content and structure of the code base and for all technical priorities with respect to the code base. The CORD chief architect is the team lead of the technical steering team.
The mailing lists are the preferred way to get in touch with the project members with any questions, suggestions, or concerns. You can find a list of our active mailing lists in the Quick Navigation.
The CORD Slack is the best way to get quick answers to your questions. Our team is distributed globally, so someone should be available at all times. Register for a CORD Slack account here: http://slackin.opencord.org
You can find all of the project calls, including brigade meetings, Scrum stand-ups, component project meetings, and more, on the CORD Calendar. Add this calendar to your personal Google calendar by clicking the blue plus in the bottom right-hand corner of the screen.
NOTE: these meetings are PUBLIC and RECORDED and the recordings are typically uploaded to YouTube.
- Learn about CORD software by reading the Guide.
- Join the discussion on Slack and Email.
- Read about CORD's Architectural Requirements.
- Build your own CORD POD.
- Peruse the Service Inventory and Technical Projects.
- See the Project Roadmap and join one of our Brigades.
- Learn how to contribute.