Skip to content

ibuildthecloud/community

Folders and files

NameName
Last commit message
Last commit date
May 13, 2016
Jul 18, 2017
Jul 25, 2017
Jul 14, 2017
May 29, 2017
Jun 7, 2017
Jun 22, 2017
Jun 22, 2017
Jul 24, 2017
Jul 20, 2017
Jun 27, 2017
Jun 22, 2017
Jun 22, 2017
Jun 22, 2017
Jun 22, 2017
Jun 22, 2017
Jun 22, 2017
Jul 12, 2017
Jul 12, 2017
Jun 22, 2017
Jul 12, 2017
Jul 26, 2017
Jun 22, 2017
Jun 22, 2017
Jun 22, 2017
Jun 22, 2017
Jul 20, 2017
Aug 22, 2016
Jul 19, 2017
Jun 22, 2017
Jun 22, 2017
Jul 19, 2017
Jun 22, 2017
Jul 11, 2017
Jun 22, 2017
Jul 7, 2017
Jul 24, 2017
Jul 14, 2017
Mar 7, 2017
Mar 8, 2017
May 3, 2016
Jul 14, 2017
Mar 15, 2017
Mar 15, 2017
Jun 21, 2017
May 12, 2017
Jun 14, 2017
May 12, 2017
May 25, 2017
Jul 26, 2017
Jul 26, 2017

Repository files navigation

Kubernetes Community

Welcome to the Kubernetes community!

This is the starting point for becoming a contributor - improving docs, improving code, giving talks etc.

Communicating

The communication page lists communication channels like chat, issues, mailing lists, conferences, etc.

For more specific topics, try a SIG.

SIGs

Kubernetes is a set of projects, each shepherded by a special interest group (SIG).

A first step to contributing is to pick from the list of kubernetes SIGs.

A SIG can have its own policy for contribution, described in a README or CONTRIBUTING file in the SIG folder in this repo (e.g. sig-cli/CONTRIBUTING), and its own mailing list, slack channel, etc.

How Can I Help?

Documentation (like the text you are reading now) can always use improvement!

There's a semi-curated list of issues that should not need deep knowledge of the system.

To dig deeper, read a design doc, e.g. architecture.

Pick a SIG, peruse its associated cmd directory, find a main() and read code until you find something you want to fix.

There's always code that can be clarified and variables or functions that can be renamed or commented.

There's always a need for more test coverage.

Learn to Build

Links in contributors/devel/README.md lead to many relevant topics, including

Your First Contribution

We recommend that you work on existing issues before attempting to develop a new feature.

Find an existing issue (e.g. one marked help-wanted, or simply ask a SIG lead for suggestions), and respond on the issue thread expressing interest in working on it.

This helps other people know that the issue is active, and hopefully prevents duplicated efforts.

Before submitting a pull request, sign the CLA.

If you want to work on a new idea of relatively small scope:

  1. Submit an issue describing your proposed change to the repo in question.
  2. The repo owners will respond to your issue promptly.
  3. If your proposed change is accepted, sign the CLA, and start work in your fork.
  4. Submit a pull request containing a tested change.

Analytics

About

Kubernetes community content

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Go 81.9%
  • Makefile 11.2%
  • Shell 6.9%