[WIP] Put contributing guide(s) on kubernetes.io

[parispittman]

This is a...

• Feature Request
• Bug Report

Problem:
All codebase and community contributor guides, documents, and relevant materials are scattered in the community github repo. A recent survey of 110 participants concluded a pattern that contributors (new and others) need a central point where other k8s documents are located for a smoother flow and easier to locate. Focus groups are also ongoing with current contributors about their experience.

Proposed Solution:
Put all updated and relevant contributor information that is located in the community repo in multiple files into a single displayed source on kubernetes.io. This would fall under "Contributing to the Kubernetes Docs" with the title "Contributing to the Kubernetes Codebase & Community"

Page to Update:
https://kubernetes.io/docs/home/

will also 'live' on the user journeys/personas piece for 'code contributor'

Additional Info

• this will have a max of 8 sections (per @chenopis advice)
• a Developers Guide will be one of those sections; this is being worked on by another team (RyanJ at RH is point)
• @castrojo and I will run this through SIG-ContribX; join our bi-weekly discussions/mailing list
• need docs for final edits
• This is our raw document that we are working from -link. We will be trimming duplicate info, condensing, and adding information so that it's not 65 pages ( :) )

[guineveresaenger]

Initial PR for starting point:
kubernetes/community#1409

[guineveresaenger]

Umbrella issue to flesh out the README and surrounding folder in PR above: kubernetes/community#1413

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[justaugustus]

/remove-lifecycle stale

[heckj]

/lifecycle frozen

[mdlinville]

I believe this is fixed by #9510

[castrojo]

/reopen
/cc @mrbobbytables

This issue is about the overall k8s contributor's guide, not the documentation contribution guide. We're close to finishing this, @mrbobbytables can you update this issue when we go live?

[k8s-ci-robot]

@castrojo: you can't re-open an issue/PR unless you authored it or you are assigned to it.

In response to this:

/reopen
/cc @mrbobbytables

This issue is about the overall k8s contributor's guide, not the documentation contribution guide. We're close to finishing this, @mrbobbytables can you update this issue when we go live?

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]

@castrojo sure thing! Shouldn't take too long once the cname record is in place.

[mrbobbytables]

The cname record is put in place, netlify configured and the site is now live! :)

[DanyC97]

@mrbobbytables what is the url for site you mentioned above ?

[mrbobbytables]

Sorry for the delay in response, the project is over in https://github.com/kubernetes-sigs/contributor-site. As all work is going on over there. I think it's safe to close this issue :) Can be reopened if needed.

/close

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to this:

Sorry for the delay in response, the project is over in https://github.com/kubernetes-sigs/contributor-site. As all work is going on over there. I think it's safe to close this issue :) Can be reopened if needed.

/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.