Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
About the team
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 ONOS chief architect is the team lead of the technical steering team.
Who's in the team
The following folks are in the team for 2015:
Thomas Vachuska, Team Lead
Ali Al-Shabibi - southbound maintainer
Madan Jampani - core maintainer
Brian O’Connor - northbound maintainer
Contact Information
Drop the technical steering team an email
You can view the email archive here
Recurring Meetings
The team will be meeting every two weeks, 15:00-16:00 PST via Google hang-outs and IRC channel #onos on irc.freenode.net. The recurring meetings along with their proposed agendas and resulting meeting minutes will be published below.
| Date | Agenda |
|---|---|
| 2015/02/04 | Tunnels or Virtual Links
|
Pending Topics
- Branches for use cases
- What will we create branches for?
- What is their lifecycle?
- Where should other supporting code go?
- Modeling services in the ONOS network graph
- Can we provide more abstract graphs that contain higher level objects?
- How are new devices modeled?
- Intent Modeling
- How should new intent types be introduced into the framework?
- Packet layer Bandwidth Enforcement
- Will likely require a protocol capable of configuration i.e. OVS-DB or NETCONF