Page History

Nominee’s bio (and/or LinkedIn profile)

Member of Technical Staff in ONF since 2019

Full stack developer, from GUI to backend to tooling.

Based in Cork, Ireland

Github: https://github.com/SeanCondonSystem and Software Architect at Microsemi Inc. Frequency & Timing Division (we used to be Symmetricom.

Linked in https://www.linkedin.com/in/sean-condon-11a00038/ (OK - the picture is about 10 years old  - must get around to changing it)

How long have been working in the ONOS community?

Since November 2016

What contributions have you made in the past to the ONOS community?

I added in the whole section under apps/cfm and incubator//l2monitoring - this is a model of the IEEE 802.1q CFM entities and MEF Services O&M

Also added a driver for Microsemi EA1000 device. This was one of the first modules in ONOS to make use of the onos-yang-tools

Both of these are now used in the E-CORD reference architecture/reference implementation. We demoed this at ONS2017

am leading the development of the Aether ROC GUI and API

I am a core member of the development team for SD-RAN and µONOS

I have re-engineered the ONOS GUI to be based of Angular 7 components (upgrading it from AngularJS). I have supported this with videos and blog postsI also added error handling to the ONOS RESTCONF implementation recently.

What are you actively working on in ONOS?

I'm currently involved in Dynamic Configuration Subsystem with the proposals for DCS v2.0 and RESTCONF.

I'm also looking a GUI enhancements, especially in the area of configuration GUI driven by YANG.Current priorities are the Aether ROC GUI and the SD-RAN

Why do you feel you would be a good candidate for this position?

I think my experience from the point of view of a device vendor would bring a different perspectiveand longevity on the project bring stability.

Are there any changes you would like to bring to the community if elected into this position?

I'd like to see more active and updated tutorials - I think there is a lot of duplicated effort by open source members making the same mistakes over and over.a focus on keeping documentation current, and a study on what the community wants from us on documentation.