Squashed commit of the following:

commit 7bebc93039
Author: Ihor Dvoretskyi <ihor@linux.com>
Date:   Thu Aug 30 14:44:23 2018 +0000

    sig-governance.md updated

    Signed-off-by: Ihor Dvoretskyi <ihor@linux.com>

commit ee0f24313f
Author: Ihor Dvoretskyi <ihor@linux.com>
Date:   Thu Aug 30 14:43:47 2018 +0000

    contributors/guide/issue-triage.md updated

    Signed-off-by: Ihor Dvoretskyi <ihor@linux.com>

commit 09bc3f6d9b
Author: Ihor Dvoretskyi <ihor@linux.com>
Date:   Thu Aug 30 14:42:38 2018 +0000

    README.md updated

    Signed-off-by: Ihor Dvoretskyi <ihor@linux.com>

commit 5b4146f10d
Author: Ihor Dvoretskyi <ihor@linux.com>
Date:   Thu Aug 30 14:26:51 2018 +0000

    README.md updated - slackarchive removed

    Signed-off-by: Ihor Dvoretskyi <ihor@linux.com>
This commit is contained in:
Ihor Dvoretskyi 2018-08-30 14:56:24 +00:00
parent 69583c388b
commit 8b68c72a17
3 changed files with 0 additions and 7 deletions

View File

@ -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

View File

@ -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)

View File

@ -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.