README for the Kubernetes landing Organisation page

[allgandalf]

Describe the issue

Currently on the landing page of Kubernetes GitHub, we directly see the pinned repositories as follows:

Opinion:

Shouldn't we have a README just to have a landing page with introduction to Kubernetes, Links to community guidelines, contributor guidelines, etc.

/sig docs

[shivakrishna0102]

Hey I want to look into this issue and want to create that readme.md

[allgandalf]

Hey @shivakrishna0102 , this is an issue I want to discuss with people from the community and get their point of view, there isn't a requirement of a PR in this case at present :)

[mrbobbytables]

Agree with @RohanSasne there is also already a readme in this repo, to update the org view it'd go in another location. With that I'm going to go ahead and close this out for now.

/close

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to this:

Agree with @RohanSasne there is also already a readme in this repo, to update the org view it'd go in another location. With that I'm going to go ahead and close this out for now.

/close

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.

[mrbobbytables]

Woops, thought this was the PR (which has now been closed). That's what I get for responding from my phone XD

/reopen

[k8s-ci-robot]

@mrbobbytables: Reopened this issue.

In response to this:

Woops, thought this was the PR (which has now been closed). That's what I get for responding from my phone XD

/reopen

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.

[allgandalf]

Totally cool, things like these happen all the time :), So What is your thought on the issue @mrbobbytables ?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten