Merge pull request #15713 from jmhbnz/create-membership-issue-template

Add issue template for new membership nominations.

.github/ISSUE_TEMPLATE/membership-request.yml

@@ -0,0 +1,30 @@
+name: Membership nomination
+description: Nominate new etcd members
+labels:
+- area/community
+body:
+- type: textarea
+  id: feature
+  attributes:
+    label: Who would you like to nominate?
+  validations:
+    required: true
+
+- id: requirements
+  type: checkboxes
+  attributes:
+    label: Requirements
+    options:
+    - label: I have reviewed the [community membership guidelines](https://github.com/etcd-io/etcd/blob/main/Documentation/contributor-guide/community-membership.md)
+      required: true
+    - label: The members are actively contributing to 1 or more etcd subprojects
+      required: true
+    - label: The members are being sponsored by two current reviewers or a current maintainer.
+      required: true
+
+- type: textarea
+  id: rationale
+  attributes:
+    label: How do the new members meet the regular active contribution requirements?
+  validations:
+    required: true

Documentation/contributor-guide/community-membership.md

@@ -28,7 +28,7 @@ Members are continuously active contributors in the community.  They can have
 issues and PRs assigned to them. Members are expected to remain active 
 contributors to the community.
 
-**Defined by:** Member of the etcd GitHub organization
+**Defined by:** Member of the etcd GitHub organization.
 
 ### Requirements
 
@@ -43,6 +43,9 @@ contributors to the community.
 - Sponsored by one active maintainer or two reviewers.
     - Sponsors must be from multiple member companies to demonstrate integration across community.
     - With no objections from other maintainers
+- Open a [membership nomination] issue against the etcd-io/etcd repo
+    - Ensure your sponsors are @mentioned on the issue
+    - Make sure that the list of contributions included is representative of your work on the project.
 - Members can be removed by a supermajority of the maintainers or can resign by notifying
   the maintainers.
 
@@ -147,7 +150,8 @@ Contributor roles and responsibilities were written based on [Kubernetes communi
 
 [MAINTAINERS]: /MAINTAINERS
 [contributor guide]: /CONTRIBUTING.md
+[membership nomination]:https://github.com/etcd-io/etcd/issues/new?assignees=&labels=area%2Fcommunity&template=membership-request.yml 
 [Kubernetes community membership]: https://github.com/kubernetes/community/blob/master/community-membership.md
 [emeritus maintainers]: /README.md#etcd-emeritus-maintainers
 [security disclosure and release process]: /security/README.md
-[two-factor authentication]: https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication
+[two-factor authentication]: https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication