search

kubernetes / contributor-site

Code for kubernetes.dev
https://www.kubernetes.dev
Apache License 2.0
66 stars 149 forks source link

hard time finding how to contribute to the site itself #289

Closed parispittman closed 1 year ago

parispittman commented 2 years ago

folks want to update the site itself and having hard time figuring how where to find this repo

"edit this site" with a link here

Atharva-Shinde commented 2 years ago

/assign

sftim commented 2 years ago

/kind feature

Atharva-Shinde commented 2 years ago

the crux is almost all the content on this website is not hardcoded in k/contributors-site repo itself. This content is present in either k/website or k/community or similar other repos. for example: The Contributors CheatSheet section is imported from here and is not present anywhere in kubernetes/contributors-site repository.

An exception to this is: all the Blogs of k8s.dev website which are present k/contributors-site repository. I have implemented an "edit this page" button for "Blog section" on my local repo which navigates to the actual blog .md file like this one

mrbobbytables commented 2 years ago

When we looked into this previously, the only good way of doing it was adding an additional frontmatter item with its original location and render that in the footer or something along those lines.

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

jberkus commented 2 years ago

/remove-lifecycle rotten

I think the immediate solution to this is to have a page on the site about how to contribute to the site, which exposes the complexity.

The eventual solution is to have allmost all of the contents of the site all live in one repo.

sreekaransrinath commented 1 year ago

Is this issue still open to work on?

@Atharva-Shinde mind if I take over and implement @jberkus' suggestions?

Atharva-Shinde commented 1 year ago

Sure@sreekaransrinath, a page describing the structure of this repo would be useful for new contributors

sreekaransrinath commented 1 year ago

/assign

k8s-triage-robot commented 1 year ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 year ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

sftim commented 1 year ago

/remove-lifecycle rotten

k8s-triage-robot commented 1 year ago

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

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

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 year ago

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:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 1 year ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/contributor-site/issues/289#issuecomment-1638493713): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.