Add CoC and move some governance docs into 'community'

And some misc clean-up

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

README.md

@@ -72,9 +72,11 @@ In addition to the documentation mentioned above, there are also an
 Learn more about the people and organizations who are creating a dynamic cloud
 native ecosystem by making our systems interoperable with CloudEvents.
 
+- Our [Governance](community/GOVERNANCE.md) documentation.
+- How to [contribute](community/CONTRIBUTING.md) via issues and pull requests.
 - [Contributors](community/contributors.md): people and organizations who helped
   us get started or are actively working on the CloudEvents specification.
-- Coming soon: [demos & open source](community/README.md) -- if you have
+- [Demos & open source](community/README.md) -- if you have
   something to share about your use of CloudEvents, please submit a PR!
 
 ## Process
@@ -109,36 +111,34 @@ 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](https://slack.cncf.io/)
 
-
 ## Meeting Time
 
 See the [CNCF public events calendar](https://www.cncf.io/community/calendar/).
 This specification is being developed by the
 [CNCF Serverless Working Group](https://github.com/cncf/wg-serverless). This
-working group meets every Thursday at 9AM PT (USA Pacific):
+working group meets every Thursday at 9AM PT (USA Pacific)
+([World Time Zone Converter](http://www.thetimezoneconverter.com/?t=9:00%20am&tz=San%20Francisco&)):
 
 Join from PC, Mac, Linux, iOS or Android: https://zoom.us/my/cncfserverlesswg
 
-Or iPhone one-tap :
+Meeting ID: 336 102 9682
 
+Or mobile one-tap :
+```
     US: +16465588656,,3361029682#  or +16699006833,,3361029682#
+```
 
 Or Telephone:
+```
+    US: +1 646 558 8656 (US Toll) or +1 669 900 6833 (US Toll)
+    or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
+```
 
-    Dial:
-        US: +1 646 558 8656 (US Toll) or +1 669 900 6833 (US Toll)
-        or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)
-
-Meeting ID: 336 102 9682
-
-International numbers available:
-https://zoom.us/zoomconference?m=QpOqQYfTzY_Gbj9_8jPtsplp1pnVUKDr
+International numbers available
+[here](https://zoom.us/zoomconference?m=QpOqQYfTzY_Gbj9_8jPtsplp1pnVUKDr).
 
 NOTE: Please use \*6 to mute/un-mute your phone during the call.
 
-World Time Zone Converter:
-http://www.thetimezoneconverter.com/?t=9:00%20am&tz=San%20Francisco&
-
 ## Meeting Minutes
 
 The minutes from our calls are available

GOVERNANCE.md → community/GOVERNANCE.md

@@ -45,21 +45,21 @@ There are three categories of project membership:
    administrative actions on behalf of the group. For example, manage the
    website, github repos and moderate the meetings. Their actions should be done
    with the knowledge and consent of the group. They also have the ability to
-   merge/close PRs, but only per the group's approval. See the [OWNERS](OWNERS)
-   file for the current list of Admins.
+   merge/close PRs, but only per the group's approval. See the
+   [OWNERS](../OWNERS) file for the current list of Admins.
 
 ### Admins
 
 Since the role of an 'Admin' is mainly administrative, the list of Members
 within this group should not need to change regularly. The following rules
 govern adding and removing Admins:
 
-- New Admins can be proposed via a PR to edit the [OWNERS](OWNERS) file. Normal
+- New Admins can be proposed via a PR to edit the [OWNERS](../OWNERS) file.
+  Normal PR voting rules apply.
+- Admins can be removed via a PR to edit the [OWNERS](../OWNERS) file. Normal
   PR voting rules apply.
-- Admins can be removed via a PR to edit the [OWNERS](OWNERS) file. Normal
-  PR voting rules apply.
-- Admins can request to be removed via a PR to edit the [OWNERS](OWNERS) file.
-  Since the group can not force an Admin to continue in that role, the PR
+- Admins can request to be removed via a PR to edit the [OWNERS](../OWNERS)
+  file.  Since the group can not force an Admin to continue in that role, the PR
   does not follow the normal voting rules and can be merged by any of the
   Admins, including the person requesting to be removed. The exception to
   this "self-merge" aspect is when they are the last Admin. See next bullet.
@@ -93,7 +93,7 @@ If a vote is taken during a meeting, the follow rules will be followed:
   meeting, not during.
 - A "primary" or "alternate" member may request a leave-of-absence via an
   e-mail to the mailing list, or a message to the
-  [public slack channel](README.md#communications), prior to the absence.
+  [public slack channel](../README.md#communications), prior to the absence.
   An acceptable absence would include situations where the person is not
   officially working at all, such as being on vacation, taking a sabbatical or
   there is a public holiday. However, situations such as a scheduling conflict
@@ -127,7 +127,7 @@ The specifications produced will adhere to the following:
   during the release cycle.
 
 Note that these rules do not apply to the
-[documented extensions](documented-extensions.md).
+[documented extensions](../documented-extensions.md).
 
 To create a new release:
 
@@ -156,3 +156,8 @@ To create a new release:
     [twitter account](https://twitter.com/cloudeventsio)
   - Add it to the "announcement" section of our
     [website](https://cloudevents.io/)
+
+## Additional Information
+
+- We adhere to the CNCF's
+  [Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) guidelines

documented-extensions.md

@@ -19,10 +19,10 @@ might be changed, or removed, at any time. As such, inclusion of an attribute in
 this document does not need to meet the same level of maturity, or popularity,
 as attributes defined in the [CloudEvents specification](spec.md). To be
 included in this document, aside from the normal PR review process, the
-attribute needs to have at least two [Voting](GOVERNANCE.md#membership) member
-organizations stating their support for its inclusion as comments in the PR. If
-the author of the PR is also a Voting member, then they are allowed to be one of
-two.
+attribute needs to have at least two
+[Voting](community/GOVERNANCE.md#membership) member organizations stating their
+support for its inclusion as comments in the PR. If the author of the PR is
+also a Voting member, then they are allowed to be one of two.
 
 ## Usage