validations:
      required: true

  - type: markdown
    attributes:
      value: >
        Comparing two approaches to a use case side by side can make it easier to examine the
        differences between them.


        Additionally, it's very useful to us if you can provide a "straw API" — what the

    This file is part of the GNU C Library.
 
    The GNU C Library is free software; you can redistribute it and/or
@@ -14,7 +14,7 @@
 
    You should have received a copy of the GNU Lesser General Public
    License along with the GNU C Library; if not, see
-   <http://www.gnu.org/licenses/>.  */
+   <https://www.gnu.org/licenses/>.  */
 
 #ifndef _UTMP_H

enabled: true # Default excludes istio-system; its actually fine to redirect there since we opt-out istiod, ztunnel, and istio-cni excludeNamespaces: - kube-system manifests/charts/gateways/istio-ingress/NOTES.txt Changes: - separate namespace allows: -- easier reconfig of just the gateway -- TLS secrets and domain name management is isolated, for better security -- simplified configuration -- multiple versions of the ingress can be used, to minimize upgrade risks - the new chart uses the default namespace...

    validations:
      required: false

  - type: textarea
    id: learning-curve
    attributes:
      label: "Would this change make Go easier or harder to learn, and why?"

  - type: textarea
    id: cost-description
    attributes:
      label: "Cost Description"
      description: "What is the cost of this proposal? (Every language change has a cost)"

        By asking questions in a structured way (following this) it will be much easier to help you.

        And there's a high chance that you will find the solution along the way and you won't even have to submit it and wait for an answer. 😎