Skip to content
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

JupyterHub chat channels: Gitter or Zulip? #751

Closed
manics opened this issue Nov 26, 2024 · 20 comments · Fixed by #757
Closed

JupyterHub chat channels: Gitter or Zulip? #751

manics opened this issue Nov 26, 2024 · 20 comments · Fixed by #757

Comments

@manics
Copy link
Member

manics commented Nov 26, 2024

A while ago there was a Jupyter discussion on moving away from Gitter to Zulip or Discord. After a pause there's a new spurt of activity around Zulip:
jupyter/governance#182 (comment) and subsequent posts.

What do people think? Switch to Zulip, stick with Gitter, or wait and see? I don't think we should support multiple chat platforms.

@minrk
Copy link
Member

minrk commented Nov 26, 2024

Zulip seems to be where folks are going. It would be nice to move away from the gitter spam.

@choldgraf
Copy link
Member

+1 from me on Zulip. I'm more familiar with discord but I know the nepari folks have used Zulip for a while and really like it.

@choldgraf
Copy link
Member

To clarify: is the plan to use the jupyter Zulip and create a channel or something? Or to set up a dedicated hub team Zulip? I think I have a preference for the former in order to encourage more cross project communication, but if folks feel strongly about the latter then I'm ok with that

@minrk
Copy link
Member

minrk commented Nov 26, 2024

I would imagine channel/room(s) in the Jupyter Zulip

@manics
Copy link
Member Author

manics commented Nov 26, 2024

The existing Jupyter Zulip https://jupyter.zulipchat.com/

@sgibson91
Copy link
Member

sgibson91 commented Nov 26, 2024

Yeah, using gitter was always a big barrier for me, that got worse when it officially became a matrix instance. I'll go wherever, so long as it's away from gitter 😆

@rgaiacs
Copy link

rgaiacs commented Nov 26, 2024

I would imagine channel/room(s) in the Jupyter Zulip

This is what makes more sense to me.

@choldgraf
Copy link
Member

Try out the #jupyterhub zulip channel!

I've asked on the Jupyter Zulip instance, and they've created a #jupyterhub channel for us to try out. We don't have to treat this as a "decision" but I thought it'd be helpful to create something so that people could get a feel for what the workflow would look like.

@consideRatio
Copy link
Member

I'm very positive towards Zulip after having used it a while now!

@choldgraf
Copy link
Member

I'm in the same boat. I like the zulip interface, especially how topic create high level summaries that we can use to group chat. I also really like that it is a cross-jupyter space and makes it easier to quickly tag and bring in other people or projects in the ecosystem. I'm +1 on making it the preferred jhub space for sync chat

@yuvipanda
Copy link
Collaborator

my own involvement in some of these projects is now purely because of the interactions in Zulip, so it's now a big win.

@sgibson91
Copy link
Member

I feel much more able to participate in chats because of zulip. Gitter wasn't great, and the experience for me got worse when it became "just another matrix server".

@minrk
Copy link
Member

minrk commented Jan 22, 2025

Seems very positive so far, I opened #757 to udpat ethe links in this repo, then we can update the Gitter room descriptions to redirect folks

@sgibson91
Copy link
Member

Merged!

@minrk
Copy link
Member

minrk commented Jan 24, 2025

Thanks! I added links to the jupyterhub rooms and made them invite-only so new people (i.e. spam bots) can't join and post new messages. The history is still fully public and anyone already in there can still post messages.

Notably, the 'Binder' room isn't actually a gitter room, it's on petrichor.me, so I'm not sure who actually has admin rights to change anything about it. I posted a message there, though, since that's all I can do.

@sgibson91
Copy link
Member

sgibson91 commented Jan 24, 2025

Ah, that's my friend Jez Cope. Stuff with that room got all messed up in the switch from Gitter to Matrix and the support team did not come back with anything useful. I've pinged him in the OLS/OpenSeeds Slack (because I, embarrassingly, cannot remember his GitHub handle!) and asked for him to follow your lead.

@sgibson91
Copy link
Member

I also see this room too? https://matrix.to/#/#jupyterhub_binder:gitter.im

@jezcope
Copy link

jezcope commented Jan 24, 2025

Oh yeah, things got a bit messed up when New Vector acquired Gitter, the transition was not handled well. I no longer have access to an account with full admin rights to that room so I can't change permissions to prevent further posting, but I have:

  • Removed all remaining room addresses that I could (including the main one, @binder:petrichor.me)
  • Made it invite-only
  • Pinned @minrk's message
  • Updated the room topic with a link to Zulip

I also see this room too? https://matrix.to/#/#jupyterhub_binder:gitter.im

This address seems to resolve to the same room, so I think we're good. Let me know if there's anything else I can do!

@jezcope
Copy link

jezcope commented Jan 24, 2025

Oh, the other thing that I can do if you want is to kick all existing users from the room and then leave, which would functionally delete it since it's invite-only. It would live on for a while in the databases of servers that participated in it but would be unjoinable and eventually be garbage-collected. But there might be some value in retaining access to its history.

@minrk
Copy link
Member

minrk commented Jan 24, 2025

Wonderful, thank you! I don't feel the need to kick anyone out. The only real reason I turned on invite-only is to stop having to deal with the spam bots, which seem to be most new joins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants