Stephen is truly one of the unsung heroes of ONAP. He has been an anchor member of the community since the beginning, but works behind the scenes for the most part.  A lot of folks aren't even aware of  the importance of his contributions to the community.  You won't see a lot of measurable criteria associated with what he does as his activity is usually managed via support systems that are not part of the LFX Insights system.  Steven has been instrumental in setting up and maintaining the original Intel/Wind River lab. He has now continued to provide remote sysadmin support for the ONAP UNH Lab following the migration to it.  This is a long overdue recognition of his efforts and contributions to making ONAP a success.

Fiachra stepped in to support the OOM project and helped pull together a community of developers to self-organise and keep OOM running without a PTL. He was very active working on OOM gating issues as they came up, and helped keep ONAP deployments running for the people dependent on it. This contribution involved actively participating in the weekly OOM meetings, Jira management at those meetings, helping to repair the automated verification and gating jobs when they went down and improving documentation. He also willingly took a position as a committer in the project. He has also committed multiple important patches in OOM for DMAAP and Strimzi integration, solving issues and working on removing dependencies for these projects.  This was a great contribution to the ONAP community as this is a central function in the project.       

All this while doing his day job as PTL for DMAAP, another important central function within the project.

During the Jakarta Release, the ONAP Community had to overcome some major challenges.
The OOM/Integration Projects lost their Project Technical Leaders before the sign-off of the release.

Andreas, already known for his voluntarism, took over the remaining tasks for the projects, ensuring through his leadership 
that the quality criteria of our ONAP release were met as expected.

In addition, Andreas's focus is always to operationalize ONAP to be used in production environment, 
sharing his Service Provider's expertise at any opportunity. 

For proposing to use SonarQube quality verification at code verification stage for each commit instead of after merge (too late!). CPS Team worked with ONAP IT to PoC this process and make it reality in Jakarta timeframe.
This improvement means that many security, performance and test coverage issues are caught at an early stage and are prevented from contaminating the master branch. This option is now available for any ONAP java project.

Toine Siebelink  (PTL) and CPS Team for maintaining (over several releases now) the best-class- quality measurements on all CPS Repositories e.g. >97% test cover coverage, 0 bugs, security or vulnerabilities. See  https://sonarcloud.io/summary/overall?id=onap_cps