summaryrefslogtreecommitdiff
path: root/contributors/guide
AgeCommit message (Collapse)Author
2018-01-29Merge pull request #1694 from castrojo/move-issue-triagek8s-ci-robot
Move issue triage guide into the contributor guide
2018-01-29Merge pull request #1703 from cblecker/guide-ownersk8s-ci-robot
Add OWNERS file for contributors/guide/
2018-01-29Merge pull request #1701 from halfcrazy/fix/typo-contributors-guidek8s-ci-robot
doc: fix typo in contributors guideline.
2018-01-30doc: fix typo in contributors guideline.zhuyan
2018-01-29Add OWNERS file for contributors/guide/Christoph Blecker
2018-01-29Merge pull request #1697 from guineveresaenger/morelinksk8s-ci-robot
fixing more links
2018-01-28fix: broken link to community-expectations.mdMoshe Immerman
2018-01-26fixing more linksguineveresaenger
2018-01-26Merge pull request #1695 from guineveresaenger/brokenlinkk8s-ci-robot
fixed links to community expectations
2018-01-26fixed links to community expectationsguineveresaenger
2018-01-26Add issue-triage to the main guideJorge O. Castro
2018-01-26This moves the issue triage guide into the contributor guideJorge O. Castro
2018-01-25move coding-conventions.md to guideTim Pepper
The coding-conventions document covers useful introductory guidance for all. This commit moves it out of the devel/ detail directory and into the contributor/guide, fixing up links from other doc's in this repo and leaving a cookie crumb of a document pointing at the new location. Signed-off-by: Tim Pepper <tpepper@vmware.com>
2018-01-25Merge pull request #1657 from tpepper/contrib_guidek8s-ci-robot
contrib guide: tighten some language
2018-01-24added missing link in github-workflowg-harel
2018-01-24contrib guide: tighten some languageTim Pepper
The difference between the two links for communications around questions and troubleshooting was not clear to me, and the wording made them seem somewhat redundant. They're really two separate topic links, so I've changed the wording to hopefully make it more clear that one has general communications information and once is actually a troubleshooting guide. Signed-off-by: Tim Pepper <tpepper@vmware.com>
2018-01-23Fix broken urlJorge O. Castro
2018-01-23Remove duplicate content and fix linksJorge O. Castro
2018-01-22Moving and revising community expectationsJorge O. Castro
2018-01-19* Remove the working comments from the top so users can just get to theJorge O. Castro
content * Remove inline todos and replace with link to labelled issues
2018-01-16adding contributor cheatsheet linkguineveresaenger
2018-01-16removed unnecessary link from guide README, also removed duplicate text from ↵guineveresaenger
linked file
2018-01-12moved cheatsheet to contributor guide for later useguineveresaenger
2018-01-10fix broken linksJessica Yao
2018-01-03Fix incorrect anchor for github markdown header in contributors guideKai Chen
2018-01-03Fix broken links in github-workflow.mdKai Chen
2018-01-03fixing broken linkguineveresaenger
2018-01-02moved Github workflow and diagram to contributors/guide folder and ↵guineveresaenger
referenced from both development.md and guide README
2017-12-22Fix some more linksChristoph Blecker
2017-12-21Update references to help wanted labelChristoph Blecker
2017-12-16contrib guide: update "help wanted" issue urlTim Pepper
The doc's referring to "help-wanted" labeled issues, but that shows zero open and closed, where there's a bunch with "help wanted" through the project history. This patch updates the url to search issues with the "help wanted label. Signed-off-by: Tim Pepper <tpepper@vmware.com>
2017-12-14contrib guide: add table of contentsTim Pepper
We're to a point were seeing the table of contents at the top is informative about overall flow of the doc. Will need to regenerate this if/when new sections are added since it's not a render-time artifact. Relates to issues #1413. Signed-off-by: Tim Pepper <tpepper@vmware.com>
2017-12-14moved warning on where to ask questions to the topguineveresaenger
2017-12-14removed commentguineveresaenger
2017-12-14clarifying SIG and asking questionsguineveresaenger
2017-12-13clarify help wanted issues on each subrepoguineveresaenger
2017-12-13clarify issues vs questions, fix serverfault linkguineveresaenger
2017-12-13explained how to choose a SIG and whyguineveresaenger
2017-12-13contrib guide: add PR, code review sections and cleanupTim Pepper
This patch hits a couple of improvement needed areas: * add a pull requests section * add a code review section * misc smaller cleanups noticed while doing the prior two Signed-off-by: Tim Pepper <tpepper@vmware.com>
2017-12-13Complete File an Issue sectionSahdev P. Zala
The File an Issue section is work in progress. Adding more detail with a broader coverage on what, why and where to file a issue to complete this section.
2017-12-13Complete File an Issue sectionSahdev P. Zala
The File an Issue section is work in progress. Adding more detail with a broader coverage on what, why and where to file a issue to complete this section.
2017-12-06contributing guide: add initial section on testingTim Pepper
This commit replaces the "Improvements needed" marker for the testing topic with an initial section of overview information and jumping off links to sig-testing, test documentation, and test code. Part of: https://github.com/kubernetes/community/issues/1413 Signed-off-by: Tim Pepper <tpepper@vmware.com>
2017-11-29Add issue triage sectionSahdev P. Zala
Issue triaging is an important contribution to the project and should be highlighted with other areas of contribution. Creating this PR per discussion in the ContribX SIG meeting on November 29, 2017.
2017-11-21Minor fix typosPenghao Cen
2017-11-20final redirectsguineveresaenger
2017-11-20redirect links and formattingguineveresaenger
2017-11-16updating KubeCon informationguineveresaenger
2017-11-16last tweaksguineveresaenger
2017-11-16tweakingguineveresaenger
2017-11-16entire document edited for realguineveresaenger
generated by cgit v1.2.3 (git 2.25.1) at 2026-03-11 16:33:24 +0000