Skip to content

Update Slack Channel in GOVERNANCE #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 8, 2025
Merged

Update Slack Channel in GOVERNANCE #27

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3598afb
Slack channel in template for Governance file
knottnt May 8, 2025
a552502
Update slack channel in Governance file
knottnt May 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion GOVERNANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ The goal is to make sure that the roles and responsibilities are well defined an

## Communication

The primary mechanism for communication will be via the `#provider-aws` channel on the Kubernetes Slack community.
The primary mechanism for communication will be via the `#aws-controllers-k8s` channel on the Kubernetes Slack community.
All features and bug fixes will be tracked as issues in GitHub. All decisions will be documented in GitHub issues.

In the future, we may consider using a public mailing list, which can be better archived.
Expand Down
2 changes: 1 addition & 1 deletion templates/GOVERNANCE.md.tpl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ The goal is to make sure that the roles and responsibilities are well defined an

## Communication

The primary mechanism for communication will be via the `#provider-aws` channel on the Kubernetes Slack community.
The primary mechanism for communication will be via the `#aws-controllers-k8s` channel on the Kubernetes Slack community.
All features and bug fixes will be tracked as issues in GitHub. All decisions will be documented in GitHub issues.

In the future, we may consider using a public mailing list, which can be better archived.
Expand Down