📖 Update documentation with CNCF community group

[embik]

Summary

We were notified on Slack that our docs still refer to the community calendar, which we no longer maintain. This replaces the reference with our CNCF community group instead. I've also made the docs index and repository readme consistent.

Related issue(s)

Fixes #

Release Notes

NONE

[embik]

/cc @mjudeikis

[embik]

/cherry-pick release-0.22

[kcp-ci-bot]

@embik: once the present PR merges, I will cherry-pick it on top of release-0.22 in a new PR and assign it to you.

In response to this:

/cherry-pick release-0.22

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dprotaso]

We'll probably want to cherry-pick #3086 first

[embik]

We'll probably want to cherry-pick #3086 first

The change in question is in v0.23.0 already, but we haven't updated our documentation link on kcp.io to the docs for that version. Will also do that (partially included in kcp-dev/kcp.io#35 already).

[dprotaso]

/lgtm

[kcp-ci-bot]

@dprotaso: changing LGTM is restricted to collaborators

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mjudeikis]

/lgtm
/approve

[kcp-ci-bot]

LGTM label has been added.

Git tree hash: 87ec8d6712cde80aa249c6d2a9cac7ebdbf23679

[kcp-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mjudeikis

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mjudeikis]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kcp-ci-bot]

@embik: #3101 failed to apply on top of branch "release-0.22":

Applying: Update repository readme and documentation index with CNCF community group
Using index info to reconstruct a base tree...
M	docs/content/index.md
Falling back to patching base and 3-way merge...
Auto-merging docs/content/index.md
CONFLICT (content): Merge conflict in docs/content/index.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Update repository readme and documentation index with CNCF community group
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-0.22

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[embik]

/cherry-pick release-0.23

Went for the wrong branch in the first place 🤦

[kcp-ci-bot]

@embik: cannot checkout release-0.23: error checking out release-0.23: exit status 1. output: error: pathspec 'release-0.23' did not match any file(s) known to git

In response to this:

/cherry-pick release-0.23

Went for the wrong branch in the first place 🤦

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.