-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Backend Protocol Section to implementators guide #2453
Comments
/assign @youngnick - who's working on this now |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Hmm, I had forgotten about this. The implementer's guide has now been, well, implemented, and is ready for someone to take the table that's currently in GEP-1911 (at https://gateway-api.sigs.k8s.io/geps/gep-1911/#supporting-protocols) and add a section that:
This is a reasonably straightforward documentation fix that is suitable for a new contributor. /help |
@youngnick: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/unassign |
/assign @dprotaso |
/assign @joerober |
@dprotaso: GitHub didn't allow me to assign the following users: joerober. Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Comment: #2444 (comment)
The text was updated successfully, but these errors were encountered: