diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8b7eba983..c2565ae19 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -225,6 +225,27 @@ 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.
+
 ## Communication
 
 - [General
diff --git a/tech-committee-charter.md b/tech-committee-charter.md
index 8c00e644a..402ff0b9d 100644
--- a/tech-committee-charter.md
+++ b/tech-committee-charter.md
@@ -41,6 +41,7 @@ The TC is responsible for all technical development within the OpenTelemetry pro
 * Development process and any coding standards
 * Approving changes to any specifications
 * Mediating technical discussions which have cross project impact
+* Deciding on and communicating about proposed donations to OpenTelemetry
 
 The TC recognizes that maintainers of specific languages or sub-projects have significant autonomy over their SIG and implementations.  The TC’s focus is on cross-project or disputed concerns with a primary goal of seeking consensus to develop an appropriate technical solution. The TC will define OpenTelemetry’s release vehicles and serve as the primary technical liaison body for the OpenTelemetry project with the CNCF's TOC, external open source projects, consortiums and groups.
 
@@ -60,6 +61,13 @@ The development process will include a process for the TC to oversee and approve
 
 The TC and entire technical community will follow any processes as may be specified by the Cloud Native Computing Foundation relating to the intake and license compliance review of contributions, including the CNCF IP Policy.
 
+### Code Donations
+
+From time to time, organizations may wish to donate existing code to
+OpenTelemetry. The basic process for donating code is described [in
+CONTRIBUTING.md](/CONTRIBUTING.md#donations).  Of note is the expectation that
+the TC respond to donation proposals **within two weeks.**
+
 ## Elections
 
 Leadership roles in OpenTelemetry project will be peer elected representatives of the community.