diff --git a/README.md b/README.md index 5292b27..c1936a5 100644 --- a/README.md +++ b/README.md @@ -2,32 +2,64 @@ ## 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: opensource@github.com. 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: opensource@github.com. To avoid +confusion with MVG artifacts, we did not place the CoC in the repo. ### Submitting a pull request @@ -35,4 +67,5 @@ Please note that this project is released with a [Contributor Code of Conduct](h 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. diff --git a/org-docs/ANTITRUST.md b/org-docs/ANTITRUST.md index 6d734c5..9acfcd6 100644 --- a/org-docs/ANTITRUST.md +++ b/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/). diff --git a/org-docs/CHARTER.md b/org-docs/CHARTER.md index dfbf0f9..5d5995b 100644 --- a/org-docs/CHARTER.md +++ b/org-docs/CHARTER.md @@ -1,6 +1,9 @@ # 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 @@ -8,37 +11,66 @@ This is the organizational charter for the [FIXME] Organization (the "Organizati ## 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 @@ -46,16 +78,27 @@ 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/). diff --git a/org-docs/STEERING-COMMITTEE.md b/org-docs/STEERING-COMMITTEE.md index fb660f6..b322e01 100644 --- a/org-docs/STEERING-COMMITTEE.md +++ b/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/). diff --git a/org-docs/TRADEMARKS.md b/org-docs/TRADEMARKS.md index d58e223..a91c992 100644 --- a/org-docs/TRADEMARKS.md +++ b/org-docs/TRADEMARKS.md @@ -1,39 +1,84 @@ ## Introduction -This is the Organization's policy for the use of our trademarks. While our work is available under free and open source software licenses, those licenses do not include a license to use our trademarks. +This is the Organization's policy for the use of our trademarks. While our work +is available under free and open source software licenses, those licenses do not +include a license to use our trademarks. -This policy describes how you may use our trademarks. Our goal is to strike a balance between: 1) our need to ensure that our trademarks remain reliable indicators of the quality software we release; and 2) our community members' desire to be full participants in our Organization. +This policy describes how you may use our trademarks. Our goal is to strike a +balance between: 1) our need to ensure that our trademarks remain reliable +indicators of the quality software we release; and 2) our community members' +desire to be full participants in our Organization. ## Our Trademarks -This policy covers the name of the Organization and each of the Organization's projects, as well as any associated names, trademarks, service marks, logos, mascots, or similar indicators of source or origin (our "Marks"). +This policy covers the name of the Organization and each of the Organization's +projects, as well as any associated names, trademarks, service marks, logos, +mascots, or similar indicators of source or origin (our "Marks"). ## In General -Whenever you use our Marks, you must always do so in a way that does not mislead anyone about exactly who is the source of the software. For example, you cannot say you are distributing the "Mark" software when you're distributing a modified version of it because people will believe they are getting the same software that they can get directly from us when they aren't. You also cannot use our Marks on your website in a way that suggests that your website is an official Organization website or that we endorse your website. But, if true, you can say you like the "Mark" software, that you participate in the "Mark" community, that you are providing an unmodified version of the "Mark" software, or that you wrote a book describing how to use the "Mark" software. - -This fundamental requirement, that it is always clear to people what they are getting and from whom, is reflected throughout this policy. It should also serve as your guide if you are not sure about how you are using the Marks. +Whenever you use our Marks, you must always do so in a way that does not mislead +anyone about exactly who is the source of the software. For example, you cannot +say you are distributing the "Mark" software when you're distributing a modified +version of it because people will believe they are getting the same software +that they can get directly from us when they aren't. You also cannot use our +Marks on your website in a way that suggests that your website is an official +Organization website or that we endorse your website. But, if true, you can say +you like the "Mark" software, that you participate in the "Mark" community, that +you are providing an unmodified version of the "Mark" software, or that you +wrote a book describing how to use the "Mark" software. + +This fundamental requirement, that it is always clear to people what they are +getting and from whom, is reflected throughout this policy. It should also serve +as your guide if you are not sure about how you are using the Marks. In addition: -* You may not use or register, in whole or in part, the Marks as part of your own trademark, service mark, domain name, company name, trade name, product name or service name. -* Trademark law does not allow your use of names or trademarks that are too similar to ours. You therefore may not use an obvious variation of any of our Marks or any phonetic equivalent, foreign language equivalent, takeoff, or abbreviation for a similar or compatible product or service. -* You agree that any goodwill generated by your use of the Marks and participation in our community inures solely to our collective benefit. +* You may not use or register, in whole or in part, the Marks as part of your + own trademark, service mark, domain name, company name, trade name, product + name or service name. +* Trademark law does not allow your use of names or trademarks that are too + similar to ours. You therefore may not use an obvious variation of any of our + Marks or any phonetic equivalent, foreign language equivalent, takeoff, or + abbreviation for a similar or compatible product or service. +* You agree that any goodwill generated by your use of the Marks and + participation in our community inures solely to our collective benefit. ## Distribution of unmodified source code or unmodified executable code we have compiled -When you redistribute an unmodified copy of our software, you are not changing the quality or nature of it. Therefore, you may retain the Marks we have placed on the software to identify your redistribution. This kind of use only applies if you are redistributing an official distribution from this Project that has not been changed in any way. +When you redistribute an unmodified copy of our software, you are not changing +the quality or nature of it. Therefore, you may retain the Marks we have placed +on the software to identify your redistribution. This kind of use only applies +if you are redistributing an official distribution from this Project that has +not been changed in any way. ## Distribution of executable code that you have compiled, or modified code -You may use any word marks, but not any Organization logos, to truthfully describe the origin of the software that you are providing, that is, that the code you are distributing is a modification of our software. You may say, for example, that "this software is derived from the source code for 'Mark' software." +You may use any word marks, but not any Organization logos, to truthfully +describe the origin of the software that you are providing, that is, that the +code you are distributing is a modification of our software. You may say, for +example, that "this software is derived from the source code for 'Mark' +software." -Of course, you can place your own trademarks or logos on versions of the software to which you have made substantive modifications, because by modifying the software, you have become the origin of that exact version. In that case, you should not use our Marks. +Of course, you can place your own trademarks or logos on versions of the +software to which you have made substantive modifications, because by modifying +the software, you have become the origin of that exact version. In that case, +you should not use our Marks. -However, you may use our Marks for the distribution of code (source or executable) on the condition that any executable is built from the official Project source code and that any modifications are limited to switching on or off features already included in the software, translations into other languages, and incorporating minor bug-fix patches. Use of our Marks on any further modification is not permitted. +However, you may use our Marks for the distribution of code (source or +executable) on the condition that any executable is built from the official +Project source code and that any modifications are limited to switching on or +off features already included in the software, translations into other +languages, and incorporating minor bug-fix patches. Use of our Marks on any +further modification is not permitted. ## Statements about your software's relation to our software -You may use the word Marks, but not the Organization's logos, to truthfully describe the relationship between your software and ours. Our Mark should be used after a verb or preposition that describes the relationship between your software and ours. So you may say, for example, "Bob's software for the 'Mark' platform" but may not say "Bob's 'Mark' software." Some other examples that may work for you are: +You may use the word Marks, but not the Organization's logos, to truthfully +describe the relationship between your software and ours. Our Mark should be +used after a verb or preposition that describes the relationship between your +software and ours. So you may say, for example, "Bob's software for the 'Mark' +platform" but may not say "Bob's 'Mark' software." Some other examples that may +work for you are: * [Your software] uses "Mark" software * [Your software] is powered by "Mark" software @@ -41,4 +86,7 @@ You may use the word Marks, but not the Organization's logos, to truthfully desc * [Your software] for use with "Mark" software * [Your software] for Mark software -These guidelines are based on the [Model Trademark Guidelines](http://www.modeltrademarkguidelines.org), used under a [Creative Commons Attribution 3.0 Unported license](https://creativecommons.org/licenses/by/3.0/deed.en_US) +These guidelines are based on the +[Model Trademark Guidelines](http://www.modeltrademarkguidelines.org), +used under a +[Creative Commons Attribution 3.0 Unported license](https://creativecommons.org/licenses/by/3.0/deed.en_US) diff --git a/project-docs/CONTRIBUTING.md b/project-docs/CONTRIBUTING.md index 73edf94..6a3665f 100644 --- a/project-docs/CONTRIBUTING.md +++ b/project-docs/CONTRIBUTING.md @@ -1,11 +1,20 @@ # Contributing -This Project welcomes contributions, suggestions, and feedback. All contributions, suggestions, and feedback you submitted are accepted under the [Project's license](./LICENSE.md). You represent that if you do not own copyright in the code that you have the authority to submit it under the [Project's license](./LICENSE.md). All feedback, suggestions, or contributions are not confidential. +This Project welcomes contributions, suggestions, and feedback. All +contributions, suggestions, and feedback you submitted are accepted under the +[Project's license](./LICENSE.md). You represent that if you do not own +copyright in the code that you have the authority to submit it under the +[Project's license](./LICENSE.md). All feedback, suggestions, or contributions +are not confidential. -[Should be further filled in by the project - including defining the requirements to reach maintainer status] +[Should be further filled in by the project - including defining the +requirements to reach maintainer status] -The Project abides by the Organization's [code of conduct](../org-docs/CODE-OF-CONDUCT.md) and [trademark policy](../org-docs/TRADEMARKS.md). +The Project abides by the Organization's +[code of conduct](../org-docs/CODE-OF-CONDUCT.md) and +[trademark policy](../org-docs/TRADEMARKS.md). --- 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/). diff --git a/project-docs/GOVERNANCE.md b/project-docs/GOVERNANCE.md index 1ed37f6..c3de09d 100644 --- a/project-docs/GOVERNANCE.md +++ b/project-docs/GOVERNANCE.md @@ -1,45 +1,81 @@ # Governance Policy -This document provides the governance policy for the Project. Maintainers agree to this policy and to abide by all Project polices, including the [code of conduct](../org-docs/CODE-OF-CONDUCT.md), [trademark policy](../org-docs/TRADEMARKS.md), and [antitrust policy](../org-docs/ANTITRUST.md) by adding their name to the [maintainers.md file](./MAINTAINERS.md). +This document provides the governance policy for the Project. Maintainers agree +to this policy and to abide by all Project polices, including the +[code of conduct](../org-docs/CODE-OF-CONDUCT.md), +[trademark policy](../org-docs/TRADEMARKS.md), and +[antitrust policy](../org-docs/ANTITRUST.md) by adding their name to the +[maintainers.md file](./MAINTAINERS.md). ## 1. Roles. -This project may include the following roles. Additional roles may be adopted and documented by the Project. +This project may include the following roles. Additional roles may be adopted +and documented by the Project. -**1.1. Maintainers**. Maintainers are responsible for organizing activities around developing, maintaining, and updating the Project. Maintainers are also responsible for determining consensus. This Project may add or remove Maintainers with the approval of the current Maintainers. +**1.1. Maintainers**. Maintainers are responsible for organizing activities +around developing, maintaining, and updating the Project. Maintainers are also +responsible for determining consensus. This Project may add or remove +Maintainers with the approval of the current Maintainers. -**1.2. Contributors**. Contributors are those that have made contributions to the Project. +**1.2. Contributors**. Contributors are those that have made contributions to +the Project. ## 2. Decisions. -**2.1. Consensus-Based Decision Making**. Projects make decisions through consensus of the Maintainers. While explicit agreement of all Maintainers is preferred, it is not required for consensus. Rather, the Maintainers will determine consensus based on their good faith consideration of a number of factors, including the dominant view of the Contributors and nature of support and objections. The Maintainers will document evidence of consensus in accordance with these requirements. +**2.1. Consensus-Based Decision Making**. Projects make decisions through +consensus of the Maintainers. While explicit agreement of all Maintainers is +preferred, it is not required for consensus. Rather, the Maintainers will +determine consensus based on their good faith consideration of a number of +factors, including the dominant view of the Contributors and nature of support +and objections. The Maintainers will document evidence of consensus in +accordance with these requirements. -**2.2. Appeal Process**. Decisions may be appealed by opening an issue and that appeal will be considered by the Maintainers in good faith, who will respond in writing within a reasonable time. If the Maintainers deny the appeal, the appeal may be brought before the Organization Steering Committee, who will also respond in writing in a reasonable time. +**2.2. Appeal Process**. Decisions may be appealed by opening an issue and that +appeal will be considered by the Maintainers in good faith, who will respond in +writing within a reasonable time. If the Maintainers deny the appeal, the appeal +may be brought before the Organization Steering Committee, who will also respond +in writing in a reasonable time. ## 3. How We Work. -**3.1. Openness**. Participation is open to anyone who is directly and materially affected by the activity in question. There shall be no undue financial barriers to participation. +**3.1. Openness**. Participation is open to anyone who is directly and +materially affected by the activity in question. There shall be no undue +financial barriers to participation. -**3.2. Balance**. The development process should balance the interests of Contributors and other stakeholders. Contributors from diverse interest categories shall be sought with the objective of achieving balance. +**3.2. Balance**. The development process should balance the interests of +Contributors and other stakeholders. Contributors from diverse interest +categories shall be sought with the objective of achieving balance. -**3.3. Coordination and Harmonization**. Good faith efforts shall be made to resolve potential conflicts or incompatibility between releases in this Project. +**3.3. Coordination and Harmonization**. Good faith efforts shall be made to +resolve potential conflicts or incompatibility between releases in this Project. -**3.4. Consideration of Views and Objections**. Prompt consideration shall be given to the written views and objections of all Contributors. +**3.4. Consideration of Views and Objections**. Prompt consideration shall be +given to the written views and objections of all Contributors. -**3.5. Written procedures**. This governance document and other materials documenting this project's development process shall be available to any interested person. +**3.5. Written procedures**. This governance document and other materials +documenting this project's development process shall be available to any +interested person. ## 4. No Confidentiality. -Information disclosed in connection with any Project activity, 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 Project activity, including but not +limited to meetings, contributions, and submissions, is not confidential, +regardless of any markings or statements to the contrary. ## 5. Trademarks. -Any names, trademarks, logos, or goodwill developed by and associated with the Project (the "Marks") are controlled by the Organization. Maintainers may only use these Marks in accordance with the Organization's trademark policy. If a Maintainer resigns or is removed, any rights the Maintainer may have in the Marks revert to the Organization. +Any names, trademarks, logos, or goodwill developed by and associated with the +Project (the "Marks") are controlled by the Organization. Maintainers may only +use these Marks in accordance with the Organization's trademark policy. If a +Maintainer resigns or is removed, any rights the Maintainer may have in the +Marks revert to the Organization. ## 6. Amendments. -Amendments to this governance policy may be made by affirmative vote of 2/3 of all Maintainers, with approval by the Organization's Steering Committee. +Amendments to this governance policy may be made by affirmative vote of 2/3 of +all Maintainers, with approval by the Organization's 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/). diff --git a/project-docs/MAINTAINERS.md b/project-docs/MAINTAINERS.md index 06bf7cd..60732b2 100644 --- a/project-docs/MAINTAINERS.md +++ b/project-docs/MAINTAINERS.md @@ -1,6 +1,15 @@ # Maintainers -This document lists the Maintainers of the Project. Maintainers may be added once approved by the existing maintainers as described in the [Governance document](./GOVERNANCE.md). By adding your name to this list you are agreeing to abide by the Project governance documents and to abide by all of the Organization's polices, including the [code of conduct](../org-docs/CODE-OF-CONDUCT.md), [trademark policy](../org-docs/TRADEMARKS.md), and [antitrust policy](../org-docs/ANTITRUST.md). If you are participating because of your affiliation with another organization (designated below), you represent that you have the authority to bind that organization to these policies. +This document lists the Maintainers of the Project. Maintainers may be added +once approved by the existing maintainers as described in the [Governance +document](./GOVERNANCE.md). By adding your name to this list you are agreeing to +abide by the Project governance documents and to abide by all of the +Organization's polices, including the +[code of conduct](../org-docs/CODE-OF-CONDUCT.md), +[trademark policy](../org-docs/TRADEMARKS.md), and +[antitrust policy](../org-docs/ANTITRUST.md). If you are participating because of your +affiliation with another organization (designated below), you represent that you +have the authority to bind that organization to these policies. | **NAME** | **Organization** | | --- | --- | @@ -9,4 +18,5 @@ This document lists the Maintainers of the Project. Maintainers may be added onc --- 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/).