Wrap at column 80, mostly.

README.md

@@ -2,37 +2,70 @@
 
 ## What is Minimum Viable Governance?
 
-Minimum Viable Governance (MVG) - currently in beta - is a repository-based approach for putting lightweight governance into free and open source projects that are run in version control systems. It provides an overall two-tier organizational governance structure for a set of free and open source projects. At the top level (called an "organization" on GitHub), there is a technical steering committee to make decisions about the overall direction and coordination between all the organization's projects. Underneath that top level are the individual projects, with lightweight, consensus-based governance.
+Minimum Viable Governance (MVG) - currently in beta - is a repository-based
+approach for putting lightweight governance into free and open source projects
+that are run in version control systems. It provides an overall two-tier
+organizational governance structure for a set of free and open source projects.
+At the top level (called an "organization" on GitHub), there is a technical
+steering committee to make decisions about the overall direction and
+coordination between all the organization's projects. Underneath that top level
+are the individual projects, with lightweight, consensus-based governance.
 
-There are two folders. The first, org-docs, provides top-level organizational governance and policies for a technical steering committee (TSC). The second folder, project-docs, provides a template for individual project governance, subject to the policies and oversight of the larger organization.
+There are two folders. The first, org-docs, provides top-level organizational
+governance and policies for a technical steering committee (TSC). The second
+folder, project-docs, provides a template for individual project governance,
+subject to the policies and oversight of the larger organization.
 
-Minimum Viable Governance is meant as a way to quickly stand up collaborations that can grow with your organization and projects. If your organization grows to the point where a corporate home becomes necessary, typically when your organization begins holding money, MVG is designed to make that transition easy.
+Minimum Viable Governance is meant as a way to quickly stand up collaborations
+that can grow with your organization and projects. If your organization grows to
+the point where a corporate home becomes necessary, typically when your
+organization begins holding money, MVG is designed to make that transition easy.
 
 ## Why would we want to use this?
 
-Minimum Viable Governance allows you to start an organization and sub-projects with simple governance in place at the outset - including legal terms, licensing and trademark issues, and due process. Having this governance in place early helps avoid disputes among participants down the road.
+Minimum Viable Governance allows you to start an organization and sub-projects
+with simple governance in place at the outset - including legal terms, licensing
+and trademark issues, and due process. Having this governance in place early
+helps avoid disputes among participants down the road.
 
 ## How do we use this?
 
 1. Review the documents and determine if this is right for you.
-2. Describe the organization's mission in Section 1 of the [CHARTER.md](org-docs/CHARTER.md) file.
-3. Put the org-docs in a repository for the organization's governance and have each initial TSC member "sign" the [STEERING-COMMITTEE.md](org-docs/STEERING-COMMITTEE.md) file by adding their name and organizational affiliation (if applicable) to the file.
-4. For each project that will be under your organization's governance, create a repository under the organization and have each initial maintainer "sign" the [MAINTAINERS.md](project-docs/MAINTAINERS.md) file by adding their name and affiliation (if applicable) to the file.
-5. [Choose a license](https://choosealicense.com/) or fill out the copyright information in the MIT [LICENSE.md](project-docs/LICENSE.md) file for each project.
+2. Describe the organization's mission in Section 1 of the
+   [CHARTER.md](org-docs/CHARTER.md) file.
+3. Put the org-docs in a repository for the organization's governance and have
+   each initial TSC member "sign" the
+   [STEERING-COMMITTEE.md](org-docs/STEERING-COMMITTEE.md) file by adding their
+   name and organizational affiliation (if applicable) to the file.
+4. For each project that will be under your organization's governance, create a
+   repository under the organization and have each initial maintainer "sign" the
+   [MAINTAINERS.md](project-docs/MAINTAINERS.md) file by adding their name and
+   affiliation (if applicable) to the file.
+5. [Choose a license](https://choosealicense.com/) or fill out the copyright
+   information in the MIT [LICENSE.md](project-docs/LICENSE.md) file for each
+   project.
 6. Get to work.
 
 ## Contributing
 
-Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
+Hi there! We're thrilled that you'd like to contribute to this project. Your
+help is essential for keeping it great.
 
-Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](LICENSE).
+Contributions to this project are
+[released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license)
+to the public under the [project's open source license](LICENSE).
 
-Please note that this project is released with a [Contributor Code of Conduct](https://raw.githubusercontent.com/EthicalSource/contributor_covenant/release/content/version/2/0/code_of_conduct.md) (CoC). By participating in this project you agree to abide by its terms. Violations of the CoC should be reported to: [email protected]. To avoid confusion with MVG artifacts, we did not place the CoC in the repo.
+Please note that this project is released with a
+[Contributor Code of Conduct](https://raw.githubusercontent.com/EthicalSource/contributor_covenant/release/content/version/2/0/code_of_conduct.md)
+(CoC). By participating in this project you agree to abide by its terms.
+Violations of the CoC should be reported to: [email protected]. To avoid
+confusion with MVG artifacts, we did not place the CoC in the repo.
 
 ### Submitting a pull request
 
 1. [Fork](https://github.com/github/MVG/fork) and clone the repository
 2. Create a new branch: `git checkout -b my-branch-name`
 3. Make your change
 4. Push to your fork and [submit a pull request](https://github.com/github/MVG/compare)
-5. Pat yourself on the back and wait for your pull request to be reviewed and merged.
+5. Pat yourself on the back and wait for your pull request to be reviewed and
+   merged.

org-docs/ANTITRUST.md

@@ -1,7 +1,20 @@
 # Antitrust Policy
 
-Participants acknowledge that they may compete with other participants in various lines of business and that it is therefore imperative that they and their respective representatives act in a manner that does not violate any applicable antitrust laws, competition laws, or associated regulations. This Policy does not restrict any participant from engaging in other similar projects. Each participant may design, develop, manufacture, acquire or market competitive deliverables, products, and services, and conduct its business, in whatever way it chooses. No participant is obligated to announce or market any products or services. Without limiting the generality of the foregoing, participants agree not to have any discussion relating to any product pricing, methods or channels of product distribution, contracts with third-parties, division or allocation of markets, geographic territories, or customers, or any other topic that relates in any way to limiting or lessening fair competition.
+Participants acknowledge that they may compete with other participants in
+various lines of business and that it is therefore imperative that they and
+their respective representatives act in a manner that does not violate any
+applicable antitrust laws, competition laws, or associated regulations. This
+Policy does not restrict any participant from engaging in other similar
+projects. Each participant may design, develop, manufacture, acquire or market
+competitive deliverables, products, and services, and conduct its business, in
+whatever way it chooses. No participant is obligated to announce or market any
+products or services. Without limiting the generality of the foregoing,
+participants agree not to have any discussion relating to any product pricing,
+methods or channels of product distribution, contracts with third-parties,
+division or allocation of markets, geographic territories, or customers, or any
+other topic that relates in any way to limiting or lessening fair competition.
 
 ---
 Part of MVG-0.1-beta.
-Made with love by GitHub. Licensed under the [CC-BY 4.0 License](https://creativecommons.org/licenses/by-sa/4.0/).
+Made with love by GitHub.
+Licensed under the [CC-BY 4.0 License](https://creativecommons.org/licenses/by-sa/4.0/).

org-docs/CHARTER.md

@@ -1,61 +1,104 @@
 # Charter for the [FIXME] Organization
 
-This is the organizational charter for the [FIXME] Organization (the "Organization"). By adding their name to the [Steering Committee.md file](./STEERING-COMMITTEE.md), Steering Committee members agree as follows.
+This is the organizational charter for the [FIXME] Organization (the
+"Organization"). By adding their name to the
+[Steering Committee.md file](./STEERING-COMMITTEE.md), Steering Committee members
+agree as follows.
 
 ## 1. Mission
 
 [Set out mission of the Organization].
 
 ## 2. Steering Committee
 
-**2.1 Purpose**. The Steering Committee will be responsible for all technical oversight, project approval and oversight, policy oversight, and trademark management for the Organization.
+**2.1 Purpose**. The Steering Committee will be responsible for all technical
+oversight, project approval and oversight, policy oversight, and trademark
+management for the Organization.
 
-**2.2 Composition**. The Steering Committee voting members are listed in the steering-committee.md file in the repository.
-Voting members may be added or removed by no less than 3/4 affirmative vote of the Steering Committee.
-The Steering Committee will appoint a Chair responsible for organizing Steering Committee activity.
+**2.2 Composition**. The Steering Committee voting members are listed in the
+steering-committee.md file in the repository.  Voting members may be added or
+removed by no less than 3/4 affirmative vote of the Steering Committee.  The
+Steering Committee will appoint a Chair responsible for organizing Steering
+Committee activity.
 
 ## 3. Voting
 
-**3.1. Decision Making**. The Steering Committee will strive for all decisions to be made by consensus. While explicit agreement of the entire Steering Committee is preferred, it is not required for consensus. Rather, the Steering Committee will determine consensus based on their good faith consideration of a number of factors, including the dominant view of the Steering Committee and nature of support and objections. The Steering Committee will document evidence of consensus in accordance with these requirements. If consensus cannot be reached, the Steering Committee will make the decision by a vote.
-
-**3.2. Voting**. The Steering Committee Chair will call a vote with reasonable notice to the Steering Committee, setting out a discussion period and a separate voting period. Any discussion may be conducted in person or electronically by text, voice, or video. The discussion will be open to the public. In any vote, each voting representative will have one vote. Except as specifically noted elsewhere in this Charter, decisions by vote require a simple majority vote of all voting members.
+**3.1. Decision Making**. The Steering Committee will strive for all decisions
+to be made by consensus. While explicit agreement of the entire Steering
+Committee is preferred, it is not required for consensus. Rather, the Steering
+Committee will determine consensus based on their good faith consideration of a
+number of factors, including the dominant view of the Steering Committee and
+nature of support and objections. The Steering Committee will document evidence
+of consensus in accordance with these requirements. If consensus cannot be
+reached, the Steering Committee will make the decision by a vote.
+
+**3.2. Voting**. The Steering Committee Chair will call a vote with reasonable
+notice to the Steering Committee, setting out a discussion period and a separate
+voting period. Any discussion may be conducted in person or electronically by
+text, voice, or video. The discussion will be open to the public. In any vote,
+each voting representative will have one vote. Except as specifically noted
+elsewhere in this Charter, decisions by vote require a simple majority vote of
+all voting members.
 
 ## 4. Termination of Membership
 
-In addition to the method set out in section 2.2, the membership of a Steering Committee member will terminate if any of the following occur:
+In addition to the method set out in section 2.2, the membership of a Steering
+Committee member will terminate if any of the following occur:
 
 **4.1 Resignation**. Written notice of resignation to the Steering Committee.
 
-**4.2 Unreachable Member**. If a member is unresponsive at its listed handle for more than three months the Steering Committee may vote to remove the member.
+**4.2 Unreachable Member**. If a member is unresponsive at its listed handle for
+more than three months the Steering Committee may vote to remove the member.
 
 ## 5. Trademarks
 
-Any names, trademarks, service marks, logos, mascots, or similar indicators of source or origin and the goodwill associated with them arising out of the Organization's activities or Organization projects' activities (the "Marks"), are controlled by the Organization. Steering Committee members may only use the Marks in accordance with the Organization's [trademark policy](./TRADEMARKS.md). If a Steering Committee member is terminated or removed from the Steering Committee, any rights the Steering Committee member may have in the Marks revert to the Organization.
+Any names, trademarks, service marks, logos, mascots, or similar indicators of
+source or origin and the goodwill associated with them arising out of the
+Organization's activities or Organization projects' activities (the "Marks"),
+are controlled by the Organization. Steering Committee members may only use the
+Marks in accordance with the Organization's [trademark policy](./TRADEMARKS.md).
+If a Steering Committee member is terminated or removed from the Steering
+Committee, any rights the Steering Committee member may have in the Marks revert
+to the Organization.
 
 ## 6. Antitrust Policy
 
-The Steering Committee is bound by the Organization's [antitrust policy](./ANTITRUST.md).
+The Steering Committee is bound by the Organization's
+[antitrust policy](./ANTITRUST.md).
 
 ## 7. No Confidentiality
 
-Information disclosed in connection with any of the Organization's activities, including but not limited to meetings, Contributions, and submissions, is not confidential, regardless of any markings or statements to the contrary.
+Information disclosed in connection with any of the Organization's activities,
+including but not limited to meetings, Contributions, and submissions, is not
+confidential, regardless of any markings or statements to the contrary.
 
 ## 8. Project Criteria
 
 In order to be eligible to be a Organization project, a project must:
 
 * Be approved by the Steering Committee.
 * Agree to follow the guidance and direction of the Steering Committee.
-* Use only the following outbound licenses or agreements unless otherwise approved:
-  - For code, a license on the Open Source Initiative's list of [Popular Licenses](https://opensource.org/licenses).
-  - For data, a license on the Open Knowledge Foundation's list of [Recommended Conformant Licenses](http://opendefinition.org/licenses/).
-  - For specifications, a community developed and maintained specification agreement, such the [Open Web Foundation Agreements](https://www.openwebfoundation.org/the-agreements) or [Community Specification Agreement](https://github.com/CommunitySpecification/1.0).
-* Include and adhere to the Organization's policies, including the [trademark policy](./TRADEMARKS.md), the [antitrust policy](./ANTITRUST.md), and the [code of conduct](./CODE-OF-CONDUCT.md).
+* Use only the following outbound licenses or agreements unless otherwise
+  approved:
+  - For code, a license on the Open Source Initiative's list of
+    [Popular Licenses](https://opensource.org/licenses).
+  - For data, a license on the Open Knowledge Foundation's list of
+    [Recommended Conformant Licenses](http://opendefinition.org/licenses/).
+  - For specifications, a community developed and maintained specification
+    agreement, such the
+    [Open Web Foundation Agreements](https://www.openwebfoundation.org/the-agreements)
+    or [Community Specification Agreement](https://github.com/CommunitySpecification/1.0).
+* Include and adhere to the Organization's policies, including the
+  [trademark policy](./TRADEMARKS.md), the [antitrust policy](./ANTITRUST.md), and the [code of conduct](./CODE-OF-CONDUCT.md).
 
 ## 9. Amendments
 
-Amendments to this charter, the [antitrust policy](./ANTITRUST.md), the [trademark policy](./TRADEMARKS.md), or the [code of conduct](./CODE-OF-CONDUCT.md) may only be made with at least a 3/4 affirmative vote of the Steering Committee.
+Amendments to this charter, the [antitrust policy](./ANTITRUST.md), the
+[trademark policy](./TRADEMARKS.md), or the
+[code of conduct](./CODE-OF-CONDUCT.md) may only be made with at least a 3/4
+affirmative vote of the Steering Committee.
 
 ---
 Part of MVG-0.1-beta.
-Made with love by GitHub. Licensed under the [CC-BY 4.0 License](https://creativecommons.org/licenses/by-sa/4.0/).
+Made with love by GitHub.
+Licensed under the [CC-BY 4.0 License](https://creativecommons.org/licenses/by-sa/4.0/).

org-docs/STEERING-COMMITTEE.md

@@ -1,6 +1,14 @@
 # Steering Committee
 
-This document lists the members of the Organization's Steering Committee. Voting members may be added once approved by the Steering Committee as described in the [charter](./CHARTER.md). By adding your name to this list you are agreeing to abide by all Organization polices, including the [charter](./CHARTER.md), the [code of conduct](./CODE-OF-CONDUCT.md), the [trademark policy](./TRADEMARKS.md), and the [antitrust policy](./ANTITRUST.md). If you are serving on the Steering Committee because of your affiliation with another organization (designated below), you represent that you have authority to bind that organization to these policies.
+This document lists the members of the Organization's Steering Committee. Voting
+members may be added once approved by the Steering Committee as described in the
+[charter](./CHARTER.md). By adding your name to this list you are agreeing to
+abide by all Organization polices, including the [charter](./CHARTER.md), the
+[code of conduct](./CODE-OF-CONDUCT.md), the [trademark
+policy](./TRADEMARKS.md), and the [antitrust policy](./ANTITRUST.md). If you are
+serving on the Steering Committee because of your affiliation with another
+organization (designated below), you represent that you have authority to bind
+that organization to these policies.
 
 | **NAME** | **Handle** | **Affiliated Organization** |
 | --- | --- | --- |
@@ -9,4 +17,5 @@ This document lists the members of the Organization's Steering Committee. Voting
 
 ---
 Part of MVG-0.1-beta.
-Made with love by GitHub. Licensed under the [CC-BY 4.0 License](https://creativecommons.org/licenses/by-sa/4.0/).
+Made with love by GitHub.
+Licensed under the [CC-BY 4.0 License](https://creativecommons.org/licenses/by-sa/4.0/).