Request for taking over DOI maintainership
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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:
- 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),
- Add a HAProxy variant with AWS-LC OpenSSL replacement instead of problematic OpenSSL 3.x,
- Add more distribution variants, like we have in
haproxytech/haproxy-*images. - 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.
- Dominant language
- Shell
- Stars
- 383
- Forks
- 162
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker-library/haproxy
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
docker-library/haproxy#237 · 5 comments · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
docker-library/haproxy#217 · 4 comments ·
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
docker-library/haproxy#142 · 3 comments ·
All issues in docker-library/haproxy
Similar issues
-
Issue-Enhancement Needs-Triage
Difficulty 1/5 Under an hour Newbie friendliness 86/100
PowerShell/PowerShell#28061 · 2 reactions ·
-
Feature Request: Add ability to load custom environment variables in linux-exec-server-installer.sh Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/vscode-remote-release#11867 ·
-
AuTest Bug Tests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/trafficserver#13714 ·
-
Update to NCCL 2.32 Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
conda-forge/nccl-feedstock#166 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
vllm-project/agentic-api#358 · 1 comment ·