kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix broken links

This commit is contained in:
Jessica Yao 2018-01-10 16:38:23 -08:00
parent 07fa2336ed
commit e21d5d1908
2 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
contributors/guide/README.md
View File

@ -105,7 +105,8 @@ Another good strategy is to find a documentation improvement, such as a missing/
#### Sig structure
You may have noticed that some repositories in the Kubernetes Organization are owned by Special Interest Groups, or SIGs. We organize the Kubernetes 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.
SIGs also have their own CONTRIBUTING.md files, which may contain extra information or guidelines in addition to these general ones. These are located in the SIG specific community documentation directories, for example: sig-docs' is in the kubernetes/community repo's [/sig-docs/CONTRIBUTING.md](/sig-docs/CONTRIBUTING.md) file and similarly for other SIGs.
Some SIGs also have their own `CONTRIBUTING.md` files, which may contain extra information or guidelines in addition to these general ones. These are located in the SIG-specific community directories. For example: the contributor's guide for SIG CLI is located in the *kubernetes/community* repo, as [`/sig-cli/CONTRIBUTING.md`](/sig-cli/CONTRIBUTING.md).
Like everything else in Kubernetes, 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 kubernetes slack channel that you can join as well.

8
mentoring/README.md
View File

@ -1,11 +1,11 @@
# Kubernetes Mentoring Initiatives
# Kubernetes Mentoring Initiatives
This folder will be used for all mentoring initiatives for Kubernetes.
---
## Kubernetes Pilots
We understand that everyone has different learning styles and we want to support as many of those as possible. Mentoring is vital to the growth of an individual and organization of every kind. For Kubernetes, the larger the project becomes, it's necessary to keep a continuous pipeline of quality contributors.
We understand that everyone has different learning styles and we want to support as many of those as possible. Mentoring is vital to the growth of an individual and organization of every kind. For Kubernetes, the larger the project becomes, it's necessary to keep a continuous pipeline of quality contributors.
*What's a Pilot?*
A pilot is a Kubernetes mentor helping new and current members navigate the seas of our repos.
@ -13,7 +13,7 @@ A pilot is a Kubernetes mentor helping new and current members navigate the seas
## Current mentoring activities:
All are currently in an incubation phase. Please reach out to Paris Pittman (parispittman@google.com or Paris on Kubernetes slack channel) for more information on how to get involved. The preliminary deck for mentoring strategies is [here](https://docs.google.com/presentation/d/1bRjDEPEn3autWzaEFirbLfHagbZV04Q9kTCalYmnnXw/edit?usp=sharing0).
[Contributor Office Hours](/community/office-hours.md)
[Contributor Office Hours](/events/office-hours.md)
[Group Mentoring Cohorts](/mentoring/group-mentoring.md)
[Outreachy](/sig-cli/outreachy.md)
@ -29,5 +29,5 @@ Thanks to:
* the many contributors who reviewed and participated in brainstorming,
* founding mentees for their willingness to try this out,
* founding Pilots (@chrislovecnm, @luxas, @kow3ns)
We welcome PRs, suggestions, and help!