Skip to content

Commit

Permalink
Added OWNERS.
Browse files Browse the repository at this point in the history
  • Loading branch information
gyliu513 committed Apr 29, 2019
1 parent e9c1915 commit fc71534
Show file tree
Hide file tree
Showing 5 changed files with 86 additions and 0 deletions.
13 changes: 13 additions & 0 deletions OWNERS
@@ -0,0 +1,13 @@
# See the OWNERS docs: https://git.k8s.io/community/contributors/guide/owners.md

approvers:
- sig-cluster-lifecycle-leads
- cluster-api-admins
- cluster-api-maintainers
- cluster-api-ibmcloud-maintainers

reviewers:
- cluster-api-maintainers
- cluster-api-ibmcloud-maintainers
- cluster-api-ibmcloud-reviewers
- sig-ibmcloud-leads
38 changes: 38 additions & 0 deletions OWNERS_ALIASES
@@ -0,0 +1,38 @@
# See the OWNERS docs: https://git.k8s.io/community/docs/devel/owners.md

aliases:
sig-cluster-lifecycle-leads:
- lukemarsden
- luxas
- roberthbailey
- timothysc
cluster-api-admins:
- justinsb
- krousey
- luxas
- roberthbailey
- kris-nova
cluster-api-maintainers:
- jessicaochen
- k4leung4
- karan
- kris-nova
- krousey
- medinatiger
- mkjelland
- roberthbailey
- rsdcastro
- spew
sig-ibmcloud-leads:
- ajayapte
- bradtopol
- khahmed
- mdelder
- spzala
cluster-api-openstack-maintainers:
- gyliu513
- jichenjc
- xunpan
cluster-api-openstack-reviewers:
- clyang82
- morvencao
9 changes: 9 additions & 0 deletions RELEASE.md
@@ -0,0 +1,9 @@
# Release Process

The Kubernetes cluster-api-provider-ibmcloud is released on an as-needed basis. The process is as follows:

1. An issue is proposing a new release with a changelog since the last release
1. All [OWNERS](OWNERS) must LGTM this release
1. An OWNER runs `git tag -s $VERSION` and inserts the changelog and pushes the tag with `git push $VERSION`
1. The release issue is closed
1. An announcement email is sent to `kubernetes-dev@googlegroups.com` with the subject `[ANNOUNCE] cluster-api-provider-ibmcloud $VERSION is released`
15 changes: 15 additions & 0 deletions SECURITY_CONTACTS
@@ -0,0 +1,15 @@
# Defined below are the security contacts for this repo.
#
# They are the contact point for the Product Security Team to reach out
# to for triaging and handling of incoming issues.
#
# The below names agree to abide by the
# [Embargo Policy](https://github.com/kubernetes/sig-release/blob/master/security-release-process-documentation/security-release-process.md#embargo-policy)
# and will be removed and replaced if they violate that agreement.
#
# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE
# INSTRUCTIONS AT https://kubernetes.io/security/

gyliu513
jichenjc
xunpan
11 changes: 11 additions & 0 deletions code-of-conduct.md
@@ -0,0 +1,11 @@
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
**Table of Contents** *generated with [DocToc](https://github.com/thlorenz/doctoc)*

- [Kubernetes Community Code of Conduct](#kubernetes-community-code-of-conduct)

<!-- END doctoc generated TOC please keep comment here to allow auto update -->

# Kubernetes Community Code of Conduct

Please refer to our [Kubernetes Community Code of Conduct](https://git.k8s.io/community/code-of-conduct.md)

0 comments on commit fc71534

Please sign in to comment.