diff --git a/.cspell.yaml b/.cspell.yaml
index c00853515..9632e7d2c 100644
--- a/.cspell.yaml
+++ b/.cspell.yaml
@@ -18,6 +18,7 @@ ignoreRegExpList:
 words:
     - Collibra
     - DASD
+    - Docu
     - datadog
     - dynatrace
     - easycla
@@ -88,6 +89,12 @@ words:
     - frzifus
     - gbbr
     - gitter
+    - gitdm
+    - henrikrexed
+    - heptio
+    - hongalex
+    - horovits
+    - jackjia
     - jaglowski
     - jemmic
     - juraci
diff --git a/guides/README.md b/guides/README.md
new file mode 100644
index 000000000..13b18b381
--- /dev/null
+++ b/guides/README.md
@@ -0,0 +1,10 @@
+# OpenTelemetry Guidebooks
+
+This directory contains a collection of guides meant for contributors,
+maintainers, and community members. These guides are meant to help you get
+started, answer common questions, and provide best practices for being a part of
+the OpenTelemetry community. These should be considered a living resource, and
+everyone is welcome to contribute to them!
+
+- [Contributor Guide](./contributor/README.md)
+- [Maintainer Guide](./maintainer/README.md)
\ No newline at end of file
diff --git a/guides/contributor/CLA.md b/guides/contributor/CLA.md
new file mode 100644
index 000000000..599a6d8ad
--- /dev/null
+++ b/guides/contributor/CLA.md
@@ -0,0 +1,88 @@
+# The Contributor License Agreement
+
+The [Cloud Native Computing Foundation](https://www.cncf.io) (CNCF) defines
+the legal status of the contributed code in two different types of _Contributor License Agreements_
+(CLAs), [individual contributors](https://github.com/cncf/cla/blob/main/individual-cla.pdf) and [corporations](https://github.com/cncf/cla/blob/main/corporate-cla.pdf).
+
+OpenTelemetry can only accept original source code from CLA signatories.
+
+It is important to read and understand this legal agreement.
+
+## How do I sign?
+
+After creating your first Pull Request, the linux-foundation-easycla bot will respond with information regarding your CLA status along with a link to sign the CLA.
+
+<img width="1065" alt="EasyCLA bot" src="https://user-images.githubusercontent.com/69111235/152226443-f6fe61ee-0e92-46c5-b6ea-c0deb718a585.png">
+
+#### 1. If you are signing up as a corporate contributor, ensure that you have linked your corporate email address to your GitHub profile (it doesn't have to be your primary email address for GitHub) or else it can lead to issues with the CLA system.
+
+For more information, please see [Adding an email address to your GitHub account](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account).
+
+#### 2. Authorize EasyCLA to read some of your GitHub information
+
+<img width="554" alt="GitHub EasyCLA Authorization" src="https://user-images.githubusercontent.com/69111235/152228712-7d22f9d0-9f3c-4226-9ee0-bacba4b47725.png">
+
+- Click on the **Please click here to be authorized** link to navigate to the GitHub Authorize Linux Foundation: EasyCLA page.
+- Then click **Authorize LF-Engineering** to give the Linux Foundation read-only access to list the email addresses associated with your GitHub account.
+
+#### 3. Select from the two types of contributor
+
+<img width="1407" alt="EasyCLA" src="https://user-images.githubusercontent.com/69111235/152224818-1246453a-b086-4a57-9d14-c10d62ad438f.png">
+
+
+After authorizing EasyCLA, you will be redirected to a page to identify which type of contributor you are. 
+Select the most appropriate option:
+  * Individual Contributor: You are contributing as yourself, and not as part of another organization.
+  * Corporate Contributor: You are contributing on behalf of your employer or other organization.
+
+#### 4. Sign the CLA
+
+Once you select the type of contributor, proceed to Sign the CLA and follow the instructions to complete the signing process through DocuSign.
+
+After you have filled out  the information, Click "Finish" and you will be redirected back to your Pull Request.
+
+#### 5. Look for an email indicating successful signup.
+
+> Hello,
+> 
+> This is a notification email from EasyCLA regarding the project Cloud Native Computing > Foundation (CNCF).
+> 
+> The CLA has now been signed. You can download the signed CLA as a PDF here.
+> 
+> If you need help or have questions about EasyCLA, you can read the documentation or reach out to us for support.
+> 
+> Thanks,
+> EasyCLA Support Team
+
+
+
+#### 6. Validate your CLA
+
+Once you are redirected back to your GitHub Pull Request, reply with a comment `/easycla` to update the CLA status of your PR,
+if the bot hasn't picked up the change automatically yet.
+
+
+## Changing your Affiliation
+
+If you've changed employers and still contribute to OpenTelemetry, your affiliation
+needs to be updated. The Cloud Native Computing Foundation uses [gitdm](https://github.com/cncf/gitdm)
+to track who is contributing and from where. Create a pull request on the [gitdm](https://github.com/cncf/gitdm)
+repository with a change to the corresponding developer affiliation text file.
+Your entry should look similar to this:
+
+```
+Jorge O. Castro*: jorge!heptio.com, jorge!ubuntu.com, jorge.castro!gmail.com
+Heptio
+Canonical until 2017-03-31
+```
+
+In addition, be sure to update your affiliation on [OpenProfile](https://openprofile.dev).
+
+## Troubleshooting
+
+If you encounter any problems signing the CLA and need further assistance, log a ticket by clicking on the link 'please submit a support request ticket' from the EasyCLA bot's response. Someone from the CNCF will respond to your ticket to help.
+
+Should you have any issues using the LF Support Site, send a message to the
+backup email support address <login-issues@jira.linuxfoundation.org>
+
+[Linux Foundation Support Site]: https://support.linuxfoundation.org/
\ No newline at end of file
diff --git a/guides/contributor/README.md b/guides/contributor/README.md
new file mode 100644
index 000000000..78fbedd01
--- /dev/null
+++ b/guides/contributor/README.md
@@ -0,0 +1,67 @@
+# OpenTelemetry New Contributor Guide
+
+Welcome to OpenTelemetry! We're excited for you to join us. This guide will help
+you get started by providing an overview of the project, how we work together,
+and where to find helpful resources.
+
+## Table of Contents
+
+- [What is OpenTelemetry?](#what-is-opentelemetry)
+- [Prerequisites](#prerequisites)
+
+## What is OpenTelemetry?
+
+OpenTelemetry is a framework for application telemetry data. If you've ever
+checked how much memory a process is using on your computer, or looked at the
+size of a file, you've already interacted with telemetry! Cloud native systems
+create, emit, and process many millions of telemetry points every second as they
+run. In addition, the developers of cloud native software need to describe what
+their applications are doing in production in order to find bugs, optimize their
+system performance, and understand their applications. OpenTelemetry provides a
+single standard for creating and collecting this telemetry, transforming it as
+needed, and exporting it to dozens of analysis tools.
+
+## Prerequisites
+
+Before you submit code to OpenTelemetry, you'll need to have a few things set
+up:
+
+### Create a GitHub account
+
+Before getting started, you'll need to [sign up](http://github.com/signup) for a
+GitHub account.
+
+### Sign the CLA
+
+Before we can accept your code, you'll need to sign the [Contributor License
+Agreement](./CLA.md). This is a one-time process.
+
+### Code of Conduct
+
+Please make sure to read and follow our [Code of Conduct](../../code-of-conduct.md).
+
+### Making a contribution
+
+Please see [contribution processes](./processes.md) for more information on how
+to make a contribution to an OpenTelemetry repository.
+
+### Community Expectations and Roles
+
+OpenTelemetry is a community-driven project. We welcome contributions from all
+interested parties, regardless of affiliation. Our success is dependent on the
+community to provide a professional, productive, friendly, and collaborative
+environment.
+
+- Review the [Mission, Vision, and Values](../../mission-vision-values.md) to
+  understand the goals of the project.
+- Read the [Community Membership](../../community-membership.md) to understand
+  the roles and responsibilities of the community.
+- As you gain experience, we encourage you to move up the ladder from member to
+  triager, approver, and maintainer!
+
+## Next Steps
+
+Now that you've read through this guide, you're ready to start contributing to
+the project.
+
+<!-- TODO: Flesh out this section -->
\ No newline at end of file
diff --git a/guides/contributor/donations.md b/guides/contributor/donations.md
new file mode 100644
index 000000000..f0b656160
--- /dev/null
+++ b/guides/contributor/donations.md
@@ -0,0 +1,60 @@
+# Donations
+
+Donations of preexisting code fall into two broad categories:
+
+* **Small donations:** Some donations only amount to a single PR and should
+  usually just be contributed as such
+* **Large or complex donations:** Other donations are much larger, require
+  ongoing maintenance of their own, and/or introduce nuanced licensing issues
+
+Large donations – or small donations that turn up complex issues during PR
+review – should be referred to the Technical Committee (TC) by filing an issue
+in this `community` repository and tagging
+`@open-telemetry/technical-committee`. The TC will respond to donation
+proposals **within two weeks** (that is, after having time to meet and discuss
+live). If the TC has not responded to the donation request within that
+interval, the donating party can and should point to this document and request
+guidance at the TC's earliest convenience.
+
+All donated code requires a license compatible with the Apache Software License
+2.0, and donated code will require a change of copyright to reflect the
+OpenTelemetry Authors. The Governance Committee (GC) will also ask to review any
+trademarks (like the names of components) the donation can carry and make a
+decision to either remove those trademarks or transfer them to the CNCF.
+
+## Donation process
+
+Broadly, these are the steps the OpenTelemetry Governance and Technical
+Committees follow to handle a prospective donation.
+
+1. Per the above, the donating organization creates a GitHub issue using
+   the "Donation Proposal" form in the `community` repository.
+2. The GC will evaluate the proposal to ensure that
+   the donation is aligned with the overall OpenTelemetry project vision
+   and roadmap and has a balanced set of interested contributors and maintainers.
+   The GC is also responsible for driving awareness in the community about
+   the contribution and making sure all interested parties have a chance to
+   object and/or contribute. The GC should work with any appropriate Special Interest
+   Groups or Working Groups to evaluate the donation proposal, consider alternatives,
+   and ensure OpenTelemetry has the resources required to support the donation. When
+   considering alternatives, the GC should consider at least the CNCF ecosystem,
+   and may also consider other well-known open source projects or alternatives proposed
+   by the community.
+3. If a donation proposal passes the initial GC screening, the TC
+   will conduct due diligence to determine if the proposed donation can be effectively
+   integrated into the OpenTelemetry project in a way that meets the quality, security,
+   and privacy standards of the project without violating stable specification or OpenTelemetry Enhancement Proposals (OTEPs).
+   The TC will summarize their findings, and make a recommendation to either
+   accept or reject the proposal, conditionally or unconditionally, in a report which will
+   be attached to the donation proposal issue. Writing the report may require meeting
+   and discussing alternative technologies with different vendors in the community and
+   can be a lengthy process. The TC member driving the report will post updates and time
+   estimates to the issue.
+4. The GC will consider the report and make a final decision about the donation,
+   and document that decision on the donation proposal issue.
+5. If accepted, the contributing organization – particularly if it's a
+   commercial entity – must formally acknowledge via the GitHub issue that its
+   respective sales and marketing departments have received, understood, and
+   accepted the terms of the [OpenTelemetry marketing guidelines](https://github.com/open-telemetry/community/blob/main/marketing-guidelines.md).
+6. Given all of the above, the GitHub issue is closed and the donation moves
+   forward as agreed to by the TC and GC.
\ No newline at end of file
diff --git a/community-membership.md b/guides/contributor/membership.md
similarity index 89%
rename from community-membership.md
rename to guides/contributor/membership.md
index bb7b2bafc..71f9912ed 100644
--- a/community-membership.md
+++ b/guides/contributor/membership.md
@@ -1,12 +1,12 @@
-# Community membership
+# Membership, Roles, and Responsibilities
 
-This doc outlines the various responsibilities of contributor roles in
-OpenTelemetry. The OpenTelemetry project is subdivided into subprojects under
-(predominantly, but not exclusively) language-focused SIGs (Special Interest
-Group). Responsibilities for most roles are scoped to these subprojects (repos).
+OpenTelemetry is a project by, and for, its community. This document outlines
+the various roles and responsibilities of members, as well as the requirements
+for achieving each role. We encourage you to consider becoming a long-term
+contributor to the project, and moving up the ladder from member, all the way to
+maintainer!
 
-The OpenTelemetry [Governance Committee][] owns this document and process until
-delegated. They can be reached via e-mail <cncf-opentelemetry-governance@lists.cncf.io>.
+## Membership Levels
 
 | **Role**              | **Responsibilities**                                              | **Requirements**                                                                                                                           | **Defined by**                                                                                                |
 |-----------------------|-------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|
@@ -19,11 +19,13 @@ delegated. They can be reached via e-mail <cncf-opentelemetry-governance@lists.c
 
 ## New contributors
 
-New contributors should be welcomed to the community by existing members, helped
-with PR workflow, and directed to relevant documentation and communication
-channels.
+If you're a new contributor reading this guide -- welcome! We're excited you're
+here. New contributors should be welcomed and encouraged to participate in the
+project. Remember, contributions aren't limited to writing code, either --
+reporting bugs, writing documentation, working on the website, or being a part
+of our community management are all valuable.
 
-## Established community members
+## Established contributors
 
 Established community members are expected to demonstrate their adherence to the
 principles in this document, familiarity with project organization, roles,
@@ -254,36 +256,6 @@ does not believe you are ready for the role, or the subproject is not in need
 of additional maintainers, they may suggest an alternate role or growth areas
 in order to improve your chances to become a maintainer in the future.
 
-### Resolving technical conflicts within a SIG
-
-From time to time, the Maintainers for a given OpenTelemetry SIG may be unable
-to reach consensus on a technical issue. While it's healthy and appropriate to
-make a sincere attempt to understand all points of view and consider the
-tradeoffs, it's also healthy to occasionally "disagree and commit."
-
-Within OpenTelemetry, SIG Maintainers are chosen specifically *because* they
-are domain experts, so we would like to keep as much of the decision-making
-authority with the SIG Maintainers rather than immediately "escalating" to the
-overall OpenTelemetry-wide Technical Committee. As such, this is
-OpenTelemetry's process for resolving technical issues where Maintainers cannot
-reach consensus:
-
-1. The SIG Maintainers should succinctly document the options under
-consideration as a GitHub issue within the SIG's respective repo (note that it
-is *not* required to document the complete framing and pros/cons – just the
-actual go-forward options themselves).
-2. Each SIG Maintainer must formally vote for their choice by commenting on
-that issue.
-3. The option receiving the most votes wins.
-4. If the vote is a tie, the OpenTelemetry TC should be brought into the
-discussion, and the TC itself gets a (single) tiebreaking vote.
-
-While inevitably these sorts of decisions will be disappointing for somebody,
-it's incredibly important for the project to maintain velocity and recognize
-that we are all coming to these sorts of technical issues with the best of
-intentions and remain aligned about the overall goals of the OpenTelemetry
-project.
-
 ## Emeritus Maintainer/Approver/Triager
 
 For any healthy open source project, it is inevitable that contributors may move
diff --git a/CONTRIBUTING.md b/guides/contributor/processes.md
similarity index 59%
rename from CONTRIBUTING.md
rename to guides/contributor/processes.md
index de6d3e07e..44abcd34b 100644
--- a/CONTRIBUTING.md
+++ b/guides/contributor/processes.md
@@ -1,61 +1,33 @@
-# OpenTelemetry Contributor Guide
-
-Welcome to OpenTelemetry! This document is the single source of truth for how to
-contribute to the code base. Feel free to browse the [open
-issues](https://github.com/open-telemetry/community/issues?q=is%3Aissue+is%3Aopen+label%3Aarea%2Fcontributor-guide)
-and file new ones, all feedback welcome!
-
-# Before you get started
-
-## Sign the CLA
-
-Before you can contribute, you will need to sign the [Contributor License
-Agreement](https://docs.linuxfoundation.org/lfx/easycla/contributors).
-
-## Code attribution
-
-[License information](README.md#License) should be included in all source files where applicable.
-Either full or short version of the header should be used as described at [apache.org](https://www.apache.org/foundation/license-faq.html#Apply-My-Software).
-It is OK to exclude the year from the copyright notice. For the details on how to apply the copyright,
-see the next section.
-
-## Copyright Notices
-
-OpenTelemetry follows [CNCF recommendations](https://github.com/cncf/foundation/blob/master/copyright-notices.md)
-for copyright notices. We use "Copyright The OpenTelemetry Authors" notice form.
-
-According to CNCF recommendations if you are contributing third-party code
-you will need to [retain the original copyright notice](https://github.com/cncf/foundation/blob/master/copyright-notices.md#dont-change-someone-elses-notice-without-their-permission).
-
-Any contributed third-party code must originally be Apache 2.0-Licensed or must
-carry a permissive software license that is compatible when combining with
-Apache 2.0 License. At this moment, BSD and MIT are the only
-[OSI-approved licenses](https://opensource.org/licenses/alphabetical) known to be compatible.
-
-If you make substantial changes to the third-party code, _prepend_ the contributed
-third party file with OpenTelemetry's copyright notice.
-
-If the contributed code is not third-party code and you are the author we
-strongly encourage to avoid including your name in the notice and use the
-generic "Copyright The OpenTelemetry Authors" notice. See rationale for this
-recommendation [here](https://github.com/cncf/foundation/blob/master/copyright-notices.md#why-not-list-every-copyright-holder).
-
-## Code of Conduct
-
-Please make sure to read and observe our [Code of
-Conduct](https://github.com/open-telemetry/community/blob/master/code-of-conduct.md).
-
-## Community Expectations and Roles
-
-OpenTelemetry is a community project. Consequently, it is wholly dependent on
-its community to provide a productive, friendly, and collaborative environment.
-
-- See [Community
-  Membership](https://github.com/open-telemetry/community/blob/master/community-membership.md)
-  for a list the various responsibilities of contributor roles. You are
-  encouraged to move up this contributor ladder as you gain experience.
-
-# Your First Contribution
+# Contribution Lifecycle and Processes
+
+OpenTelemetry is a big project, and can be overwhelming at first glance. This
+guide aims to help you understand how to find things to work on, how to find
+help, and how changes are merged and released.
+
+## Table of Contents
+
+- [Contribution Lifecycle and Processes](#contribution-lifecycle-and-processes)
+  - [Table of Contents](#table-of-contents)
+  - [Your First Contribution](#your-first-contribution)
+    - [Finding something to work on](#finding-something-to-work-on)
+    - [Find a good first topic](#find-a-good-first-topic)
+      - [Issue Assignment in Github](#issue-assignment-in-github)
+  - [Special Interest Groups (SIGs)](#special-interest-groups-sigs)
+      - [SIG structure](#sig-structure)
+    - [SIG-specific contributing guidelines](#sig-specific-contributing-guidelines)
+    - [File an Issue](#file-an-issue)
+  - [Workflows](#workflows)
+    - [Communication](#communication)
+  - [GitHub workflow](#github-workflow)
+  - [Open a Pull Request](#open-a-pull-request)
+  - [Code Review](#code-review)
+  - [Code attribution and licensing](#code-attribution-and-licensing)
+    - [Copyright Notices](#copyright-notices)
+  - [Specification Changes](#specification-changes)
+    - [Creating specification issues](#creating-specification-issues)
+    - [Issue lifecycle](#issue-lifecycle)
+
+## Your First Contribution
 
 Would you like to help make robust, modern telemetry a built-in feature of
 modern software? We will help you understand the organization of the project and
@@ -69,7 +41,7 @@ Channel](https://cloud-native.slack.com/archives/CJFCJHG4Q) ([Get an invite to j
 questions on [Stack
 Overflow](https://stackoverflow.com/questions/tagged/open-telemetry).
 
-## Find something to work on
+### Finding something to work on
 
 Help is always welcome! For example, documentation (like the text you are
 reading now) can always use improvement. There's always code that can be
@@ -104,7 +76,7 @@ Unfortunately, due to GitHub limitations we can only assign issues to org
 members or repo collaborators. Instead, please state in a comment that you
 intend to work on this issue and it will be assumed to be yours.
 
-### Learn about SIGs
+## Special Interest Groups (SIGs)
 
 #### SIG structure
 
@@ -137,7 +109,7 @@ Make sure to adhere to the repository specific policies or issue templates to
 provide detailed information that will help prompt answer and resolution of an
 issue.
 
-### Contributing
+## Workflows
 
 OpenTelemetry is open source, but many of the people working on it do so as
 their day job. In order to avoid forcing people to be "at work" effectively
@@ -218,82 +190,54 @@ nuances:
 Note: if your pull request isn't getting enough attention, you can explicitly
 mention approvers or maintainers of this repository.
 
-# Community
-
-If you haven't noticed by now, we have a large, lively, and friendly open-source
-community. We depend on new people becoming members and regular code
-contributors, so we would like you to come join us! The [Community Membership
-Document](https://github.com/open-telemetry/community/blob/master/community-membership.md)
-covers membership processes and roles.
-
-## Donations
-
-Donations of preexisting code fall into two broad categories:
-* **Small donations:** Some donations only amount to a single PR and should
-  usually just be contributed as such
-* **Large or complex donations:** Other donations are much larger, require
-  ongoing maintenance of their own, and/or introduce nuanced licensing issues
-
-Large donations – or small donations that turn up complex issues during PR
-review – should be referred to the Technical Committee (TC) by filing an issue
-in this `community` repository and tagging
-`@open-telemetry/technical-committee`. The TC will respond to donation
-proposals **within two weeks** (that is, after having time to meet and discuss
-live). If the TC has not responded to the donation request within that
-interval, the donating party can and should point to this document and request
-guidance at the TC's earliest convenience.
-
-All donated code requires a license compatible with the Apache Software License
-2.0, and donated code will require a change of copyright to reflect the
-OpenTelemetry Authors. The Governance Committee will also ask to review any
-trademarks (like the names of components) the donation can carry and make a
-decision to either remove those trademarks or transfer them to the CNCF.
-
-### Donation process
-
-Broadly, these are the steps the OpenTelemetry Governance and Technical
-Committees follow to handle a prospective donation.
-
-1. Per the above, the donating organization creates a GitHub issue using
-   the "Donation Proposal" form in the `community` repository.
-2. The Governance Committee (GC) will evaluate the proposal to ensure that
-   the donation is aligned with the overall OpenTelemetry project vision
-   and roadmap and has a balanced set of interested contributors and maintainers.
-   The GC is also responsible for driving awareness in the community about
-   the contribution and making sure all interested parties have a chance to
-   object and/or contribute. The GC should work with any appropriate Special Interest
-   Groups or Working Groups to evaluate the donation proposal, consider alternatives,
-   and ensure OTel has the resources required to support the donation. When
-   considering alternatives, the GC should consider at least the CNCF ecosystem,
-   and may also consider other well-known open source projects or alternatives proposed
-   by the community.
-3. If a donation proposal passes the initial GC screening, the Technical Committee (TC)
-   will conduct due diligence to determine if the proposed donation can be effectively
-   integrated into the OpenTelemetry project in a way that meets the quality, security,
-   and privacy standards of the project without violating stable specification or OTEPs.
-   The TC will summarize their findings, and make a recommendation to either,
-   conditionally or unconditionally, accept or reject the proposal, in a report which will
-   be attached to the donation proposal issue. Writing the report may require meeting
-   and discussing alternative technologies with different vendors in the community and
-   can be a lengthy process. The TC member driving the report will post updates and time
-   estimates to the issue.
-4. The GC will consider the report and make a final decision about the donation,
-   and document that decision on the donation proposal issue.
-5. If accepted, the contributing organization – particularly if it's a
-   commercial entity – must formally acknowledge via the GitHub issue that its
-   respective sales and marketing departments have received, understood, and
-   accepted the terms of the [OpenTelemetry marketing guidelines](https://github.com/open-telemetry/community/blob/main/marketing-guidelines.md).
-6. Given all of the above, the GitHub issue is closed and the donation moves
-   forward as agreed to by the TC and GC.
-
-## Communication
-
-- [General
-  Information](https://github.com/open-telemetry/community#Communication)
-
-## Events
-
-OpenTelemetry participates in KubeCon + CloudNativeCon, held three times per
-year in China, Europe and in North America. Information about these and other
-community events is available on the CNCF [events](https://www.cncf.io/events/)
-pages.
+## Code attribution and licensing
+
+[License information](README.md#License) should be included in all source files where applicable.
+Either full or short version of the header should be used as described at [apache.org](https://www.apache.org/foundation/license-faq.html#Apply-My-Software).
+It is OK to exclude the year from the copyright notice. For the details on how to apply the copyright,
+see the next section.
+
+### Copyright Notices
+
+OpenTelemetry follows [CNCF recommendations](https://github.com/cncf/foundation/blob/master/copyright-notices.md)
+for copyright notices. We use "Copyright The OpenTelemetry Authors" notice form.
+
+According to CNCF recommendations if you are contributing third-party code
+you will need to [retain the original copyright notice](https://github.com/cncf/foundation/blob/master/copyright-notices.md#dont-change-someone-elses-notice-without-their-permission).
+
+Any contributed third-party code must originally be Apache 2.0-Licensed or must
+carry a permissive software license that is compatible when combining with
+Apache 2.0 License. At this moment, BSD and MIT are the only
+[OSI-approved licenses](https://opensource.org/licenses/alphabetical) known to be compatible.
+
+If you make substantial changes to the third-party code, _prepend_ the contributed
+third party file with OpenTelemetry's copyright notice.
+
+If the contributed code is not third-party code and you are the author we
+strongly encourage to avoid including your name in the notice and use the
+generic "Copyright The OpenTelemetry Authors" notice. See rationale for this
+recommendation
+[here](https://github.com/cncf/foundation/blob/master/copyright-notices.md#why-not-list-every-copyright-holder).
+
+## Specification Changes
+
+OpenTelemetry is driven by its
+[specification](https://github.com/open-telemetry/opentelemetry-specification)
+and [semantic conventions](https://github.com/open-telemetry/semantic-conventions).
+Making cross-cutting changes to the project will start in one of these two
+places. This section details how an idea becomes a specification change.
+
+### Creating specification issues
+
+A specification issue can be big, or small. A good specification issue, though,
+will be clear, concise, and scoped to a single, well-defined problem. Be sure to
+include specific examples of the problem you're trying to solve by opening a
+specification issue, along with any prior art or other relevant documentation.
+
+### Issue lifecycle
+
+Specification issues are regularly triaged by the Governance Committee (GC). The GC may accept,
+decline, or defer the issue until more details are added. Once an issue is
+accepted, it may need a sponsor from the TC who will be responsible for driving the
+issue to completion. Some issues may be small enough that they do not need a
+sponsor -- these issues can be worked on as soon as they are accepted.
diff --git a/guides/maintainer/README.md b/guides/maintainer/README.md
new file mode 100644
index 000000000..9b05a8e61
--- /dev/null
+++ b/guides/maintainer/README.md
@@ -0,0 +1,13 @@
+# Maintainers Guide
+
+Welcome! This guidebook is designed to collect and share best practices,
+processes, and other information on being a maintainer of an OpenTelemetry
+project.
+
+## Table of Contents
+
+TODO
+
+## What is a Maintainer?
+
+See [Maintainer](../contributor/membership.md) for more information.
diff --git a/guides/maintainer/conflict-resolution.md b/guides/maintainer/conflict-resolution.md
new file mode 100644
index 000000000..eb169e293
--- /dev/null
+++ b/guides/maintainer/conflict-resolution.md
@@ -0,0 +1,29 @@
+# Resolving technical conflicts within a SIG
+
+From time to time, the Maintainers for a given OpenTelemetry SIG may be unable
+to reach consensus on a technical issue. While it's healthy and appropriate to
+make a sincere attempt to understand all points of view and consider the
+tradeoffs, it's also healthy to occasionally "disagree and commit."
+
+Within OpenTelemetry, SIG Maintainers are chosen specifically *because* they
+are domain experts, so we would like to keep as much of the decision-making
+authority with the SIG Maintainers rather than immediately "escalating" to the
+overall OpenTelemetry-wide Technical Committee (TC). As such, this is
+OpenTelemetry's process for resolving technical issues where Maintainers cannot
+reach consensus:
+
+1. The SIG Maintainers should succinctly document the options under
+consideration as a GitHub issue within the SIG's respective repo (note that it
+is *not* required to document the complete framing and pros/cons – just the
+actual go-forward options themselves).
+2. Each SIG Maintainer must formally vote for their choice by commenting on
+that issue.
+3. The option receiving the most votes wins.
+4. If the vote is a tie, the OpenTelemetry TC should be brought into the
+discussion, and the TC itself gets a (single) tiebreaking vote.
+
+While inevitably these sorts of decisions will be disappointing for somebody,
+it's incredibly important for the project to maintain velocity and recognize
+that we are all coming to these sorts of technical issues with the best of
+intentions and remain aligned about the overall goals of the OpenTelemetry
+project.