...
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 The following folks are in the team for 2016:
...
Anchorrecurmeet recurmeet
Recurring Meetings
recurmeet | |
recurmeet |
The team will be meeting every week, 15:00-16:00 PST via Google Hangouts on Air. To make accommodations for community members in other time-zones, the TST is open to scheduling meetings outside of the regular time to fit the needs of the presenters or the interested audience. Since it is not possible to accommodate all time-zones at the same time, the meetings notes will be available as a shared Google document. These documents will be open for editing during the meeting and then for comments afterwards and in this way can serve as a nexus for off-line discussion on the corresponding topic, especially for those topics which may involve technical decisions, where community feedback will be needed and wanted.
The . The recurring meetings along with their proposed agendas and resulting meeting minutes will be published below (in reverse chronological order). Please see the ONOS calendar for details on the how to join the meetings; each week's entry will be updated to convey the agenda and the Google hang-out link.
Standing Agenda Items:
- Community Acknowledgements (2 minutes) – Please feel free to update the wiki in advance with details about who you would like to acknowledge and why
Specific Discussion Topics:
Suggested Discussion Topics
The TST would like to invite ONOS contributors to propose topics for discussion and/or presentations in the weekly meetings. Feel free to contact TST via email or edit this page to register a topic. The following is a set of pending topics:
Recent community survey findings and a discussion with the group about ways to address those points (David & William)
- Upgrading OpenFlow libraries to support 1.5 (Murat)
- Publishing events to external event bus, e.g. Kafka, RabitMQ (David Bainbridge & Madan?)
- Should any internal ONOS event be candidate for this?
- Consider correctness issues in distributed environments
- Branches for use cases (Brian?
- What will we create branches for?
- What is their lifecycle?
- Where should other supporting code go?
- Packet layer Bandwidth Enforcement (Ali or Jono?)
- Will likely require a protocol capable of configuration i.e. OVS-DB or NETCONF
- Moving docs from Wiki to version control - which parts? (Ayaka?)
- Overview of ONOSFW, an integration of ONOS into OPNFV (Jiangchuncheng)
Scheduled & Past Discussion Topics
|
| |
|
| |
2016/05/04 |
|
2016/04/27 |
|
2016/04/20 |
|
2016/03/30 |
|
2016/03/29 |
|
| |
2016/02/25 |
|
2016/02/17 | |
2016/02/10 | |
2015/01/27 |
|
2016/01/20 | |
2016/01/13 |
|
2016/01/06 |
|
2015/12/02 | |
2015/11/11 |
|
2015/11/04 |
|
2015/10/28 | Cancelled due to lack of prepared topics |
2015/10/21 |
|
2015/10/14 |
|
2015/10/07 |
|
2015/09/30 |
|
2015/06/24 |
|
2015/04/29 |
|
2015/04/15 |
|
2015/04/01 |
|
2015/02/18 |
|
2015/02/04 |
|
Suggested Discussion Topics
The following topics have been proposed, but currently lack an owner. Proposed owners are shown in parentheses.
...
- Should any internal ONOS event be candidate for this?
- Consider correctness issues in distributed environments
...
- What will we create branches for?
- What is their lifecycle?
- Where should other supporting code go?
...
|
...
Deprecated Topics
Modeling services in the ONOS network graphCan we provide more abstract graphs that contain higher level objects?How are new devices modeled?
Intent ModelingHow should new intent types be introduced into the framework?
...