Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This election and nomination process is limited to those individuals who have committer rights on one or more OpenDaylight Projects. Any OpenDaylight Committer can nominate themselves, run for election, and vote in the election for the Committer-At-Large seats on the TSC.  Details on the election process may be found here.

...

Abhijit K

Picture 

Biography

Abhijit is the current TSC Chair for OpenDaylight. As the OpenDaylight TSC Chair, he has presented OpenDaylight at various conferences including ONS, North America, ONS Europe and Linux Foundation's OSN Networking Day in the Bay Area. He was the project lead for the OpenDaylight OpenFlow plugin project since its inception till the start of the Oxygen release as well as a committer on the TTP project. He was elected to the TSC in both the 2016 and the 2017 committer-at-large TSC elections. During the 2017 TSC term - he came up with and evangelized the idea of calendar based ODL release schedules which is now being implemented in Oxygen and beyond. He is technical lead for Ericsson OpenDaylight efforts and works in the Technology department for Ericsson's Cloud unit. In the past he had been an active member of the Forwarding Abstractions Workgroup (FAWG) at the Open Networking Foundation (ONF) and has contributed to and evangelized the main example table type pattern at the FAWG meetings/ONF member workdays. He has around 20 years of experience in networking software development as well as leading teams toward successful outcomes. Prior to joining Ericsson he led a 100+ person software development team at Blade Network Technologies into a successful integration into IBM via acquisition. He is an alumnus of Indian Institute of Technology (IIT), Kharagpur.

Statement of Intent

As a member of the TSC, Abhijit is intending to drive the following issues:

...

JamO Luhrsen

Picture

Biography

Jamo's entire career to date (21 years via Cisco, HP, Red Hat and currently Lumina Networks) has been in the networking industry exclusively in system test and automation. He works remotely from Sacramento, CA. He has been involved as a contributor since the 2nd OpenDaylight release (Helium). He has worked closely as the test lead in several projects including OpenflowPlugin, OVSDB, and Netvirt. He has served as the Integration/Test projects Technical Lead (PTL) since 2015 and served on the TSC since 2016.

Projects

  • PTL: Integration/Test
  • Committer Integration/Test, Integration/Packaging, Releng/Builder, Autorelease

Statement of Intent

  • Test automation has always been important to me and I believe it is vital to any software project. As the PTL of Integration/Test I try to help drive high quality automated system test across all OpenDaylight projects which in turn helps deliver a higher quality OpenDaylight release. The top benchmark for deciding release quality resides on the automated tests run by the various OpenDaylight projects and supporting and that process will be a top priority.


Luis Gomez Palacios

Picture

Image Added

Biography

Luis Gomez is a Principal Engineer at Lumina Networks. Previously he was a Principal Software Test Engineer in the Open Source Software group at Brocade where he spent 4 years integrating, testing and supporting OpenDaylight in customer solutions, before he was a Solution Integration Engineer at Ericsson where he spent more than a decade integrating and testing service provider networks

Projects

Luis is PTL of integration/distribution and committer in the integration/test, releng/builder, releng/autorelease and docs projects as well as test contact for OpenFlow plugin project. Most of Luis contribution is on test infrastructure and system test for OpenDaylight core components, recent works include common distribution and CSIT for self-managed projects, multi-patch job enhancements and test dashboard for OpenDaylight (ongoing work).

Statement of Intent

My goal for OpenDaylight has always been the same: deliver the quality and usability required for the controller to be broadly consumed and ultimately deployed in production, while fostering projects collaboration and contributors innovation. OpenDaylight has evolved since its start and I believe current users are looking for an stable, flexible and scalable platform they can use to write SDN applications. As a TSC member I would like to work in community matters like: new contributors welcome, lower entry barrier, users technical support, updated documentation, or simpler processes; as well as technical matters like: current platform features and performance competitiveness, integration with new technologies (e.g. kubernetes) or southbound devices interoperability.