...
Top Achievement Award
Citizenship Award
Marketing Award
Code Contribution Award
Project Achievement Award
Innovation Award
Marketing Award
Top Achievement Award Anchortop top
top | |
top |
...
Chris has performmmed extremely valuable work in the TSC and ARC. The important works include: education, guidance and review on how to develop and communicate in open source team. Whose behavior really help to create a culture equal cooperation between members, it’s really important for ONAP as a new community.
Dan Rose:
Dan has provided assistance to many people through responses on the onap-discuss mailing lists, wiki question answers, presentations of the end to end platform, and working with many projects to create an end to end integration test of the platform. For example, he ranks 4th on emails sent list and provided assistance on broad range of topics at detailed technical levels.
Eric Debeau:
Eric always made himself available to other teams whereever and whenever thet needed his help. He produced a great deal of documebntation and played a key role in making necessarry updates and changes in Readthedocs for the release.
...
Rich has provided unparalleled Documentation support from the very beginning of ONAP (even pre-Amsterdam). Though much of his work has been “behind the scenes”, Rich has been instrumental in insuring the success of ONAP through his work in developing, testing and implementing the technical components and structure needed to support documentation. Among his many contributions Rich Coordinated much of the seed documentation, including initial Developer Guides, Tested and troubleshot Documentation Tool Chain development, Established and supported Jenkins job flows, Tested and implemented Readthedocs structure, Provided ongoing technical support for all ONAP project teams and Developed Amsterdam branching strategy.
...
...
Code Contribution Award Anchor
...
code
code |
...
code
code |
Presented to the individual software contributor who provided the most support to the Marketing and PR teams, and generated and/or supported development of documentation, videos, tutorials, press/analyst interviews, webinars, etcdeveloped the highest quantity of quality code as judged by the PTLs, Committers and Contributors.
Nominees:
Alla Goldner:
- Led Tel Aviv hackathon, in partnership with local AT&T and Cloudify teams
- Spoke at L123 mini-summit
Chris Donley:
- Lead writer of architecture whitepaper, with Paul Bartoli of AT&T; coordinated all feedback within the Architecture committee
- Regular speaker on behalf of ONAP at events around the globe
- Contributed key architecture overview video
Jamil Chawki:
- Site host for OSN Day, Paris
- Site host for OSN Day, Paris
Lingli Deng:
- Regular speaker on behalf of ONAP at events around the globe
- Contributed 2 technical videos in English, 3 in Chinese
- Led review team for VoLTE whitepaper
- Frequent coordinator of Chinese contributions to marketing and marketing-related activities
Nermin Mohammed:
- European City Tour lead and London site host and speaker; also help co-sponsor and co-organize Paris event
- Significant contributor to:
- ONAP core messaging and FAQ
- Initial ONAP U proposal
- Leader of Amsterdam promotion activity in China
- Organized press release translation between Huawei & ZTE; also contributed member quote sheet translation
- Organized CMCC-Huawei Amsterdam launch ceremony in China, with video
- Primary driver of Chinese press coverage, with at least 9 unique articles
Yoav Kluger:
- Contributed 2 use case videos
- Designated SME/reviewer for Residential vCPE whitepaper
...
Dan Timony:
Dan Timoney not only serves as PTL for the CCSDK and SDNC projects but he has also contributed a significant amount of quality code to ONAP for the Amsterdam project. Dan has been on the leading edge of the controller technology in ONAP and his contributions to the CCSDK sets the foundation for multiple controllers to be built upon. Dan consistently ranks near the top of software contributions across the ONAP projects. Besides the quantity of code that Dan has delivered, his deliveries have been high quality with very few defects. Dan’s contributions to Amsterdam, not only around software delivery but also partner collaboration, qualifies him as a worthy recipient of this award.
Honghui Xiao:
Honghui's work on hierarchical binding based integration with the third party SDN controller. HongHui is an active contributor in multi-vim/cloud project. He also plays an important part in the integration of use cases. In VoLTE use case, there is a requirement to connect two data centers by using EVPN/VXLAN. Normally, this is done by connecting OpenStack with some specific networking hardware. Networking hardware vendor will provide solution of connecting based on OpenvSwitch. However, there is no EVPN support in VIO (VMware Integrated OpenStack), nor did VIO support OpenvSwitch. And VIO is deployed in one of the data center. So, there is problem of connecting two data centers. To solve this problem, HongHui did some investigation about how OpenvSwitch connects to the specific networking hardware, how OpenStack orchestrates such connection and how VMware VDS (virtual distributed switch) works. And then he delivered a driver to connect VMware VDS and specific networking hardware. There are only about 100 lines of code in the driver. However, the code, which has been proven by VoLTE use case, can be said neat and stable.
Jinhua Fu:
As the main committer of VF-C, Jinhua Fu made outstanding contributions to the implementation of VF-C's main functions in Amsterdam release, including not only code contributions and testing, but also technology sharing. It did a lot of tentative work and provided effective guidance to all team members. From ONAP community Git contribution rankings(2017-06-01~2017-12-05), His code contribution also ranked in the top three.
Jorge Hernandez-Herrero:
Jorge set an incredible high standard when it came to pulling together the Policy code for Amsterdam. He designed and built a telemetry API on top of the Drools PDP Controller which enabled the community to more easily debug Control Loop scenarios. He led a team of developers to enhance the development environment for building and testing Policy Templates that the community will be able to begin utilizing going forward. Jorge set a high standard when accepting code submissions and displayed a keen eye when came to identifying how submissions for one repository would have an effect upon another repository. Jorge also provided the majority of support to the Integration team, forgoing vacation time and weekends, when it came to testing and supporting the Use Case testing.
Kanagaraj Manickam:
Contributed to ONAP CLI project with high-quality code and made this project to achieve the highest score in quality gate (sonar) with
a. 1st in code coverage (82.5 %) across ONAP projects.
b. ONAP CLI project quality gate Status: green
c. Duplicate code count: 0 (zero)
Implemented maximum no. of commits as well as commands (90%, 79/87 commands) in ONAP CLI project.
Lusheng Ji:
Lusheng Ji was a committer and major contributor to DCAE open source seed code and a substantially new version, DCAEGEN2. In delivering DCAEGEN2, Lusheng contributed to Amsterdam use cases, establishment of test labs, and integration tests.
Murali Mohan Murthy Potham (Murali P):
He was the top contributor in the VNFSDK project, leading the development of the marketplace component. As part of the work, he migrated from mysql to PostgreSQL and refactored significant portions of the web ui. This resulted in significantly REDUCING the size of the vnfsdk codebase. I think Murali deserves credit for putting clean code over lines of code as our driving metric.
Patrick Brady:
Patrick Brady was a committer on the APPC project; he delivered high quality code, but also debugged issues in other projects (e.g. CCSDK) and made these changes in those other projects to unblock APPC. He made extensive contributions to the code base and was prime for the Gerrit/GIT repo management.
Ruijing Guo:
Ruijing Guo worked on multiple projects in ONAP including Policy, SDNC, Multi-VIM etc. His code quality is high. During Amsterdam, overall he submitted 47 commits which caused 160K+ lines were changed. Most of his patches are to merge seed code from OpenECOMP to ONAP and fix critical sonar issues in policy, setup ONAP demo, fix build issues in SDNC, and setup test framework for multi-VIM. The biggest patch he made (https://gerrit.onap.org/r/#/c/6081/) is to replace OpenECOMP with ONAP for policy-engine together with the project PTL Pamela Dragosh. That patch review lasted 10 day and the commit caused 161066 lines added and 161064 lines removed. At the first glance, the commit was mostly physical work however after replacing and renaming, he needed to fix build errors and make the component run correctly. The policy-engine was the biggest part in policy merging, and its code changes were taken very carefully before the commit was merged. Finally it helped the entire policy merging process succeeded.
Sebastien Determe:
In addition to the code that he was developing in the context of the CLAMP project, Sebastien has increased the test coverage beyond the original test coverage target. He added jUnit test cases in various areas of the project even if he was not responsible of the associated source code.
Seshu Kumar:
If there is someone who can do something to make a difference and impact positively the community it is Seshu. Seshu played important role in leading SO project reach the critical milestones, esp the M4 and further where the time was critical. He also helped in resolving some of the blocking issues on time, which helped ONAP deliver the release ontime. Seshu has been the top contributors from the number of commits and ranked amongst the top 5 authors in the ONAP community and has been consistent in his contributions. He has also provided multiple Tech talks on ONAP and SO in various forums and branded ONAP in IIT Madras one of renowned universities.
Yunlong Ying:
In Amsterdam version, Yunlong undertook and completed several important functions of VFC project development and testing, contribute a lot of code, become one of the main contributors to VFC Project, from Onap community Git contribution rankings(2017-06-01~2017-12-05), Yunlong is the highest contributor.
...
Project Achievement Award Anchor proj proj
proj | |
proj |
Presented to the Project which made the most significant technical progress while delivering all milestones on time, serving as a model for other projects to follow.
Nominees:
The AAI Team:
Throughtput the Amsterdam cycle they have been stepping up to help teams understand how to use AAI and how to either correct they way they were using it or to help work around knowledge gaps and or bugs in the system. The project met their milestones with a process the emphasized teamwork across all the various piece parts of AAI.
The CCSDK Team:
The CCSDK project has set the foundation as the software base of all controllers to be built upon. It’s integration with OpenDaylight as well as its directed Graph technology allows projects to quickly build SDN services in the controller space. The directed graph technology allows programmers to easily access the necessary adaptors to enable service provisioning. The contributions of CCSDK were not only used by the Application Controller (APP-C) but also the SDN-C project to quickly build and enable the defined user cases for the Amsterdam release.
The CLAMP Team:
Although this project was not originally part of the ONAP launch and was not identified as a Amsterdam gating project, the CLAMP project delivered all milestones on time. In addition, CLAMP is one of the key components of the Control Loop that it provides the necessary automation to proactively respond to network and service conditions without human intervention. Along the Release, CLAMP always got things right the first time. There is barely anything CLAMP had to redo. The Team is mastering all the aspects of the development lifecycle, processes and tool chain. CLAMP is
...
Presented to the software contributor who developed the highest quantity of quality code as judged by the PTLs, Committers and Contributors.
Nominees:
Dan Timony:
Dan Timoney not only serves as PTL for the CCSDK and SDNC projects but he has also contributed a significant amount of quality code to ONAP for the Amsterdam project. Dan has been on the leading edge of the controller technology in ONAP and his contributions to the CCSDK sets the foundation for multiple controllers to be built upon. Dan consistently ranks near the top of software contributions across the ONAP projects. Besides the quantity of code that Dan has delivered, his deliveries have been high quality with very few defects. Dan’s contributions to Amsterdam, not only around software delivery but also partner collaboration, qualifies him as a worthy recipient of this award.
Honghui Xiao:
Honghui's work on hierarchical binding based integration with the third party SDN controller. HongHui is an active contributor in multi-vim/cloud project. He also plays an important part in the integration of use cases. In VoLTE use case, there is a requirement to connect two data centers by using EVPN/VXLAN. Normally, this is done by connecting OpenStack with some specific networking hardware. Networking hardware vendor will provide solution of connecting based on OpenvSwitch. However, there is no EVPN support in VIO (VMware Integrated OpenStack), nor did VIO support OpenvSwitch. And VIO is deployed in one of the data center. So, there is problem of connecting two data centers. To solve this problem, HongHui did some investigation about how OpenvSwitch connects to the specific networking hardware, how OpenStack orchestrates such connection and how VMware VDS (virtual distributed switch) works. And then he delivered a driver to connect VMware VDS and specific networking hardware. There are only about 100 lines of code in the driver. However, the code, which has been proven by VoLTE use case, can be said neat and stable.
Jinhua Fu:
As the main committer of VF-C, Jinhua Fu made outstanding contributions to the implementation of VF-C's main functions in Amsterdam release, including not only code contributions and testing, but also technology sharing. It did a lot of tentative work and provided effective guidance to all team members. From ONAP community Git contribution rankings(2017-06-01~2017-12-05), His code contribution also ranked in the top three.
Jorge Hernandez-Herrero:
Jorge set an incredible high standard when it came to pulling together the Policy code for Amsterdam. He designed and built a telemetry API on top of the Drools PDP Controller which enabled the community to more easily debug Control Loop scenarios. He led a team of developers to enhance the development environment for building and testing Policy Templates that the community will be able to begin utilizing going forward. Jorge set a high standard when accepting code submissions and displayed a keen eye when came to identifying how submissions for one repository would have an effect upon another repository. Jorge also provided the majority of support to the Integration team, forgoing vacation time and weekends, when it came to testing and supporting the Use Case testing.
Kanagaraj Manickam:
Contributed to ONAP CLI project with high-quality code and made this project to achieve the highest score in quality gate (sonar) with
a. 1st in code coverage (82.5 %) across ONAP projects.
b. ONAP CLI project quality gate Status: green
c. Duplicate code count: 0 (zero)
Implemented maximum no. of commits as well as commands (90%, 79/87 commands) in ONAP CLI project.
Lusheng Ji:
Murali Mohan Murthy Potham (Murali P):
He was the top contributor in the VNFSDK project, leading the development of the marketplace component. As part of the work, he migrated from mysql to PostgreSQL and refactored significant portions of the web ui. This resulted in significantly REDUCING the size of the vnfsdk codebase. I think Murali deserves credit for putting clean code over lines of code as our driving metric.
Patrick Brady:
Patrick Brady was a committer on the APPC project; he delivered high quality code, but also debugged issues in other projects (e.g. CCSDK) and made these changes in those other projects to unblock APPC. He made extensive contributions to the code base and was prime for the Gerrit/GIT repo management.
Ruijing Guo:
Ruijing Guo worked on multiple projects in ONAP including Policy, SDNC, Multi-VIM etc. His code quality is high. During Amsterdam, overall he submitted 47 commits which caused 160K+ lines were changed. Most of his patches are to merge seed code from OpenECOMP to ONAP and fix critical sonar issues in policy, setup ONAP demo, fix build issues in SDNC, and setup test framework for multi-VIM. The biggest patch he made (https://gerrit.onap.org/r/#/c/6081/) is to replace OpenECOMP with ONAP for policy-engine together with the project PTL Pamela Dragosh. That patch review lasted 10 day and the commit caused 161066 lines added and 161064 lines removed. At the first glance, the commit was mostly physical work however after replacing and renaming, he needed to fix build errors and make the component run correctly. The policy-engine was the biggest part in policy merging, and its code changes were taken very carefully before the commit was merged. Finally it helped the entire policy merging process succeeded.
Sebastien Determe:
In addition to the code that he was developing in the context of the CLAMP project, Sebastien has increased the test coverage beyond the original test coverage target. He added jUnit test cases in various areas of the project even if he was not responsible of the associated source code.
Seshu Kumar:
If there is someone who can do something to make a difference and impact positively the community it is Seshu. Seshu played important role in leading SO project reach the critical milestones, esp the M4 and further where the time was critical. He also helped in resolving some of the blocking issues on time, which helped ONAP deliver the release ontime. Seshu has been the top contributors from the number of commits and ranked amongst the top 5 authors in the ONAP community and has been consistent in his contributions. He has also provided multiple Tech talks on ONAP and SO in various forums and branded ONAP in IIT Madras one of renowned universities.
Yunlong Ying:
In Amsterdam version, Yunlong undertook and completed several important functions of VFC project development and testing, contribute a lot of code, become one of the main contributors to VFC Project, from Onap community Git contribution rankings(2017-06-01~2017-12-05), Yunlong is the highest contributor.
...
Presented to the Project which made the most significant technical progress while delivering all milestones on time, serving as a model for other projects to follow.
Nominees:
The AAI Team:
Throughtput the Amsterdam cycle they have been stepping up to help teams understand how to use AAI and how to either correct they way they were using it or to help work around knowledge gaps and or bugs in the system. The project met their milestones with a process the emphasized teamwork across all the various piece parts of AAI.
The CCSDK Team:
The CCSDK project has set the foundation as the software base of all controllers to be built upon. It’s integration with OpenDaylight as well as its directed Graph technology allows projects to quickly build SDN services in the controller space. The directed graph technology allows programmers to easily access the necessary adaptors to enable service provisioning. The contributions of CCSDK were not only used by the Application Controller (APP-C) but also the SDN-C project to quickly build and enable the defined user cases for the Amsterdam release.
The CLAMP Team:
Although this project was not originally part of the ONAP launch and was not identified as a Amsterdam gating project, the CLAMP project delivered all milestones on time. In addition, CLAMP is one of the key components of the Control Loop that it provides the necessary automation to proactively respond to network and service conditions without human intervention. Along the Release, CLAMP always got things right the first time. There is barely anything CLAMP had to redo. The Team is mastering all the aspects of the development lifecycle, processes and tool chain. CLAMP is excellent to get things running as it should, and should be treated as “Best in Class” for all its deliverables.
...
Presented to the Project which delivered a new compelling feature or capability in ONAP (not originally delivered in Open-O or Ecomp) that has significantly impacted ONAP in one or more areas including but not limited to architecture, integration, SDOs or security.
Nominees:
Architecture Subcommittee “Tiger Team”
...
This project was started as an attempt to deploy ONAP services without relying on a OpenStack deployment. The Vagrant project provides an automated tool to provision ONAP development environment and it can be used during the development cycle. This tool covers some common development tasks such as the cloning source code repositories of specific component, compile java artifacts per component and building Docker images of specific component. The tool has been standardized for its reutilization and since this tool provides an automated provisioning mechanism it’s possible to setup a development environment using a single instruction resulting in a quick way for new developers to easily start to contribute. This is an excellent innovation to save valuable time and get an ONAP environment up and running in no time. Also adding this tool into a CICD pipeline can help to prevent any compilation failure in the future and guarantee that build image process is working any time. Victor started this project on April 25 and has been doing most of the changes. Victor contributed over 100 commits and over 8000 lines of code to this project. For now, Vagrant tool is part of the integration project but it will most likely be moved to its own repo and will be possibly renamed. Helen Chen (PTL of Integration project) is aware of this project and also the SDC developers have been contributing to this as well.
...
Marketing Award Anchor mkt mkt
mkt | |
mkt |
Presented to the individual who provided the most support to the Marketing and PR teams, and generated and/or supported development of documentation, videos, tutorials, press/analyst interviews, webinars, etc.
Nominees:
Alla Goldner:
- Led Tel Aviv hackathon, in partnership with local AT&T and Cloudify teams
- Spoke at L123 mini-summit
Chris Donley:
- Lead writer of architecture whitepaper, with Paul Bartoli of AT&T; coordinated all feedback within the Architecture committee
- Regular speaker on behalf of ONAP at events around the globe
- Contributed key architecture overview video
Jamil Chawki:
- Site host for OSN Day, Paris
- Site host for OSN Day, Paris
Lingli Deng:
- Regular speaker on behalf of ONAP at events around the globe
- Contributed 2 technical videos in English, 3 in Chinese
- Led review team for VoLTE whitepaper
- Frequent coordinator of Chinese contributions to marketing and marketing-related activities
Nermin Mohamed:
- European City Tour lead and London site host and speaker; also help co-sponsor and co-organize Paris event
- Significant contributor to:
- ONAP core messaging and FAQ
- Initial ONAP U proposal
- Leader of Amsterdam promotion activity in China
- Organized press release translation between Huawei & ZTE; also contributed member quote sheet translation
- Organized CMCC-Huawei Amsterdam launch ceremony in China, with video
- Primary driver of Chinese press coverage, with at least 9 unique articles
Yoav Kluger:
- Contributed 2 use case videos
- Designated SME/reviewer for Residential vCPE whitepaper