-
Notifications
You must be signed in to change notification settings - Fork 764
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.
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
update slack channel links #3589
update slack channel links #3589
Conversation
Signed-off-by: Mathew Wicks <thesuperzapper@users.noreply.github.com> Signed-off-by: Mathew Wicks <5735406+thesuperzapper@users.noreply.github.com>
/assign @andreyvelich @terrytangyuan |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: terrytangyuan, thesuperzapper The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@thesuperzapper There are not internal Slack channels. |
@thesuperzapper Are you going to submit PR to update it back ? |
@andreyvelich , that is not correct, when we made those channels we were clear that the users should discuss in the It's also a lot less confusing, because users don't think about the working groups they think about the app they're using. Furthermore, if you compare the member counts of each of these channels, the |
@thesuperzapper We've been promoting Other channels ( @kubeflow/wg-training-leads @tenzen-y Please comment on this thread. |
@andreyvelich firstly, the reason that channel is listed in your charter is because it's where you're meant to discuss working group matters . You're not really allowed to have private channels, as the working groups are meant to operate in the open, where possible. I would suggest that you either make your main channel open or you can just start using the official channel. (After you make your private channels open , we could rename the existing |
Why this statement is true ? I don't think we discussed it before.
I don't understand why we can't keep channels as For example, for Manifests we have |
The main channels for users to ask questions about Notebooks and Pipelines are
The Also, I'm not sure that the pipelines working group actually uses slack for this purpose so they don't have a channel as far as I can see. The reason it's good to keep these separate is because we want people asking questions but we also don't want them interrupting our work. And also they're going to search for channels based on the thing that they're using, rather than the working group which owns them. |
I think, the main reason is why these channels have more users because they were created earlier (5 years ago) than WGs were established (3 years ago). I am happy to discuss it during our Kubeflow Community Call to provide consistent across Kubeflow components. |
This PR ensures we are linking to the public Slack channels, rather than the internal working group ones.
So we don't have people asking questions in the WG channels.
#wg-automl
replaced with#kubeflow-katib
#wg-training
replaced with#kubeflow-training-operator
It also updates the name of the channel for KFServing to KServe, and reflects that it is now a separate project:
#kubeflow-kfserving
renamed to#kserve
The problematic links were introduced in #3588