Request for taking over DOI maintainership

Dear team, we (HAProxy Technologies) would like to ask if it is possible to transfer/take over HAProxy DOI maintainership to us. We would also like to know of the exact steps that are required to do this on both sides.

We are currently maintaining haproxytech/haproxy-* images which unnecessarily create a fork in the community, instead of unifying our efforts with the community and Docker. We also have a number of improvements planned:

1. Add a HAProxy variant with s6-overlay and Dataplaneapi enabled by default for the future K8s Gateway API project as well as some other incoming community-related projects (instead of running dataplaneapi as a program within HAProxy),
2. Add a HAProxy variant with AWS-LC OpenSSL replacement instead of problematic OpenSSL 3.x,
3. Add more distribution variants, like we have in haproxytech/haproxy-* images.
4. Further streamline and automate new HAProxy release builds

We have obtained "Verified Publisher" status and plan to collaborate with Docker community even better in the future.

This issue concerns transferring HAProxy Docker Official Image maintainership and coordinating future image variants and release automation. Start by reviewing the issue discussion and the existing DOI ownership process; done requires agreement on the transfer steps and ownership, not a defined code change.