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 8 Next »

Interim Governing Board representative (March'2018)

  • Nomination Period: March 14-19, 2018
  • Voting Period: March 20 - 23, 2018 (will be done via Condorcet)

If you are interested in running in the interim GB representative election, please enter your nomination statement/bio in the table below by 5pm Pacific Time on March 19th.  

Name/OrganizationNomination Statement/BioNotes
Mazin Gilbert/ATT/ONAP

I will be honored and privileged  to serve this committee on the governing board.

I am currently the technical chair for the Linux Foundation ONAP, where my organization is actively contributing code and leading over half of the TSC projects. My team and I are actively leading or contributing to other open source projects including Acumos Deep Learning, ODL and Akraino  EdgeStack.

Ed Warnicke/Cisco/

I've been involved in Open Source Networking of various sorts for over 15 years, dating back to being a committer on Wireshark in he early 2000s.

I am currently the TSC Chair of the community, was a founding TSC member at OpenDaylight and ONAP, and was immortalized in lego by the OpNFV community.

I feel strongly that its crucial that the TAC represent the technical communities of all the LFN community to the board.

My broad experience across all of the major project technical communities over the last half decade puts me in an excellent position to represent the technical community to the board.

Rossella Sblendido/SUSE

Understanding the communities’ needs and be able to voice them to the GB are the key characteristics of the GB representative we've outlined together.

I’ve been part of several open-source communities in the last years and I’ve gathered a good amount of experience in understanding their needs. I’ve always focused my attention on critical areas. I had been Core Reviewer for OpenStack Neutron for few years. There I pushed for an internship program in a moment when starting contributing to Neutron was hard to say the least. I am currently a member of the TSC of OPNFV. In OPNFV I was an early supporter of the XCI, whose benefits are now known to everybody. 

In SUSE I lead the engineering team that focus on SDN and NFV.  We contribute actively to OPNFV, ODL, data plane projects (i.e., DPDK, ODP, OpenVSwitch) and we plan to get more involved with ONAP . This gives me a good insight on most of the projects of the LF Networking Fund.

With my experience in open-source and my familiarity with the projects of the LF Networking Fund I am sure I could serve the community as GB representative very well.

Wenjing Chu / Huawei

The TAC rep to the GB is a critical role to help make LFN truly a community driven organization.

I was a founding Board member of OPNFV since its inception and also serving as a TSC member and a committer in active projects. Serving in both the Board and TSC gave me good appreciation of how to effectively bring technical community’s voice and priority to the GB and help foster a healthy community.

As an example of my collaborative and transparent style of work, I was the initial chair of the compliance committee that organized its PlugFests and drove the development of the OPNFV Verified program (OVP) and was a committer in the Dovetail project that made it all happen. OVP was recently launched with acclaim by the community and recognized as a core value that open source communities like LFN can provide for the industry. My other recent work is in driving cloud native initiatives which is another example that touches many projects in ONAP/ and upstream.

Maybe I’ll reinforce it with a quick plug for the OPNFV project: since it’s a unique community organized for a focus in upstream and cross project integration, it seems natural for me to broaden my attention scope wider and consider the whole ecosystem. I hope I can bring these qualities and experiences along as a rep for the LFN TAC. Thanks for your trust.

  • No labels