Replace IRC with Slack in docs #13530
Conversation
|
GCE e2e build/test passed for commit 527344b4b944b4ce3b6ba005a7fe4a9e3f8ff11f. |
|
GCE e2e build/test failed for commit 231252fa879a4e57769ed96f39e32b96659659b2. |
k8s-github-robot
added
the
size/S
|
Labelling this PR as size/S |
|
Are you guys really moving to Slack off IRC? :( |
|
@k8s-bot please test this |
|
@yuvipanda yes, looks like it. we tried it out, and most people liked the grouping of channels under one team, newer UI, and some of the notifications you can set up. |
|
I see. Does this mean Slack is the new official place to get support for k8s? |
|
I'll throw in a vote against, even though it may not/doesn't matter. |
|
Another vote against. If connecting to IRC is too hard or the webchat is not enough, you can suggest things like irc cloud. |
|
Voting against doesn't help unless you explain why. The project is too big to have a single channel -- there's too much noise and cross-talk. I, for one, could rarely afford to pay attention it. We needed new channels for GKE vs. K8s, users vs. devs, SIGs, etc. We either could create lots of new IRC channels, or choose a new medium. A number of people suggested Slack. For instance, the scalability SIG decided to use it. We tried it and liked it. Among other issues, without threading, IRC is very hard to follow when there's more than one conversation. There's also no obvious way to search the logs. I don't know how to discover new IRC channels within a general topic area. With respect to support, we'd like people to try stackoverflow/stackexchange first. Real-time support doesn't scale, and we also get a lot of FAQs. And, regardless of the communication medium, we need the community to help more with support. |
| @@ -76,7 +76,7 @@ These guidelines say *what* to do. See the Rationale section for *why*. | |||
|
|
|||
| If you have a cluster partially working, but doing all the above steps seems like too much work, | |||
| we still want to hear from you. We suggest you write a blog post or a Gist, and we will link to it on our wiki page. | |||
| Just file an issue or chat us on IRC and one of the committers will link to it from the wiki. | |||
| Just file an issue or chat us on [Slack](https://github.com/docs/troubleshooting.md#slack) and one of the committers will link to it from the wiki. | |||
There was a problem hiding this comment.
Please use relative links everywhere. ../troubleshooting.md#slack in this case.
|
You need to run hack/update-generated-docs.sh. |
|
|
||
| The Kubernetes team hangs out on IRC at [`#google-containers`](https://botbot.me/freenode/google-containers/) on freenode. Feel free to come and ask any and all questions there. | ||
| The Kubernetes team hangs out on Slack in the `#kubernetes-users` channel. Slack requires registration, but the [Kubernetes](https://kubernetes.slack.com) team is open invitation to [join](http://slack.kubernetes.io). Feel free to come and ask any and all questions there. |
There was a problem hiding this comment.
It's not obvious which of these links the user should click on to join or participate. I suggest being more explicit, like register HERE and access the channels HERE.
Good news is that they have an IRC gateway, but it still requires signing up and it's messy when people send stuff other than text e.g. images or files. Also the whole mentioning via
Agreed on multiple channels, which works in either IRC or Slack.
Slack doesn't have threading, at least as far as I can see.
You use botbot.me, which makes this easy.
Freenode doesn't offer this service directly but some third parties do: Also, regarding notifications, you can have those set up by being connected all the time. You don't need to be connected directly, you can use a third party service like IRC Cloud which then can push notifications to your devices. |
|
I've enabled IRC gateway from Slack for the Kubernetes team. If you want to try it out, https://kubernetes.slack.com/account/gateways should give you the details you need. |
|
And our self-service signup page is http://slack.k8s.io |
goltermann
force-pushed
the
docs
branch
2 times, most recently
from
4a95a5b to
f8b9bcc
Compare
|
GCE e2e build/test failed for commit 4a95a5bc93f1f50840e17bc1154c5fba533241be. |
|
GCE e2e build/test failed for commit f8b9bcc794be7d8d1e9085586975ee2d45b5968c. |
|
@k8s-bot test this again (just barely timed out after passing all E2E tests) |
|
GCE e2e build/test passed for commit f8b9bcc794be7d8d1e9085586975ee2d45b5968c. |
j3ffml
added
lgtm
|
GCE e2e build/test passed for commit f0dbf1cca0f94cca82142ef6da62fbe4d6a70ded. |
|
GCE e2e build/test passed for commit bec4c10. |
j3ffml
added
the
lgtm
|
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
|
GCE e2e build/test passed for commit bec4c10. |
|
Automatic merge from SubmitQueue |
Auto commit by PR queue bot
Just a find and replace.