Add TAG leadership election governance template

tags/resources/tag-formation-templates/template-leadership-election-process.md

@@ -1,3 +1,87 @@
 # Leadership election process within the `<TAG NAME>`
 
-*tbd* - contributions are welcome!
+<!--
+This file is a template which can be used by TAGs to bootstrap their governance structure.
+Please review this file carefully and make adjustments to better fit your TAG where needed.
+-->
+
+The TAG leadership as well as the leadership of working groups or projects follows a common set of rules to ensure a transparent, open and accessible role transition between contributors.
+Contributors in leadership positions provide guidance and directions to TAG members and ensure that the efforts are in line with its mission and values, as well as the goals of the TAG.
+Roles within the TAG outlining expectations and responsibilities are defined in the [roles](template-roles.md) governance document. <!-- ! UPDATE THE LINK ! -->
+
+## Process of nominations
+
+Leadership roles are open to all interested participants within the community. Depending on the needs of the community, as determined by the current TAG leadership team (Chairs and TLs), nominations may come from working group co-chairs, TAG co-chairs and/or tech leads and/or other community members. Each TAG is expected to define this for themselves.
+
+The `<TAG NAME>` does not have a current limit on the amount of leadership roles. <!-- ! UPDATE IF DISCUSSED OTHERWISE ! -->
+
+Final nominations will adhere to the [CNCF's TOC described process](https://github.com/cncf/toc/blob/main/tags/cncf-tags.md#elections) as well as to the leadership nomination requirements described below.
+
+Any individual who is a member of the `<TAG NAME>`, its working groups, or otherwise considered an active participant of the group may nominate another individual. <!-- Update if your TAG has a more restricted pool of nominators -->
+
+The process of endorsing and selecting individuals will consider the following factors to ensure both the need for proper community representation and the necessary technical expertise: <!-- If the TAG has any additional items, such as leading a minimum number of projects, or facilitating a number meetings, they should be added to this list under "Body of work" -->
+
+* Gender diversity
+* Company diversity
+* Geo diversity
+* Number of nominations from different companies, people, regions for a single individual
+* Existing body of work
+* Justification provided during nomination
+
+In case there are no individuals expressing interest in taking up leadership positions, an evaluation process for the TAG / working group or project archival may be initiated, as [outlined by the TOC](https://github.com/cncf/toc/blob/main/tags/cncf-tags.md#retirement).
+
+### Community timeline
+
+Community nominations will run for at least 1 month, with a maximum up to 2 months.
+
+* For TAG Chair nominations, the TOC will take a vote as [described by the TOC](https://github.com/cncf/toc/blob/main/tags/cncf-tags.md#elections).
+* For TAG TL, TAG Chairs will vote and propose the nomination to the TOC. The TOC takes the final vote.
+* For Working Group and Project Chairs, the TAG Chairs and Leads will take a vote.
+
+Upon close of nominations, a decision should be made within the next month.
+
+### Submitting a nomination
+
+Nominations are to be submitted to [TAG Co-Chair's email alias](mailto:cncf-tag-chairs@lists.cncf.io) with the details: <!-- ! UPDATE EMAIL with the TAG's Leadership's correct mailing list ! -->
+
+* Subject "NOMINATION $(TAG Chair, TAG TL, WG XYZ Chair): $NAME-OF-NOMINEE"
+* CC the nominee
+* Justification
+* Nominee Biography
+
+## Nomination requirements
+
+The `<TAG NAME>` recognizes and values the achievements of individuals who have proven themselves in this community.
+If a given nominee does not meet all the requirements, the TAG leadership will still review the nomination and justification to determine if enough intent and commitment is present to move forward with an endorsement.
+
+**Nominees must**:
+
+* Be the author of at least one pull request against the `<TAG NAME>` repository
+* Be active in the community within the last 3 months before their nomination
+  * Active - Attending at least 1 `<TAG NAME>` Regular Meeting a month
+  * Engaging in community chat via Slack or lists
+  * Commenting on PRs and issues to drive suggestions to proposals, define scope, resolve clarity issues, etc.
+* Agree to the nomination
+
+*additional requirements may be defined in the specific [roles](template-roles.md) governance document* <!-- ! UPDATE THE LINK ! -->
+
+**Nominations must**:
+
+* Come from someone other than the nominee
+* Have justification from the nominator regarding the nominee's capabilities
+
+### Justification for nominees
+
+To ensure nominations are thoughtful and supported, in addition to the above requirements, a justification must enumerate on the nominee's:
+
+* TAG Community involvement
+* Leadership and collaboration skills
+* Willingness to learn and expand existing technical knowledge
+
+## Announcing nomination results
+
+The TAG leadership will release aggregate information about the nominees at the end of the nomination process. Aggregate information will not include who nominated someone.
+
+## Next Steps
+
+If the role under nomination requires TOC approval or vote, the TAG Co-chairs are responsible for coordinating and executing that in accordance with the TOC's processes (defined previously).