Remove comments not intended for final document

Author: Relequestual

CHARTER.md

@@ -4,21 +4,15 @@
 <!-- While this document is being written, you can find the discussion to help determine what should be found here at https://github.com/json-schema-org/community/discussions/286 - This comment should be removed before merging -->
 
 ## Section 0: Guiding Principles
-<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391241 -->
-
 The JSON Schema project is part of the OpenJS Foundation which operates transparently, openly, collaboratively, and ethically. We strive to be open and transparent as much as is possible, and wish to enable anyone to interact and engage with any area of our work.
 
 Having no structure in place usually leads to one that is informal and undocumented, making it difficult to meet our own expectations of how we wish to operate. As such, we define the following charter which includes aspects of the governance model to which we subscribe and by which we operate.
 
 ## Section 1: Scope
-<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391250 -->
-
 JSON Schema aims to enable the confident and reliable use of the JSON data format. It does this primarily by providing specification documents which define a declarative language that allows annotation and validation of JSON documents.
 While JSON Schema's primary target is constraint-based data validation, it continues to be used across the whole stack, in different stages of a given project, and for purposes beyond its original design. We aim to enable these additional and emergent use cases.
 
 ### 1.1: In-scope (optional)
-<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391253 -->
-
 The scope of the JSON Schema project is split into two sections: primary and secondary concerns.
 Primary concerns are areas we wish to give focus to, while secondary concerns are more likely to require the creation of a Special Interest Group.
 
@@ -51,23 +45,15 @@ Secondary Concerns
 - Vocabularies registry
 
 ### 1.2: Out-of-Scope (optional)
-<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391262 -->
-
 Section Intentionally Left Blank
 
 ## Section 2: Relationship with OpenJS Foundation CPC.
-<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391266 -->
-
 Most large, complex open source communities have both a business and a technical governance model. Technical leadership for the projects within the OpenJS Foundation is delegated to the projects through their project charters by the OpenJS Cross Project Council (CPC). In the case of the JSON Schema project, it is delegated to the JSON Schema Technical Steering Committee ("TSC").
 
 ### 2.1 Other Formal Project Relationships (optional)
-<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391271 -->
-
 Section Intentionally Left Blank
 
 ## Section 3: JSON Schema Org Governing Body (TSC)
-<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391284 -->
-
 The TSC is initially established from the observed major contributors who are currently active and in good standing.
 
 There is no maximum TSC membership size. The TSC must have a minimum of four members.
@@ -91,8 +77,6 @@ A TSC member may be removed by vote from the TSC if, during a 3-month period, al
 - They do not provide any form of excuse or no excuse is known for their absence
 
 ## Section 4: Roles & Responsibilities
-<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391286 -->
-
 The JSON Schema project is jointly governed by a Technical Steering Committee (TSC) which is responsible for high-level guidance of the project.
 
 The TSC has final authority over this project including:
@@ -108,14 +92,9 @@ The TSC has final authority over this project including:
 In joining the TSC, members commit to communicate on a regular basis and respond to issues raised by the TSC in a timely manner. If they are no longer able or willing to make such a commitment, they should discuss this with the TSC or a TSC Chair.
 
 ### Section 4.1 Project Operations & Management (optional)
-<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391290 -->
-
 The TSC and entire technical community will follow any processes as may be specified by the OpenJS Foundation Board relating to the intake and license compliance review of contributions, including the OpenJS Foundation IP Policy.
 
 ### Section 4.2: Decision-making and Voting
-<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391296 -->
-Note: See comments found in raw view...
-
 The TSC follows a formal consensus seeking decision making model.
 In some situations, a vote may be preferable, however a vote will not be used to make the vast majority of decisions.
 In the unlikely case where it seems that consensus cannot be reached after multiple attempts, the decision process may be moved to resolve via a vote. This is not expected to happen, but defined as a backup.
@@ -244,8 +223,6 @@ The following responsibilities are recognised as those requiring roles to be def
 - Financial allocation approval, tracking, and auditing
 
 ## Section 5: Definitions (optional)
-<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391301 -->
-
 The JSON Schema project: The project which is housed by the OpenJS Foundation which operates as The JSON Schema Org.
 
 The JSON Schema Org: The people, policies, processes, activities, and artifacts, found within the GitHub json-schema-org.