Add governance policies (#38)

* Add governance policies

Add a number of policies and documents about CDEvents governance
and processes. A lot of content is inspired by the Tekton community
governance documents and adapted for CDEvents.

Key new things added:
- governing boards elections (eligibility, etc)
- contributor roles and ladder (eligibility, etc)

Some new mailing lists will have to be created.

The current bootstrap committee includes 5 individuals.
My proposal is to keep a team of five. For continuity, I propose that
- We held elections for three of the seats, to ensure continuity in the
  project governance.
- Emil and Andrea have been acting as project governance since the
  beginning, so their seats that be maintained until after 1 year
  after the election
- Mattias, Erik and Steve seats are up for election

* Add back the cdevents-code-of-conduct mailing list

This will have to be updated on the code of conduct in the .github repo
as well as in the community page on the website

* Align on governing board naming

* Remove the reviewer role

Remove the reviewer role as agreed during the WG meeting on 23.11
since the role is not used today and we'd like to keep policies
as simple as possible.

Clarify the stepping down / emeritus process.

---------

Signed-off-by: Andrea Frittoli <[email protected]>

README.md

@@ -4,12 +4,27 @@ This is the central home for the CDEvents community documentation.
 
 ## The CDEvents project
 
-## How to get involved
+CDEvents is a common specification for Continuous Delivery events.
+Its scope spans the entire software development lifecycle and it includes several projects:
+
+* [a specification](https://github.com/cdevents/spec)
+* various SDKs
+  * [golang](https://github.com/cdevents/go-sdk)
+  * [java](https://github.com/cdevents/go-java)
+  * [python](https://github.com/cdevents/go-python)
+* [the CDEvents website and primer](https://github.com/cdevents/cdevents.dev)
+
+Plus various experiments, proof-of-concepts and upcoming SDKs.
+
+To learn more about CDEvents:
 
-### How to get involved
+* read the [CDEvents docs and primer](https://cdevents.dev/docs/)
+* take a look at the [features we're working on](https://github.com/orgs/cdevents/projects/1)
+* take a look at the [tools integration we're working on](https://github.com/orgs/cdevents/projects/4)
 
-[Reach out](governance.md#project-communication-channels) to see what we're up
-via:
+## How to get involved
+
+Reach out to see what we're up via:
 
 * [slack](https://cdeliveryfdn.slack.com/archives/C030SKZ0F4K)
 * [our mailing list](https://groups.google.com/g/cdevents-dev)
@@ -18,14 +33,19 @@ via:
   * [EMEA/APAC Friendly](https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=YmV1Mmdna3RnbnYwZmszZm5nNTY2cTNuZmxfMjAyMzEwMzBUMTEwMDAwWiBsaW51eGZvdW5kYXRpb24ub3JnX21oZjBrbWdlZG42N2lobmk4cjEyOWF2cDI0QGc&tmsrc=linuxfoundation.org_mhf0kmgedn67ihni8r129avp24%40group.calendar.google.com&scp=ALL)
   * [Meeting Notes](working-group-notes.md)
 
-### Contributing
+## Contributing
 
 If you would like to contribute, see our [contributing](https://github.com/cdevents/.github/blob/main/docs/CONTRIBUTING.md)
 guidelines.
 
+See out standards and processes regarding:
+
+* [Code of conduct](https://github.com/cdevents/.github/blob/main/docs/CODE_OF_CONDUCT.md)
+* [Versioning](https://cdevents.dev/docs/primer/#versioning)
+* [Development](processes.md#contributions)
+* [Contributor Ladder](processes.md#contributor-ladder)
+
 ### Governance
 
-The project has been started by the CDF
-[SIG Events](https://github.com/cdfoundation/sig-events) and is currently
-[governed](governance.md) by a few members of the SIG.
+The project governance is documented in the [`governance.md` document](/governance.md).