Merge pull request #3772 from castrojo/contrib-metadata
Add hugo metadata to the contributor guides. Fixes #3769
This commit is contained in:
commit
19e0013d1c
|
@ -1,4 +1,9 @@
|
||||||
# Kubernetes Contributor Guide
|
---
|
||||||
|
title: "Kubernetes Contributor Guide"
|
||||||
|
weight: 1
|
||||||
|
slug: "guide"
|
||||||
|
---
|
||||||
|
|
||||||
|
|
||||||
<!--
|
<!--
|
||||||
Contributing to this document?
|
Contributing to this document?
|
||||||
|
|
|
@ -1,4 +1,8 @@
|
||||||
# Kubernetes Bug Bounty Program
|
---
|
||||||
|
title: "Bug Bounty Programs"
|
||||||
|
weight: 1
|
||||||
|
slug: "bounties"
|
||||||
|
---
|
||||||
|
|
||||||
This program is a **work in progress**. This tracks the currently proposed program, but the bug
|
This program is a **work in progress**. This tracks the currently proposed program, but the bug
|
||||||
bounty is not currently active. If you currently have a bug to submit, follow instructions at https://kubernetes.io/docs/reference/issues-security/security/
|
bounty is not currently active. If you currently have a bug to submit, follow instructions at https://kubernetes.io/docs/reference/issues-security/security/
|
||||||
|
|
|
@ -1,6 +1,8 @@
|
||||||
# Coding Conventions
|
---
|
||||||
|
title: "Coding Conventions"
|
||||||
Updated: 1/24/2018
|
weight: 1
|
||||||
|
slug: "coding-conventions"
|
||||||
|
---
|
||||||
|
|
||||||
**Table of Contents**
|
**Table of Contents**
|
||||||
|
|
||||||
|
|
|
@ -1,4 +1,8 @@
|
||||||
# On Collaborative Development
|
---
|
||||||
|
title: "Collaborative Development"
|
||||||
|
weight: 1
|
||||||
|
slug: "collab"
|
||||||
|
---
|
||||||
|
|
||||||
## Code reviews
|
## Code reviews
|
||||||
|
|
||||||
|
|
|
@ -1,4 +1,8 @@
|
||||||
# Community Expectations
|
---
|
||||||
|
title: "Community Expectations"
|
||||||
|
weight: 1
|
||||||
|
slug: "expectations"
|
||||||
|
---
|
||||||
|
|
||||||
Kubernetes is a community project. Consequently, it is wholly dependent on
|
Kubernetes is a community project. Consequently, it is wholly dependent on
|
||||||
its community to provide a productive, friendly and collaborative environment.
|
its community to provide a productive, friendly and collaborative environment.
|
||||||
|
|
|
@ -1,4 +1,8 @@
|
||||||
## Workflow
|
---
|
||||||
|
title: "GitHub Workflow"
|
||||||
|
weight: 1
|
||||||
|
slug: "github"
|
||||||
|
---
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
|
|
|
@ -1,3 +1,9 @@
|
||||||
|
---
|
||||||
|
title: "Help Wanted and Good First Issue Labels"
|
||||||
|
weight: 1
|
||||||
|
slug: "help-wanted"
|
||||||
|
---
|
||||||
|
|
||||||
# Overview
|
# Overview
|
||||||
|
|
||||||
We use two labels [help wanted](#help-wanted) and [good first
|
We use two labels [help wanted](#help-wanted) and [good first
|
||||||
|
|
|
@ -1,4 +1,8 @@
|
||||||
# Kubernetes Issue Triage Guidelines
|
---
|
||||||
|
title: "Issue Triage Guidelines"
|
||||||
|
weight: 1
|
||||||
|
slug: "issue-triage"
|
||||||
|
---
|
||||||
|
|
||||||
## Purpose
|
## Purpose
|
||||||
|
|
||||||
|
|
|
@ -1,4 +1,8 @@
|
||||||
# Non-code Contributions
|
---
|
||||||
|
title: "Non-code Contributions"
|
||||||
|
weight: 1
|
||||||
|
slug: "non-code"
|
||||||
|
---
|
||||||
|
|
||||||
*This section is new and in progress. Expect this document to change often.*
|
*This section is new and in progress. Expect this document to change often.*
|
||||||
|
|
||||||
|
|
|
@ -1,4 +1,8 @@
|
||||||
# OWNERS files
|
---
|
||||||
|
title: "OWNERS Files"
|
||||||
|
weight: 1
|
||||||
|
slug: "owners"
|
||||||
|
---
|
||||||
|
|
||||||
## Overview
|
## Overview
|
||||||
|
|
||||||
|
|
|
@ -1,4 +1,8 @@
|
||||||
# Pull Request Process
|
---
|
||||||
|
title: "Pull Request Process"
|
||||||
|
weight: 1
|
||||||
|
slug: "pull-requests"
|
||||||
|
---
|
||||||
|
|
||||||
This doc explains the process and best practices for submitting a pull request to the [Kubernetes project](https://github.com/kubernetes/kubernetes) and its associated subrepositories. It should serve as a reference for all contributors, and be useful especially to new and infrequent submitters.
|
This doc explains the process and best practices for submitting a pull request to the [Kubernetes project](https://github.com/kubernetes/kubernetes) and its associated subrepositories. It should serve as a reference for all contributors, and be useful especially to new and infrequent submitters.
|
||||||
|
|
||||||
|
|
|
@ -1,4 +1,8 @@
|
||||||
# Adding Release Notes
|
---
|
||||||
|
title: "Adding Release Notes"
|
||||||
|
weight: 1
|
||||||
|
slug: "adding-release-notes"
|
||||||
|
---
|
||||||
|
|
||||||
On the kubernetes/kubernetes repository, release notes are required for any pull request with user-visible changes, such as bug-fixes, feature additions, and output format changes.
|
On the kubernetes/kubernetes repository, release notes are required for any pull request with user-visible changes, such as bug-fixes, feature additions, and output format changes.
|
||||||
|
|
||||||
|
|
|
@ -1,4 +1,8 @@
|
||||||
# Scalability Good Practices for Kubernetes contributors
|
---
|
||||||
|
title: "Scalability Good Practices"
|
||||||
|
weight: 1
|
||||||
|
slug: "scalability-good-practices"
|
||||||
|
---
|
||||||
|
|
||||||
*This document is written for contributors who would like to avoid their code being reverted for performance reasons*
|
*This document is written for contributors who would like to avoid their code being reverted for performance reasons*
|
||||||
|
|
||||||
|
|
|
@ -1,9 +1,9 @@
|
||||||
---
|
---
|
||||||
title: Documentation Style Guide
|
title: "Documentation Style Guide"
|
||||||
|
weight: 1
|
||||||
|
slug: "documentation-style-guide"
|
||||||
---
|
---
|
||||||
|
|
||||||
# Documentation Style Guide
|
|
||||||
|
|
||||||
This style guide is for content in the Kubernetes github [community repository].
|
This style guide is for content in the Kubernetes github [community repository].
|
||||||
It is an extension of the [Kubernetes documentation style-guide].
|
It is an extension of the [Kubernetes documentation style-guide].
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue