[WIP] What: Add tech leadership principles guidance

Why:
 * CoCC is receiving reports of violations they are not chartered to manage

This change address the need by:
 * creates the guidance file with enforcement/escalation information

 What is missing:
 * We need the email alias set up for escalation, CC @mrbobbytables

Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>

PRINCIPLES.md

@@ -177,6 +177,10 @@ Project needs may include test automation and CI, cloud resources to test on, cl
 
 The Technical Oversight Committee has adopted these leadership principles to help guide the ecosystem in growth and maturity. These principles define the expectations of TOC members, project maintainers, TAG Chairs and Leads, chairs and leads of any group or committee, and other persons serving in any leadership role in the CNCF community.
 
+#### Guidance and Enforcement
+
+For additional guidance and information on how the Technical Leadership Principles are enforced and how projects can align with the principles, please refer to the [Technical Leadership Principles Guidance in the TOC's docs folder](docs/tech_leadership_principles_guidance.md).
+
 ### Principles
 
 Our goal with these is to foster a more inclusive and welcoming community for all, and we expect all leaders in the CNCF community  to participate in accordance with these principles. If a leader is not acting in accordance with these principles, community members should first address it with the other leaders of the project, TAG, committee, group, or body. Project and TAG governance documentation must explain procedures (including who is responsible) for response and resolution if these principles are not being followed. In general, if a leader is not following these principles, there should be a good faith effort to educate, inform, and provide the leader with an opportunity to improve before taking further action such as suspending or removing them from their leadership role. If the behavior that violates these principles persists, or if the other leaders of the applicable project, committee, or group do not take corrective action in response to a reported violation of these principles, projects should escalate the matter to the TOC.

docs/tech_leadership_principles_guidance.md

@@ -0,0 +1,66 @@
+# Technical Leadership Principles Enforcement Process
+
+This document serves as a guide for occasions where the Code of Conduct Committee or another entity informs the TOC of a technical leader who is allegedly infringing on or in violation of the technical leadership principles.
+
+## Background
+
+The technical leadership principles were developed during the creation of the CNCF Code of Conduct Committee to establish the standard of excellence among leaders in our Groups, Committees, and Projects. They were subsequently approved by the TOC for inclusion in the CNCF TOC Principles.
+
+The harm and erosion of trust that can occur as a lack of embodiment of these principles detrimentally degrades our projects, groups, and communities. 
+
+Where Code of Conduct violations impact one or more individuals directly, lack of adherence to the leadership principles impact the Project, the Group, and the community.
+
+## Expectations for projects and groups
+
+As with all things, Projects and our groups are Self-governing towards the governance outcomes defined and expected by the TOC.
+
+It is in this spirit of our operating principles that the TOC expects all projects, groups, and community bodies to self-enforce adherence to the Technical Leadership Principles. We further expect each project, group, and body to respectfully and reasonably address any behavior by an individual that is not in alignment with the Technical Leadership Principles prior to escalating to the TOC for resolution. Among the TOC, escalation is to the TOC Chair and Vice Chair. 
+
+## Escalating to the TOC
+
+In the event that the project or group cannot resolve this conflict with the resources available to them, the project should escalate to the TOC through the TOC Chair, Vice Chair, or CNCF Staff using the email alias below:
+
+$TLPTOCEMAIL _todo_
+
+Once escalated, two TOC members will be assigned to guide and mentor the project or group and its leadership on methods and options to arrive at an agreeable resolution. Resolutions are crafted to allow for the best outcome for the project or group and its future. The TOC may suggest changes among the leadership roles, responsibilities, and project governance to support that outcome.
+
+## Additional Information and Guidance
+
+### Conflict is likely
+
+Innovation is often born from the diversity of opinion, perspective, and experience of individuals collaborating towards a common goal or objective. Fostering an engaging and exploratory discussion, debate, and exchange of ideas to drive innovation requires a foundation of respect, grace, and curiosity so all voices may be elevated, heard, and incorporated into the discussion.
+
+Any personal, social views and political opinions exposed to the community can destroy and undermine trust of the leader holding them because those personal views may not align with CNCF values and may be seen to promote intolerance. Individuals have a right to their personal, private perspectives, but as leaders in our community we are expected to embody and practice the technical leadership principles and uphold our Code of Conduct through our behavior and engagements, serving as the arbiter of equity and fairness within projects, within the community, within CNCF spaces, and at CNCF events.
+
+### Building and breaking trust
+
+Leadership creates a power imbalance and in our community this imbalance is offset through an individuals’ ability to positively influence contributors to collaborate towards agreed outcomes. Our nomination and voting process for filling leadership roles in our groups, projects, or committees) is rooted in the merits of an individual’s work and the trust built as a result of their behaviors and community engagement. It is that trust that allows for positive influence to occur to offset any negative harm that could occur due to such an imbalance of power.
+
+When an individual's behavior fails to embody our principles and values and/or their personal/private views are exposed to the community, it has the potential to subversively abuse that imbalance and negatively harm the project and its community. A leader’s behavior and views has the singular ability to build or break our projects and our community.
+
+### Prevention
+
+All projects, groups, and committees are expected to establish a policy or governance process that allows for the removal of a leader for failure to continually align with our principles and values through a vote of no confidence after attempts to constructively correct (restorative justice) have occurred. It is unrealistic to detail every possible offense or behavior that could warrant such action and each project may have additional considerations to evaluate as part of determining the need for a vote of no confidence. 
+
+These prevention guidelines will be codified into a future revision of the moving levels criteria regarding appropriate project governance.
+
+## Resources
+
+We want to hear from you! These resources are available for the community to add to, especially if they found it useful. To add a resource, please file a PR. TOC members reviewing PRs for adding content must review the material in its entirety prior to approving.
+
+### Training
+
+#### No cost
+
+* Inclusive Strategies for open source https://training.linuxfoundation.org/training/inclusive-strategies-for-open-source-lfc103/ 
+* Inclusive Speaker orientation https://training.linuxfoundation.org/training/inclusive-speaker-orientation/ 
+  * While focused on Speaking, this training provides tips to help you check assumptions in your content and its delivery. 
+
+### Past talks
+
+* _please suggest talks on this topic here_
+
+### Community content
+
+* [Technical Mediation](https://github.com/TheFoxAtWork/Technical-Leadership/tree/main/technical-mediation), @TheFoxAtWork - how to resolve technical conflicts collaboratively. 
+* [Patience and Listening](https://github.com/TheFoxAtWork/Technical-Leadership/tree/main/patience-listening), @TheFoxAtWork - understanding how to be patient and actively listen during a conflict to be supportive while reaching resolution.