Skip to end of banner
Go to start of banner

2022 OpenDaylight TSC Election

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

This election and nomination process is for those individuals who have committer rights on one or more OpenDaylight Projects and Active Community Members (ACM). All OpenDaylight Committers and ACMs can nominate themselves, run for election, and vote in the election for the Committer-At-Large seats on the TSC. 

  • A Committer is a contributor that has the authority, and responsibility to submit changes to an OpenDaylight software repository.
    • 5 seats
  • Active Community Members: Anyone from the OpenDaylight community with twenty (20) or more measurable contributions during the previous 12-month period, inclusive of code merged, code reviews performed, wiki page edits, or JIRA activities.
    • 2 seats

Details on the election process may be found here.

Dates to Remember

Nomination Period:  to  

Voting Period:   to  


Information on Candidates

When self-nominating, please provide the following:

@Candidate Name

Picture

Biography

Committer / ACM seat designation

Statement of Intent


@Guillaume Lambert

Biography


Guillaume Lambert is a Telecommunication Engineer and has been working for Orange since 2003.
He has been interested in Open Source and Free Software since he was graduating at ENST Bretagne and he took part to its Linux User Groups and to the "Groupe de Réflexion et d'Animation Autour du Libre" .
During his carreer at Orange, he was involved in various in-house developments and deployments, for example on Single-Sign-On platforms based on Liberty Alliance specifications or on IP Networks Monitoring systems relying on Netflow/IPFIX.
Guillaume joined Orange Labs transmission department in 2015 and the OpenDaylight Community in 2016. Since then, he has been actively promoting and contributing to it.

He is currently the TSC chairman and the documentation PTL, and a committer of transportpce and releng/builder projects .
He has been the PTL of the transportPCE project until 2021 and is occasionally contributing to others projects such as BGPCEP.


Committer / ACM seat designation
both, preferably committer seat

Statement of Intent

I would like to promote OpenDaylight as a network controller implementation of reference.
There are lots of challenges today in the area of open and interoperable standards.
And I believe OpenDaylight is one of the best platform to implement these new standards or to speed up their adoption, but also to mutualize companies effort to this end.
During these last years, I had also to take the train on the way and to learn from scratch how to integrate transportPCE to the OpenDaylight official distributions.
I think that my experience benefits the TSC to improve our operating modes inside the community and to attract new contributors.
This last topic is getting more and more important since OpenDaylight has now a strong legacy and higher requirements for quality that are faced by newcomers.


Venkatrangan Govindarajan


Biography

I have been involved with opendaylight since the first release (Hydrogen) across various projects like vtn, Integration/Test, Netvt, OVSDB, AAA.

I have been a TSC Member for the past two years. I work as a Product Owner of SDN  at Rakuten Symphony. I am working to bring the ODL projects in possible

use-cases. 

Committer / ACM seat designatio

 Both


Statement of Intent

  • Would like to work with different projects and help create more micro distributions.
  • Would like to improve documentation of new use-cases like slicing with ODL
  • Would like to involve more in collaboration with other communities like ONAP.
  • Would like to write more technical blogs/tweets writeups on ODL and use-cases




@Manoj Chokka

Picture

Biography

I have been working in Verizon since 2019 in the SDN planning department.

We have been working on enabling Verizon's network to migrate to SDN enabled networks. 

Committer / ACM seat designation

ACM seat

Statement of Intent

ODL is very stable but it is also monolithic. We need a way that more people can adopt ODL with relative ease.

There are a lot of problems that need to be sorted out. Some of which can be sorted by aligning ODL to latest deployment methodologies.

I intend to help ODL be adopted by more and more companies. 

I also intend help the community grow in terms of participation and contribution. 



@Anil Belur

Picture

Biography

Anil has been serving the OpenDaylight project since 2016 (since the Boron SR2 release), with release management and engineering activities and is an active maintainer of the LF/releng* repositories. He's works closely with the developer community supporting projects, performs timely releases and maintains the infrastructure for the project.

During the late 90's he began his journey learning Linux, and started his career with Novell and got an opportunity to contribute to Open Source (MIT Kerberos). He's has worked in the areas of Security & Identity Management, Networking, Systems, Devops and Release engineering with firms like Goldman Sachs, HP and Redhat. He is always inclined to experiment and learn new technologies and has a keen interest on the developments in OSS, security and deep learning.

Committer / ACM seat designation

Either

Statement of Intent

* Migrate existing CI jobs from Jenkins freestyle jobs to Jenkins pipelines.
* In the past year, I have led the work on containerize ODL using docker/K8S pods/clusters. This gives an opportunity for new developers to deploy/test ODL as a container. There are more use-cases that could added and with potential for migrating CSIT jobs to start using ODL on K8S environment.
* Improve processes and workflows within OpenDaylight, ensuring best practices are shared across LF projects.
* Optimize ODL's CI infrastructure to improve CI/job performance with a focus on quality, metrics and minimize downtime.
* Continue making OpenDaylight Simultaneous Releases in a timely manner.
* Facilitate new developers to contribute to ODL and automate the infrastructure.
* Improve documentation that would benefit larger developer community.



  • No labels