Add Governance Document for Infrastructure team

GOVERNANCE.md

@@ -0,0 +1,107 @@
+# CHAOSS Infrastructure Team Project Governance
+
+The CHAOSS Infrastructure Team is dedicated to managing shared CHAOSS Community infrastructure as the technical administrators of CHAOSS. The CHAOSS Infrastructure Team will operate as a working group within the CHAOSS Organization, which is a member of the Linux Foundation. This governance explains how the team is run.
+
+- [The CHAOSS Infrastructure Team Project Governance](#The CHAOSS Infrastructure Team-project-governance)
+  - [Values](#values)
+  - [Team Members](#Team Members)
+    - [Becoming a Team Member](#becoming-a-Team Member)
+    - [Removing a Team Member](#removing-a-Team Member)
+  - [Meetings](#meetings)
+  - [CHAOSS Resources](#chaoss-resources)
+  - [Code of Conduct Committee](#code-of-conduct-committee)
+  - [Security Response Team](#security-response-team)
+  - [Voting](#voting)
+  - [Transitional Period](#transitional-period)
+  - [Modifying this Charter](#modifying-this-charter)
+
+## Values
+
+The CHAOSS Infrastructure Team embraces the following values:
+
+* Openness: Communication and decision-making happens in the open and is discoverable for future
+  reference. As much as possible, all discussions and work take place in public
+  forums and open repositories.
+
+* Fairness: All stakeholders have the opportunity to provide feedback and submit
+  contributions, which will be considered on their merits.
+
+* Inclusivity: We innovate through different perspectives and skill sets, which
+  can only be accomplished in a welcoming and respectful environment.
+
+* Participation: Responsibilities within the project are earned through
+  participation, and there is a clear path up the contributor ladder into leadership
+  positions.
+
+## Team Members
+
+The current team members can be found in [MEMBERS.md](./MEMBERS.md). Team members collectively steward the CHAOSS Community infrastructure and forms the governing body for shared CHAOSS commmunity infrastructure. 
+
+The CHAOSS Infrastructure Team members have merge approval rights to the [team GitHub repository](https://github.com/chaoss/infrastructure) and any other repositories later created by or assigned to The CHAOSS Infrastructure Team.
+
+### Becoming a Team Member
+
+Team members are appointed by the CHAOSS Governing Board. There is no other way to become a CHAOSS Infrastructure Team Member
+
+### Removing a Team Member
+
+Team Members may resign at any time if they feel that they will not be able to
+continue fulfilling their project duties.
+
+Team Members may also be removed after being inactive, failure to fulfill their 
+Team Member responsibilities, violating the CHAOSS Code of Conduct, or other reasons.
+Inactivity is defined as a period of very low or no activity in the project 
+for a year or more, with no definite schedule to return to full Team Member 
+activity.
+
+A Team Member may be removed at any time by the CHAOSS Governing Board.
+
+
+<!-- ## Meetings
+
+Time zones permitting, Team Members are expected to participate in the public
+developer meeting, which occurs every two weeks according to the CHAOSS calendar.  
+
+Team Members will also have closed meetings in order to discuss security reports
+or reports from the CHAOSS Code of Conduct Committee.  Such meetings should be scheduled by any Team Member on receipt of a security issue or CoCC message.  All current Team Members must be invited to such closed meetings, except for any Team Member who is accused of a CoC violation.
+
+## CHAOSS Resources
+
+Any Team Member may suggest a request for CHAOSS resources, either in an issue, or during a meeting.  A simple majority of Team Members approves the request.  The Team Members may also choose to delegate working with CHAOSS to non-Team Member community members, who will then be added to the [Team MemberS.md file](./Team MemberS.md) with that special status. -->
+
+## Code of Conduct Committee
+
+The The CHAOSS Infrastructure Team project adheres to the [CHAOSS Code of Conduct](https://chaoss.community/code-of-conduct/)(CoC).  As such, community members needing to report a violation of the CoC should report it directly to the CHAOSS Code Of Conduct Committee (CoCC).
+
+The Team Members will work with the CoCC on any reports which require action by the team. 
+
+## Security Response Team
+
+The Team Members will appoint a Security Response Team to handle security reports.
+This committee may simply consist of the Team Members themselves.  If this
+responsibility is delegated, the Team Members will appoint a team of at least two 
+contributors to handle it.  The Team Members will review who is assigned to this
+at least once a year.
+
+<!-- The Security Response Team is responsible for handling all reports of security
+holes and breaches according to the [security policy](./SECURITY.md). -->
+
+## Voting
+
+While most business in The CHAOSS Infrastructure Team is conducted by "[lazy consensus](https://community.apache.org/committers/lazyConsensus.html)", 
+periodically the Team Members may need to vote on specific actions or changes.
+A vote can be taken on the project's public Slack channel (#community-infrastructure in the [CHAOSS Slack](https://chaoss.community/kb-getting-started/)) or 
+the private Team Member Slack channel for security or conduct matters.  
+Votes may also be taken at the biweekly developer meeting.  Any Team Member may
+demand a vote be taken on any issue.
+
+Most votes require a simple majority of all Team Members to succeed, except where
+otherwise noted.  Two-thirds majority votes mean at least two-thirds of all 
+current Team Members.
+
+## Modifying this Charter
+
+Changes to this Governance and its supporting documents may be approved by 
+a 2/3 vote of the Team Members.
+
+This governance document was created based on the template available at https://github.com/cncf/project-template/blob/main/GOVERNANCE-maintainer.md and the adaptations to it from the [CollectOSS project governance](https://github.com/chaoss/CollectOSS/blob/main/GOVERNANCE.md).