community/communication/slack-config
Stephen Augustus 2d34dde749 slack/sig-release: Add Tabby to Security Release Team usergroup
Signed-off-by: Stephen Augustus <foo@auggie.dev>
2021-04-27 21:23:31 -04:00
..
sig-architecture slack-config/sig-arch: Add enhancements-owners usergroup 2020-04-16 18:14:10 -04:00
sig-cloud-provider slack: renamed provider-alibaba-cloud channel 2019-12-20 18:31:04 +09:00
sig-docs fix: Rename kubernetes-docs-be to kubernetes-docs-bn (#5209) 2020-10-12 07:58:48 -07:00
sig-network Renaming Service APIs to Gateway API 2021-02-10 10:20:26 -08:00
sig-release slack/sig-release: Add Tabby to Security Release Team usergroup 2021-04-27 21:23:31 -04:00
sig-security add configs and updates for SIG Security 2021-01-01 19:54:18 -06:00
sig-storage Setting up a slack channel for sig-storage subproject kubernetes-cosi 2020-07-17 12:24:37 +00:00
sig-testing Move testing-commons subproject to best-effort 2021-01-27 16:55:27 -05:00
OWNERS Add munnerz as a primary admin/approver 2020-11-18 10:20:35 +00:00
README.md Rename kubernetes-sigs/slack-infra default branch 2021-04-01 15:19:20 -04:00
channels.yaml Add #kubewarden slack channel 2021-04-07 15:33:59 +02:00
restrictions.yaml Move sig-testing slack config to own folder 2021-01-27 16:55:22 -05:00
template.yaml Add initial slack config 2019-04-11 16:14:45 -07:00
usergroups.yaml slack/sig-release: Add Tabby to Security Release Team usergroup 2021-04-27 21:23:31 -04:00
users.yaml slack/sig-release: Add Wilson Husin to release-managers 2021-04-27 21:13:38 -04:00

README.md

Slack Config

YAML files in this directory control the state of Slack, via Tempelis. Updating a configuration file will result in Slack being updated once the change merges. If a change is not legal, a presubmit will fail.

Users

There is no safe, stable way to derive a specific Slack user from any human-readable identifier. Instead of using Slack IDs everywhere, a single mapping from GitHub usernames to Slack IDs is given in users.yaml. To reference a user, they must first be added to users.yaml.

Channels

Channels can be created by adding a new channel in channels.yaml. Channels should be sorted alphabetically. New channels will be created in accordance with the template specified in template.yaml.

Deleting channels is not permitted, but a channel can be archived by specifying archived: true, or unarchived by removing it (or specifying false).

To rename a channel, set its id property to its current Slack ID, then change the name.

A fully-specified channel looks like this:

- name: slack-admins # mandatory
  id: C4M06S5HS      # optional except when renaming
  archived: false    # optional for unarchived channels

Usergroups

Usergroups are pingable Slack groups. All members of a usergroup can be automatically added to certain channels. A usergroup must have at least one member. A usergroup can be removed by deleting it from the configuration.

Some usergroups (e.g. @test-infra-oncall) are managed by other tooling. To prevent Tempelis from trying to deactivate these usergroups, they can be included on the list and marked as external: true. Other usergroups should look like this:

- name: slack-admins               # mandatory, the pingable handle
  long_name: Slack Admins          # mandatory, the human-readable name
  description: Slack Admin Group   # mandatory, a description
  channels:                        # optional, a list of channels for members to auto-join
    - slack-admins
  members:                         # mandatory, a list of at least one member.
    - castrojo                     # member names must be listed in users.yaml.
    - katharine
    - jeefy
    - mrbobbytables
    - alejandrox1
    - jdumars
    - parispitmann
    - coderanger
    - idvoretskyi
    - idealhack