Update readme with contact section #387
Conversation
|
@Madhu-1 PTAL :) |
|
@ShyamsundarR PTAL .. |
There was a problem hiding this comment.
@humblec request that the default text in the PR description be changed/removed to detail the current PR, at present it is reflecting the default text, Thanks.
| Join us at [Rook ceph-csi Channel](https://rook-io.slack.com/messages/CG3HUV94J/details/) | ||
| Please use the following to reach members of the community: | ||
|
|
||
| - Slack: Join our [slack channel](https://cephcsi.slack.com) |
There was a problem hiding this comment.
(query) We are going to have a new slack channel? Or, is this the same as the older one under Rook?
There was a problem hiding this comment.
same question. need to know the reason behind creating new channel :)
There was a problem hiding this comment.
Actually its different. Lets hear the feedback.
There was a problem hiding this comment.
@Madhu-1 @ShyamsundarR Its not necessary that, all CSI users are rook users. Atleast I came to know recently that there are enough users who use ceph-csi seperately. Thats the justification. :)
There was a problem hiding this comment.
we have around 86 users in current csi slack channel. what about them?
There was a problem hiding this comment.
We have 86 members in the other (rook managed) slack channel, are we going to maintain 2? Or, are we going to announce it to the channel that we are moving, or what is the plan here?
From whom are we expecting to hear feedback on for the new channel?
There was a problem hiding this comment.
From whom are we expecting to hear feedback on for the new channel?
@ShyamsundarR people who have contributed here or close to us, the list is avialable as a comment below. So that we can conclude based on majority :)
Thanks ..
There was a problem hiding this comment.
It does seem to me that having a more "general" forward facing channel for CSI isn't a bad idea. Pointing to the Rook channel is ok too IMO (at least for now). I do think it might be worth looking at a general "csi-users" slack channel under the Kubernetes slack that we just "share". A lot of questions that come in tend to be general CSI questions so it would make sense to me.
There was a problem hiding this comment.
@j-griffith thanks for sharing your thought! yeah, having a seperate channel to accommodate every ceph-csi users/dev..etc is better for long term. Regarding sharing kubernetes slack, it is a good idea, but unfortunately I dont think its going to happen. afaict, unless and until we/ceph-csi are hosted under kube, its not possible.
README.md
Outdated
| Please use the following to reach members of the community: | ||
|
|
||
| - Slack: Join our [slack channel](https://cephcsi.slack.com) | ||
| - Forums: [rook-dev](https://groups.google.com/forum/#!forum/ceph-csi) |
There was a problem hiding this comment.
Header text reads "rook-dev" and should change to cephcsi-dev?
If this is a dev channel should the google groups be renamed with the dev suffix?
There was a problem hiding this comment.
Changed, forgot to push, but its now.
There was a problem hiding this comment.
Is the channel a dev channel? If so can we suffix it with "-dev"?
There was a problem hiding this comment.
not really shyam, its meant for all ceph-csi communication. @ShyamsundarR
README.md
Outdated
|
|
||
| - Slack: Join our [slack channel](https://cephcsi.slack.com) | ||
| - Forums: [rook-dev](https://groups.google.com/forum/#!forum/ceph-csi) | ||
| - Twitter: [@rook_io](https://twitter.com/CephCsi) |
There was a problem hiding this comment.
Header text reads"@rook_io" and should read "@cephcsi" instead.
I am no social media expert, but do we actually need a separate twitter channel? Should this be done in conjunction with folks managing the existing Ceph handles and such?
There was a problem hiding this comment.
Corrected this too. Done.
There was a problem hiding this comment.
we can have a seperate channel if someone maintains it up to date. @rook_io to @cephcsi
There was a problem hiding this comment.
yep, its perfectly fine to have a seperate one. thanks
Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
|
@ShyamsundarR @Madhu-1 PTAL, I forgot to push the changes, but now its in place now. |
|
@rootfs @travisn @leseb @phlogistonjohn @j-griffith @gman0 need your input on creating a new slack channel @humblec please add if some missing some one here |
|
@Madhu-1 PTAL . |
|
Based on John's and Madhu's approval, merging this one. Thanks ! |
Update readme with contact section
Syncing latest changes from upstream devel for ceph-csi
Signed-off-by: Humble Chirammal hchiramm@redhat.com
Describe what this PR does
This PR adds reference to social contacts like Google Forum, Twitter handle and Slack channel specific to ceph-csi.
There are slack channels in other groups like
rook, but its not the case that, all the consumers of ceph-csi use Rook. Secondly someone else also may have ceph-csi shipped as part of their project, thus a channel available for communication. These channels should not be a blocker for having a specific channel for this repo/project.