Hi Sergey, This sounds reasonable to me. Since flink-ci-docker is a critical part of the Flink CI infrastructure, having it managed under Apache seems beneficial from a maintainability perspective. It should also make future work, such as JDK upgrades and CI environment changes, easier to coordinate across the community. Best, Chanhae Oh
________________________________ From: Sergey Nuyanzin <[email protected]> Sent: Tuesday, June 2, 2026 17:19 To: [email protected] <[email protected]> Subject: [DISCUSS] Move flink-ci-docker under Apache Hi everyone We use flink-ci-docker in Flink CI pipelines. The main issue is that each time we want to update it there are only a few or even a single person who can approve/merge it. It was under flink-ci[1], then[2] where most of Flink committers do not have access. The proposal is to move it under Apache in a similar way as it is done for flink-shaded/connectors. Then it will unblock activities like movements towards jdk25[3] and especially[4], where there is a need to add jdk25 to flink--ci-docker, I'd like to raise this [1] https://github.com/flink-ci/flink-ci-docker [2] https://github.com/zentol/flink-ci-docker [3] https://issues.apache.org/jira/browse/FLINK-37719 [4] https://issues.apache.org/jira/browse/FLINK-39739 -- Best regards, Sergey
