Šimon and I collaborated together from 2011-2016 in the formation of Red Hat's OpenSCAP technologies and associated open source communities. Šimon worked within Red Hat's Engineering organization, with myself in our Public Sector CTO office. OpenSCAP development efforts automated security compliance checks -- both configuration and vulnerabilities -- for RHEL-based systems. This automation drove competitive superiority of RHEL-based systems and was among the most visible projects affecting Red Hat's global Government markets. This work was among the top customer requested features of Red Hat Enterprise Linux 7, enhancing the security automation experience for Red Hat customers globally. Over the years, Šimon grew to become a leader of the OpenSCAP community. From a technology perspective Šimon became the upstream maintainer of our SCAP interpreter. Among his many responsibilities, Šimon ran our Scrum sprints -- coordinating across development, sales, and product management to drive our technology roadmap. I quickly began to admire Šimon's skills in stakeholder management, as he carefully balanced aggressive development timelines and realistic schedules while keeping all parties informed. Through his planning, Šimon and his team drove OpenSCAP releases which shipped in several versions of Red Hat Enterprise Linux 6 and 7. Extremely important in open source development, Šimon balanced the rapid development needs of an upstream development community versus stable enterprise releases. For the upstream code base, Šimon focused on making something usable. The code did not need to be feature complete or ultra-reliable, but needed to convey a vision of Security Automation. Establishing a clear vision established an entry point for other developers to get involved -- which included Red Hat's competitors such as Oracle. Šimon forged a reputation where the community took him seriously, and recognized that he's capable of acting as a steward of the community, rather than only a "Red Hat staffer." In addition to his code development role, Šimon helped build the OpenSCAP community. Over 5 years the community grew from less than 5 code contributors to over 100 people across some 25 independent companies. Over 1.3 million lines of code were developed across the OpenSCAP communities. MITRE wrote a report citing OpenSCAP's configuration remediation process as leading industry, something of which other vendors should aspire towards. I have great personal and professional respect for Šimon. As he moves from the OpenSCAP development team to ManageIQ, I wish him all the best -- and I will jump on any opportunity to collaborate again in the future.

Šimon and I collaborated together from 2011-2016 in the formation of Red Hat's OpenSCAP technologies and associated open source communities. Šimon worked within Red Hat's Engineering organization, with myself in our Public Sector CTO office. OpenSCAP development efforts automated security compliance checks -- both configuration and vulnerabilities -- for RHEL-based systems. This automation drove competitive superiority of RHEL-based systems and was among the most visible projects affecting Red Hat's global Government markets. This work was among the top customer requested features of Red Hat Enterprise Linux 7, enhancing the security automation experience for Red Hat customers globally. Over the years, Šimon grew to become a leader of the OpenSCAP community. From a technology perspective Šimon became the upstream maintainer of our SCAP interpreter. Among his many responsibilities, Šimon ran our Scrum sprints -- coordinating across development, sales, and product management to drive our technology roadmap. I quickly began to admire Šimon's skills in stakeholder management, as he carefully balanced aggressive development timelines and realistic schedules while keeping all parties informed. Through his planning, Šimon and his team drove OpenSCAP releases which shipped in several versions of Red Hat Enterprise Linux 6 and 7. Extremely important in open source development, Šimon balanced the rapid development needs of an upstream development community versus stable enterprise releases. For the upstream code base, Šimon focused on making something usable. The code did not need to be feature complete or ultra-reliable, but needed to convey a vision of Security Automation. Establishing a clear vision established an entry point for other developers to get involved -- which included Red Hat's competitors such as Oracle. Šimon forged a reputation where the community took him seriously, and recognized that he's capable of acting as a steward of the community, rather than only a "Red Hat staffer." In addition to his code development role, Šimon helped build the OpenSCAP community. Over 5 years the community grew from less than 5 code contributors to over 100 people across some 25 independent companies. Over 1.3 million lines of code were developed across the OpenSCAP communities. MITRE wrote a report citing OpenSCAP's configuration remediation process as leading industry, something of which other vendors should aspire towards. I have great personal and professional respect for Šimon. As he moves from the OpenSCAP development team to ManageIQ, I wish him all the best -- and I will jump on any opportunity to collaborate again in the future.

Šimon and I collaborated together from 2011-2016 in the formation of Red Hat's OpenSCAP technologies and associated open source communities. Šimon worked within Red Hat's Engineering organization, with myself in our Public Sector CTO office. OpenSCAP development efforts automated security compliance checks -- both configuration and vulnerabilities -- for RHEL-based systems. This automation drove competitive superiority of RHEL-based systems and was among the most visible projects affecting Red Hat's global Government markets. This work was among the top customer requested features of Red Hat Enterprise Linux 7, enhancing the security automation experience for Red Hat customers globally. Over the years, Šimon grew to become a leader of the OpenSCAP community. From a technology perspective Šimon became the upstream maintainer of our SCAP interpreter. Among his many responsibilities, Šimon ran our Scrum sprints -- coordinating across development, sales, and product management to drive our technology roadmap. I quickly began to admire Šimon's skills in stakeholder management, as he carefully balanced aggressive development timelines and realistic schedules while keeping all parties informed. Through his planning, Šimon and his team drove OpenSCAP releases which shipped in several versions of Red Hat Enterprise Linux 6 and 7. Extremely important in open source development, Šimon balanced the rapid development needs of an upstream development community versus stable enterprise releases. For the upstream code base, Šimon focused on making something usable. The code did not need to be feature complete or ultra-reliable, but needed to convey a vision of Security Automation. Establishing a clear vision established an entry point for other developers to get involved -- which included Red Hat's competitors such as Oracle. Šimon forged a reputation where the community took him seriously, and recognized that he's capable of acting as a steward of the community, rather than only a "Red Hat staffer." In addition to his code development role, Šimon helped build the OpenSCAP community. Over 5 years the community grew from less than 5 code contributors to over 100 people across some 25 independent companies. Over 1.3 million lines of code were developed across the OpenSCAP communities. MITRE wrote a report citing OpenSCAP's configuration remediation process as leading industry, something of which other vendors should aspire towards. I have great personal and professional respect for Šimon. As he moves from the OpenSCAP development team to ManageIQ, I wish him all the best -- and I will jump on any opportunity to collaborate again in the future.