Skip to end of metadata
Go to start of metadata

Nominee’s bio

I have been a Member of the Technical Staff at ON.Lab since 2013, where I work primarily as a software developer, as well as an platform advocate, mentor, and software designer. Prior to joining ON.Lab, I worked on the consumer and profile team at LinkedIn and on the high speed trading platform team at Chopper Trading. I graduated from Stanford with a Bachelor's and Master's in Computer Science.

How long have been working in the ONOS community?

Since 2013, I have been an active contributor to the ONOS community as a developer, reviewer, and mentor. I have been a member of the ONOS TST since its inception in December 2014. I am also a core developer for the Mininet project and have been involved in development using other SDN platforms (including Beacon, Floodlight, and Pox) over the past five years.

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

On the technical front, I’ve contributed to several areas over the past few years. I was the principle developer for the original intent framework, and I have worked on the application, flow, and several southbound subsystems. I am a module owner for all areas of the project, and I review proposals and code from across the project. I’ve worked on both the Maven and Buck build, packaging, and deployment tools. I also maintain Gerrit, our code review system, and wrote the module owner plugin. From a community perspective, I’ve given several talks and tutorials on ONOS at conferences and events around the world. I’ve mentored dozens of community members on design and code development.

What are you actively working on in ONOS?

I am currently working with the dynamic configuration, intent enhancement and build tools brigades, as well as on improving testing and platform stability.

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

I bring years of experience and a breadth of knowledge from my experience as a developer and TST member. I can offer a perspective on project proposals that accurately accesses their feasibility and value in the context of the ONOS project.

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

As the ONOS project continues to grow, code stability remains vital to keeping developers productive. I will advocate for us to focus on continuous testing and more frequent developer releases, as well as the disaggregation of the source code, test, and build systems to accommodate different modules’ maturity and ease the creation of distributions. Additionally, I will push for in-service upgrades, high performance programmatic APIs, and tools for runtime debugging.

  • No labels