search

kubernetes / contributor-site

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

[content] stuff to surface for current contributors #60

Closed parispittman closed 2 years ago

parispittman commented 5 years ago

Taking from this doc and setting as an issue so we can close the doc down.

parispittman commented 5 years ago

confirming with github analytics against the community repo that we should definitely surface api-conventions as a first class piece of content on the site. in order of highest views: api-convention.md Entire community repo Architecture Horizontal pod autoscaler Entire devel folder Sig list Contributor guide Resource metrics api

celanthe commented 5 years ago

Per a conversation with @parispittman--I am going to be taking this on and collaborating with her on it. :)

celanthe commented 5 years ago

/assign @celanthe

fejta-bot commented 4 years ago

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

mrbobbytables commented 4 years ago

Specific content can be imported pretty easily. The scripts are in place, the documentation though is not 😬 I'll create an issue to update that.

/remove-lifecycle stale

vishakhanihore commented 4 years ago

Hello, @mrbobbytables and @parispittman , I am outreachy applicant and have applied for Technical Writer, Can I start contributing to this issue, since there is around a month in results 😄 ?

celanthe commented 4 years ago

I'm happy to let @vishakhanihore contribute to this as well @parispittman @mrbobbytables -- It would be nice to have some help! :)

celanthe commented 4 years ago

Hi all, just an update, wanted to circle back with @parispittman @mrbobbytables about having @vishakhanihore and I collaborate on this with y'all once things calm down a bit after KubeCon! :) If that sounds good, let me know! :) Looking forward to it and thanks so much!

fejta-bot commented 4 years ago

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

vishakhanihore commented 4 years ago

/remove-lifecycle stale

On Mon, 17 Feb, 2020, 00:00 fejta-bot, notifications@github.com wrote:

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 https://github.com/fejta. /lifecycle stale

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubernetes-sigs/contributor-site/issues/60?email_source=notifications&email_token=AM6PS4SAWEKV4RC4BZ6UERLRDGA4XA5CNFSM4HJG7MXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4ON5I#issuecomment-586737397, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM6PS4WIYWP6M3MJE4UNSPDRDGA4XANCNFSM4HJG7MXA .

fejta-bot commented 4 years ago

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

celanthe commented 4 years ago

Hi all--As I'm stepping back from contributing outside of my Storyteller role on the Upstream Marketing team, I've unassigned myself from this issue. Was wondering if @vishakhanihore was still interested in taking it on?

fejta-bot commented 4 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

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 rotten

mrbobbytables commented 4 years ago

/lifecycle frozen

sftim commented 4 years ago

I'd like to see the content currently in https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api_changes.md published on https://k8s.dev/ so that it has a stable URI (and there's an opportunity to redirect to it if there is ever a change).

sftim commented 4 years ago

Looking at https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md I think this is also relevant to people who aren't planning to contribute to Kubernetes (eg: someone writing a CustomResourceDefinition or a controller).

Should that page move to within https://kubernetes.io/ ?

CIPHERTron commented 2 years ago

/assign

CIPHERTron commented 2 years ago

/remove-lifecycle frozen

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

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.

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes/contributor-site/issues/60#issuecomment-1120244833): >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: >- 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 or PR with `/reopen` >- Mark this issue or PR 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 > >[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.