charter.md

SIG etcd Charter

This charter adheres to the conventions described in the Kubernetes Charter README and uses the Roles and Organization Management outlined in sig-governance.

Scope

Owns the etcd project and how it is used by Kubernetes.

In scope

Code, Binaries and Services

• Development of etcd and other repositories under etcd-io organization
• Maintenance of etcd image packaged with Kubernetes

Cross-cutting and Externally Facing Processes

• Specifying, testing and improving the implicit Kubernetes-ETCD Contract, which includes storage requirements, write and delete requirements, read requirements and watch requirements.
• Release process of etcd and other binaries belonging to etcd-io organization

Out of scope

• Structure of data stored in etcd by Kubernetes components is owned by SIG API Machinery

Roles and Organization Management

This SIG follows the Roles and Organization Management outlined in sig-governance and opts-in to updates and modifications to sig-governance.

Additional responsibilities of Tech Leads

• Release of etcd and other binaries belonging to etcd-io organization

Deviations from sig-governance

• SIG etcd's participation in the Kubernetes release cycle is limited by etcd having a different schedule for its releases.
• SIG etcd communication utilizes pre-existing forums for communication:
  • Email: etcd-dev.
  • Slack: #etcd channel on Kubernetes.
• SIG etcd contributing instructions (CONTRIBUTING.md) be defined in etcd project.

Deviations from kubernetes-repositories

• SIG etcd repositories live in github.com/etcd-io
• SIG etcd repositories should (but not must) adopt merge bot, Kubernetes PR commands/bot.
• SIG etcd repositories will follow rules for donated repositories.

Subproject Creation

By SIG Technical Leads