Dear all, I've been elected to the Continuous Delivery Foundation Technical Oversight Committee. Effective July 1st, I will be representing the Jenkins project there. Thanks to everyone for the support during the nomination! I would also like to thank Kohsuke Kawaguchi who has been the official Jenkins' representative to the TOC since the inception of the CDF. These are big shoes to fill.
Many of the contributors know that the last months have not been exactly easy to me. Reactivating the community work has been a huge contributing factor to my recovery, and I will do my best in this new role. I am looking forward to continue representing the Jenkins community in the CDF TOC, now in more official capacity and the binding vote power. You can find my public statement below. Let me rather focus on how Jenkins and the CDF TOC collaboration will look like going forward: - CDF Technical Oversight Committee is an open group. I do NOT consider myself as a single point of contact between Jenkins and the CDF TOC. Any Jenkins community member is welcome to participate in the TOC meetings. It is not a case for some other entities like the Outreach committee unfortunately. Everyone is invited to participate in the CDF TOC and to bring up topics in the meetings/GitHub/mailing lists. - I will be a liaison to the CDF TOC from the Jenkins project. I will do my best to participate in the CDF TOC meeting and to bring up topics from contributors there if they cannot attend on their own. I will also be a liaison of the CDF TOC in the Jenkins community, and I will be bringing up the key topics from it in the Jenkins community channels. - I consider the CDF TOC representative role as a lower ranking role being compared to the open governance process <https://www.jenkins.io/project/governance/>, not a higher one like someone may assume. A CDF TOC Representative IMHO "reports" to the Jenkins community. The binding vote also represents the Jenkins community, and hence the Jenkins governance process should be applied when possible and feasible. As a representative I will vote based on the community decisions, not on my personal opinion. The key word is "when possible and feasible", we will need to figure out what that means on a case-by-case study - As the CDF TOC member I will often operate on higher level than just the Jenkins project. My responsibilities will be to facilitate the entire CDF ecosystem, not just the Jenkins project. I will also work with foundations beyond the CDF. Personally I that the strong CD ecosystem is what Jenkins end users actually need, regardless of where a particular capability is implemented. I hope it will be a win-win in the most of cases, but there is a potential risk of conflict of interest between the community and the CDF. Should such situation occur, I will inform the Jenkins governance board immediately to agree on how we handle it. - I invite any experienced contributors to become "shadow CDF TOC representatives" if they are interested. We can work with the CDF to ensure that there is a "deputy representative" role introduced so that a Jenkins contributor could apply a binding vote should I be unable to do so due to any reason. Same for the seat inheritance should I be unable to continue in the role before the end of the term. Maybe the CDF TOC Representative role should be formally documented in a JEP, will appreciate any opinions and suggestions. And again, thanks to everyone for your support! Looking forward to make a difference in the CDF. Best regards, Oleg Nenashev *My public statement (LinkedIn post <https://www.linkedin.com/posts/onenashev_cdfoundationtoc-activity-6804399697592123392-Nmfe>)* *I've been elected to the Continuous Delivery Foundation Technical Oversight Committee. Effective July 1st, I will be representing the Jenkins project there. Thanks to all community members for their support! My main responsibility will be to facilitate technical programs among the CDF, its member companies and projects: Jenkins project, Tekton, Spinnaker, Jenkins X, Ortelius Open Source, Screwdriver.CD and other members yet to join. I will help all the projects to grow their community and improve governance processes. Another priority will be interoperability between projects so that the end users can easily combine them for their software delivery needs. I will work with the CDF special interest groups to define a public technical roadmap, including but not limited to interoperability and security.I will also facilitate collaboration with CDF end users, and other open software and hardware organizations, e.g. The Linux Foundation, CNCF [Cloud Native Computing Foundation], RISC-V International, Inclusive Naming Initiative, TODO (OSPO) Group, OpenSSF, Open Source Design, etc.Looking forward to this new role and to working with all TOC participants! Thanks to CloudBees for backing it with working time. And kudos to all contributors!* -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ae7fc5f7-128b-464c-8c66-71e41ac3fb74n%40googlegroups.com.
