- type: textarea
    id: generics-proposal
    attributes:
      label: Is this about generics?
      description: If so, how does this relate to the accepted design and other generics proposals?
      placeholder: |
       Yes or No

       If yes, 
        1. how does this relate to the accepted design and other generics proposals?

    validations:
      required: true

  - type: textarea
    id: proposal

        that it's for a use case that actually comes up in the real world. We want to hear the
        real-world use case so the community can discuss and debate whether this feature is actually
        the *best* way to address the real use case, or whether or not a different approach might be
        more appropriate.

republican res.aero res.in research.aero research.museum reservd.com reservd.dev.thingdust.io reservd.disrec.thingdust.io reservd.testing.thingdust.io reserve-online.com reserve-online.net resindevice.io resistance.museum rest restaurant restaurant.bj resto.bj review reviews revista.bo rexroth rg.it rhcloud.com ri.it ri.us ribeirao.br ric.jelastic.vps-host.net rich richardli ricoh rieti.it rifu.miyagi.jp riik.ee rikubetsu.hokkaido.jp rikuzentakata.iwate.jp ril rimini.it rindal.no ringebu.no ringerike.no...

      }[primary] or "#ffffff" }}
    {%- endif -%}

  # Font family (default: Roboto)
  - &font_family >-
    {%- if layout.font_family -%}
      {{ layout.font_family }}
    {%- elif config.theme.font != false -%}
      {{ config.theme.font.get("text", "Roboto") }}
    {%- else -%}
      Roboto
    {%- endif -%}

  # Site name
  - &site_name >-
    {{ config.site_name }}

  homepage: https://maven.apache.org/ref/current
  labels:
    - java
    - build-management
    - apache-maven
    - maven
    - hacktoberfest
  enabled_merge_buttons:
    squash: true
    merge: false
    rebase: true
  autolink_jira:
    - MNG
notifications:
  commits: ******@****.***
  issues: ******@****.***
  pullrequests: ******@****.***

        Before new features get added to Guava, we really want to be sure that it's for a use case
        that actually comes up in the real world. We want to hear the real-world use case so the
        community can discuss and debate whether this feature is actually the *best* way to address
        the real use case, or whether or not a different abstraction might be more appropriate.