Add governance page (#641)

Co-authored-by: Joel Denning <[email protected]>

docusaurus.config.js

@@ -73,6 +73,10 @@ module.exports = {
         {
           title: "Community",
           items: [
+            {
+              label: "Governance",
+              to: "governance/",
+            },
             {
               label: "Code of Conduct",
               to: "code-of-conduct/"

src/pages/governance/index.md

@@ -0,0 +1,51 @@
+# Single-spa governance
+
+## Overview and scope
+
+The single-spa project consists of various software projects, documentation resources, and community resources that are freely available for corporations, governments, and nonprofits to use when creating websites. It was started in 2015 by Joel Denning.
+
+Single-spa is not owned by any individual, corporation, or legal entity, but rather is communally owned by its creator, maintainers, and users. Its users span across the globe and various jurisdictions. Due to its open source license, single-spa provides no guarantees to its users. It is the intention and hope of single-spa’s creator, maintainers, and users that no political or legal tension or intervention will prevent the single-spa community from continuing to use and improve the software.
+
+This single-spa governance document outlines how the single-spa software project and its community operate, including which people and groups have official influence over it.
+
+## Maintainer positions
+
+The following designations or positions are granted to individuals within the single-spa community:
+
+### Creator
+The creator of single-spa (Joel Denning) reserves final say over the project, having created it and maintained and guided the project for many years.
+
+### Core team member
+
+The single-spa core team is a group of technical leaders with influence over all single-spa software projects and subprojects.
+
+The core team may grow or shrink to any size. Core team members are added or removed by the single-spa creator.
+
+The current core team is shown at https://single-spa.js.org/contributors/
+
+### Maintainer
+
+A single-spa maintainer is a technical position for community members who have limited influence over a subset of the single-spa project.
+
+The current maintainers are shown on Github repository pages and at https://single-spa.js.org/contributors/
+
+### Community manager
+
+Single-spa community managers are people who help organize the community, moderate its discussions, provide visibility into the project, and assist in resolving disputes between members.
+
+The current community managers are shown at https://single-spa.js.org/contributors/
+
+## Community governance
+
+All single-spa community members are subject to the single-spa code of conduct. Any disputes between members of the community can be surfaced to single-spa’s creator and community managers, for resolution.
+
+Single-spa discussions are held in the single-spa Slack workspace and on Github.
+
+## Technical governance
+The single-spa core team, maintainers, and creator may periodically hold meetings to discuss the current status and roadmap of single-spa. The creator has final say over all technical decisions. The core team helps out in day-to-day maintenance of the project, new feature initiatives, and roadmap.
+
+For transparency to the broader community, meeting notes are published on the single-spa blog.
+
+## Funding
+
+The single-spa project accepts voluntary donations via single-spa’s Open Collective. Single-spa’s creator accepts donations via Github sponsors. Budgeting and dispensing of single-spa Open Collective funds is controlled by single-spa’s creator, including paying the creator, core team, and maintainers for their labor.