contributor-site icon indicating copy to clipboard operation
contributor-site copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Add Best Practices guide to contributing to Kubernetes

Open nitishfy opened this issue 2 years ago • 4 comments

This is a Feature Request

Although experienced developers and new folks are contributing to the K8s project. It can be beneficial especially to all the new folks where we can include a page with the motive of "Best practices in the community" depicting what are the things that should be followed and avoided. For eg. Don't spam, Try before asking, Don't work on an issue that has already been assigned, Be patient, etc.

Why is this needed

This page can really be helpful to all the new folks who are looking forward to contributing to the K8s project.

Comments:

If this issue gets accepted, I'd love to work on this issue since I've written a blog on it as well.

nitishfy avatar Aug 01 '22 15:08 nitishfy

It is already there in contributors guide and code of conduct.

deveshgoyal1000 avatar Aug 07 '22 03:08 deveshgoyal1000

@deveshgoyal1000 I feel like the document is good but it can be enhanced to make it look better by adding the above points mentioned.

nitishfy avatar Aug 07 '22 12:08 nitishfy

I agree with @deveshgoyal1000 we have most of this documented in the guide and the cheatsheet. We are also adding a "new contributor course" that will take people through the processes step by step based off the new contributor workshops that we used to run at in person events.

mrbobbytables avatar Aug 07 '22 13:08 mrbobbytables

@mrbobbytables May I know what topics does the following course covers?

nitishfy avatar Aug 07 '22 13:08 nitishfy

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:

  • 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Nov 05 '22 13:11 k8s-triage-robot

/close

nitishfy avatar Nov 10 '22 13:11 nitishfy

@NitishKumar06: Closing this issue.

In response to this:

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

k8s-ci-robot avatar Nov 10 '22 13:11 k8s-ci-robot