...
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 2015The following are the current steering team members:
Thomas Vachuska, Team Lead
Ali Al-Shabibi - southbound maintainer
Madan Jampani - core maintainer
Brian O’Connor - northbound maintainer
- Andrea Campanella
- Charles Chan
- Jordan Halterman
- Carmelo CasconeJonathan Hart - core networking
Contact Information
Drop the technical steering team an email if you have a technical or architectural topic to discuss or get guidance for. The email archive is available for browsing and review of past conversations.
...
Anchorrecurmeet recurmeet
Recurring Meetings
recurmeet | |
recurmeet |
The team will be meeting every holds PUBLIC and RECORDED meetings every other week, 15between 09:00 and 10:00 PST/PDT conducted via Zoom. To make accommodations for community members in other time-zones, the TST is open to scheduling meetings outside of the regular times 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 are generally available as shared Google documents, and whenever possible, recordings will be made and posted on YouTube. These documents are open for editing during the meeting and for comments afterwards. In this way, they 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 is needed and wanted.
The -16:00 PST via Google hang-outs and Slack #tech-steering channel. 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.
Joining the Meeting
Join Zoom Meeting:
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:
Meeting ID: 970 969 526
One tap mobile
+16699006833,,970969526# US (San Jose)
+19292056099,,970969526# US (New York)
Find your local number: https://zoom.us/u/adqQM87Zrg
US Toll-free 888 788 0099
Scheduled & Past 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 below:
2021/03/10 |
|
2020/08/12 |
|
2020/06/24 | |
2020/06/03 | |
2020/05/20 | |
2020/05/06 |
|
2020/04/08 | |
2020/03/24 |
|
2020/01/22 |
|
2020/01/08 |
|
2019/12/11 | |
2019/11/27 |
|
2019/10/16 |
|
2019/10/02 |
|
2019/08/14 |
|
2019/07/31 |
|
2019/07/10 |
|
2019/06/26 |
|
2019/06/12 |
|
2019/05/29 |
|
2019/05/15 |
|
2019/04/24 |
|
2019/04/10 |
|
2019/03/28 |
|
2019/03/13 |
|
2019/02/27 |
|
2019/02/20 |
|
2019/02/13 |
|
2019/01/29 |
|
2019/01/23 |
|
2018/11/28 |
|
2018/11/14 |
|
2018/10/31 |
|
2018/10/24 |
|
2018/10/10 |
|
2018/09/12 | |
2018/08/22 | |
2018/08/01 |
|
2018/07/18 |
|
2018/06/27 |
|
2018/06/06 |
|
2018/05/10 |
|
2018/05/02 |
|
2018/04/25 |
|
2018/04/04 |
|
2018/03/21 |
|
2018/03/14 |
|
2018/03/07 |
|
2018/02/21 |
|
2018/01/24 | |
2018/01/10 |
|
2017/12/21 |
|
2017/11/29 |
|
| |
2017/10/25 |
|
2017/10/04 |
|
2017/09/13 | |
2017/08/02 |
|
2017/07/19 |
|
2017/06/21 |
|
2017/06/07 |
|
2017/05/31 |
|
2017/05/24 |
|
2017/05/10 |
|
2017/05/03 |
|
2017/04/26 |
|
2017/04/19 |
|
2017/04/12 |
|
2017/03/22 |
|
2017/03/15 |
|
2017/02/22 |
|
2017/02/15 |
|
2017/02/01 |
|
2017/01/25 |
|
2017/01/11 |
|
2017/01/04 |
|
2016/11/29 |
|
2016/11/23 |
|
2016/11/16 |
|
2016/11/09 |
|
2016/10/26 |
|
2016/10/12 |
|
2016/10/05 |
|
2016/09/28 |
|
2016/09/14 |
|
2016/09/07 |
|
2016/08/31 |
|
2016/08/24 |
|
2016/08/10 |
|
2016/08/03 |
|
2016/07/27 |
|
2016/07/20 |
|
2016/07/13 |
|
2016/07/06 |
|
2016/06/15 |
|
2016/06/01 |
|
| |
| |
2016/05/04 |
|
2016/04/27 |
|
2016/04/20 |
|
2016/03/30 |
|
2016/03/29 |
|
| |
2016/02/25 |
|
2016/02/17 | |
2016/02/10 | |
2016/01/27 |
|
2016/01/20 |
Agenda
2016/01/13 |
|
2016/01/06 |
|
2015/12/02 | |
2015/11/11 |
|
2015/11/04 |
|
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?
...
- Will likely require a protocol capable of configuration i.e. OVS-DB or NETCONF
...
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?
...