diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-08-31 09:29:29 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-08-31 09:29:29 -0700 |
| commit | 689654f4aac66a094bce03e8d2f2961249a9ff88 (patch) | |
| tree | 116fc4722ade05aa3689b3aae1f5171bc26106ca | |
| parent | 0e8dfd3c48dc9a04f0f7d5ec8fd81e3b47ac7f71 (diff) | |
| parent | 1616ecd99521326b288775a6802358434bf82baf (diff) | |
Merge pull request #2607 from idvoretskyi/idvoretskyi-slackarchive-rm
README.md updated - slackarchive removed
| -rw-r--r-- | communication/README.md | 5 | ||||
| -rw-r--r-- | contributors/guide/issue-triage.md | 1 | ||||
| -rw-r--r-- | sig-governance.md | 1 |
3 files changed, 0 insertions, 7 deletions
diff --git a/communication/README.md b/communication/README.md index 01ba4b1f..2e44a0cb 100644 --- a/communication/README.md +++ b/communication/README.md @@ -24,10 +24,6 @@ and meetings devoted to Kubernetes. * Pose questions and help answer them on [Stack Overflow]. * [Slack] - sign up -Real time discussion at kubernetes.slack.io: -Discussions on most channels are archived at [kubernetes.slackarchive.io]. -Start archiving by inviting the _slackarchive_ bot to a -channel via `/invite @slackarchive`. To add new channels, contact one of the admins in the #slack-admins channel. Our guidelines are [here](/communication/slack-guidelines.md). ## Issues @@ -99,7 +95,6 @@ Kubernetes is the main focus of CloudNativeCon/KubeCon, held every spring in Eur [kubernetes-announce]: https://groups.google.com/forum/#!forum/kubernetes-announce [kubernetes-dev]: https://groups.google.com/forum/#!forum/kubernetes-dev [kubernetes-users]: https://groups.google.com/forum/#!forum/kubernetes-users -[kubernetes.slackarchive.io]: https://kubernetes.slackarchive.io [kubernetes.slack.com]: https://kubernetes.slack.com [Slack]: http://slack.k8s.io [Special Interest Group]: /README.md#SIGs diff --git a/contributors/guide/issue-triage.md b/contributors/guide/issue-triage.md index fd6e2eba..ef5e9c6d 100644 --- a/contributors/guide/issue-triage.md +++ b/contributors/guide/issue-triage.md @@ -58,7 +58,6 @@ Support requests should be directed to the following: [ServerFault](http://serverfault.com/questions/tagged/kubernetes) * [Slack](https://kubernetes.slack.com) ([registration](http://slack.k8s.io)) - * Check out the [Slack Archive](http://kubernetes.slackarchive.io/) first. * [Email/Groups](https://groups.google.com/forum/#!forum/kubernetes-users) diff --git a/sig-governance.md b/sig-governance.md index 3a7bb725..aee336e5 100644 --- a/sig-governance.md +++ b/sig-governance.md @@ -31,7 +31,6 @@ Guidelines for drafting a SIG Charter can be found [here](/committee-steering/go * Propose the new SIG publicly, including a brief mission statement, by emailing kubernetes-dev@googlegroups.com and kubernetes-users@googlegroups.com, then wait a couple of days for feedback. * Ask a repo maintainer to create a github label, if one doesn't already exist: sig/foo. * Request a new [kubernetes.slack.com](http://kubernetes.slack.com) channel (#sig-foo) from the #slack-admins channel. New users can join at [slack.kubernetes.io](http://slack.kubernetes.io). -* Slack activity is archived at [kubernetes.slackarchive.io](http://kubernetes.slackarchive.io). To start archiving a new channel invite the slackarchive bot to the channel via `/invite @slackarchive` * Organize video meetings as needed. No need to wait for the [Weekly Community Video Conference](community/README.md) to discuss. Please report summary of SIG activities there. * Request a Zoom account by emailing Paris Pittman(`parispittman@google.com`) and Jorge Castro(`jorge@heptio.com`). You must set up a google group (see below) for the SIG leads so that all the SIG leads have the ability to reset the password if necessary. * Read [how to use YouTube](/communication/K8sYoutubeCollaboration.md) for publishing your videos to the Kubernetes channel. |