Changes per TAG Contrib Strategy review

Signed-off-by: Doug Davis <[email protected]>

OWNERS

@@ -1,4 +1,4 @@
-# See the GOVERNANCE.md document for the definition of the roles and
+# See the docs/GOVERNANCE.md document for the definition of the roles and
 # responsibilities
 admins:
   - deissnerk

README.md

@@ -96,6 +96,12 @@ The SDK [feature support table](cloudevents/SDK.md#feature-support) is a
 good resource to see which features, event formats and bindings are supported
 by each SDK.
 
+For more information about how the SDKs operate, please see the following
+documents:
+- [SDK Governance](docs/SDK-GOVERNANCE.md)
+- [SDK Maintainer Guidlines](docs/SDK-maintainer-guidelines.md)
+- [SDK PR Guidlines](docs/SDK-PR-guidelines.md)
+
 ## Community and Docs
 
 Learn more about the people and organizations who are creating a dynamic cloud
@@ -139,6 +145,9 @@ For SDK related comments and questions:
 - Archives are at: https://lists.cncf.io/g/cncf-cloudevents-sdk/topics
 - Slack: #cloudeventssdk on [CNCF's Slack workspace](http://slack.cncf.io/)
 
+For SDK specific communications, please see the main README in each
+SDK's github repo - see the [list of SDKs](#sdks).
+
 ### Meeting Time
 
 See the [CNCF public events calendar](https://www.cncf.io/community/calendar/).

docs/GOVERNANCE.md

@@ -5,6 +5,16 @@
 This document describes the governance process under which the CloudEvents
 project will manage this repository.
 
+For easy reference, additional documentation related to how this project,
+and its subprojects, operate are listed below:
+- [Contributing](CONTRIBUTING.md)
+  - [List of contributors to the project](contributors.md)
+- [Project Releases](RELEASES.md)
+- [Project Roadmap](ROADMAP.md)
+- [SDK Governance](SDK-GOVERNANCE.md)
+  - [SDK Maintainer Guidlines](SDK-maintainer-guidelines.md)
+  - [SDK PR Guidlines](SDK-PR-guidelines.md)
+
 ## Meetings
 
 In order to provide equitable rights to all members, the following process will
@@ -17,7 +27,8 @@ be followed:
   NOT LGTMs) and comments are strongly encouraged to gauge the group's opinion
   on the proposed change prior to the meeting.
 - During meetings, priority will be given to PRs that appear to be ready for a
-  vote over those that appear to require discussions.
+  vote over those that appear to require discussions. See [PRs](#prs) for more
+  information.
 - PRs should not be merged if they have had substantial changes made within two
   days of the meeting. Rebases, typo fixes, etc. do not count as substantial.
   Note, administrivia PRs that do not materially modify output documents may be
@@ -81,6 +92,10 @@ merged:
 - PRs that have objections/concerns will be discussed off-line by interested
   parties. A resolution, updated PR, will be expected from those talks.
 
+Anyone is welcome to comment on PRs, not just Admins, voting members or
+regular call participants. The goal of the project is consensus and broad
+community support, so community input is strongly encouraged.
+
 ## Voting
 
 If a vote is taken, the follow rules will be followed: