summaryrefslogtreecommitdiff
path: root/contributors/guide/first-contribution.md
diff options
context:
space:
mode:
authorJorge O. Castro <jorgec@vmware.com>2020-06-22 12:05:45 -0400
committerJorge O. Castro <jorgec@vmware.com>2020-06-22 12:05:45 -0400
commit67c6f7fe148a6eb5e164564ece60fea4d1a27a9e (patch)
treeee47b7ffe43824f92097e2a0657493f099a27d88 /contributors/guide/first-contribution.md
parente5a19ad6d6e677bc99cb073ae6180ccc57ff9074 (diff)
Merge getting started into the main page as they're required.
Restructure the main menu, fix up formatting. Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
Diffstat (limited to 'contributors/guide/first-contribution.md')
-rw-r--r--contributors/guide/first-contribution.md24
1 files changed, 7 insertions, 17 deletions
diff --git a/contributors/guide/first-contribution.md b/contributors/guide/first-contribution.md
index 4d3388d8..0126367e 100644
--- a/contributors/guide/first-contribution.md
+++ b/contributors/guide/first-contribution.md
@@ -17,16 +17,6 @@ description: |
- [SIG-specific contributing guidelines](#sig-specific-contributing-guidelines)
- [File an Issue](#file-an-issue)
-
-Have you ever wanted to contribute to the coolest cloud technology?
-We will help you understand the organization of the Kubernetes project and direct you to the best places to get started.
-You'll be able to pick up issues, write code to fix them, and get your work reviewed and merged.
-
-Please be aware that due to the large number of issues our triage team deals with, we cannot offer technical support in GitHub issues.
-If you have questions about the development process, feel free to jump into our [Slack Channel](http://slack.k8s.io/) or join our [mailing list](https://groups.google.com/forum/#!forum/kubernetes-dev).
-You can also ask questions on [ServerFault](https://serverfault.com/questions/tagged/kubernetes) or [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes).
-The Kubernetes team scans Stack Overflow on a regular basis and will try to ensure your questions don't go unanswered.
-
## Find something to work on
Help is always welcome! For example, documentation (like the text you are reading now) can always use improvement.
@@ -43,8 +33,6 @@ There are [multiple repositories](https://github.com/kubernetes/) within the Kub
Each repository has beginner-friendly issues that provide a good first issue.
For example, [kubernetes/kubernetes](https://git.k8s.io/kubernetes) has [help wanted](https://go.k8s.io/help-wanted) and [good first issue](https://go.k8s.io/good-first-issue) labels for issues that should not need deep knowledge of the system.
The `good first issue` label indicates that members have committed to providing [extra assistance](/contributors/guide/help-wanted.md) for new contributors.
-<!-- TODO: review removing this note after 3 months or after the 1.12 release -->
-Please note that while several of the repositories in the Kubernetes community have `good first issue` labels already, they are still being applied throughout the community.
Another good strategy is to find a documentation improvement, such as a missing/broken link, which will give you exposure to the code submission/review process without the added complication of technical depth. Please see [Contributing](#contributing) below for the workflow.
@@ -55,16 +43,18 @@ then the robot will assign the issue to you and your name will present at `Assig
### Learn about SIGs
-#### SIG structure
-
-You may have noticed that some repositories in the Kubernetes Organization are owned by Special Interest Groups, or SIGs.
+You may have noticed that some repositories in the Kubernetes Organization are owned by [Special Interest Groups](/sig-list.md), or SIGs.
We organize the community into SIGs in order to improve our workflow and more easily manage what is a very large community project.
-The developers within each SIG have autonomy and ownership over that SIG's part of Kubernetes.
+The developers within each SIG have autonomy and ownership over that SIG's part of Kubernetes. Check out the [list of SIGs](/sig-list.md) for contact information.
+
+Understanding how to interact with SIGs is an important part of contributing.
+
+#### SIG structure
A SIG is an open, community effort.
Anybody is welcome to jump into a SIG and begin fixing issues, critiquing design proposals and reviewing code.
SIGs have regular [video meetings](https://kubernetes.io/community/) which everyone is welcome to.
-Each SIG has a slack channel that you can join as well.
+Each SIG has a slack channel, meeting notes, and their own documentation that is useful to read and understand.
There is an entire SIG ([sig-contributor-experience](/sig-contributor-experience/README.md)) devoted to improving your experience as a contributor.
Contributing to Kubernetes should be easy.