Skip to content

Suggestion: New PyPulseq Chat room on Gitter #364

@schuenke

Description

@schuenke

Hey all,

I want to suggest creating a new PyPulseq Chat.

Some people might know that we already have a PyPulseq Slack channel (#97 ), but it is not really used. I think the reasons for this might be:

  • Friction: Everybody has to create a new Slack account just for this workspace.
  • Discoverability: The channel cannot be found publicly and the invitation link in #pypulseq on Slack #97 has to be updated regularly.
  • History: The free version of Slack now only offers a 90-day chat history, so we lose all our old discussions.

For these reasons, I think it makes sense to move the PyPulseq chat to another framework. I would suggest switching to Gitter because:

  • No new accounts: You can just login to Gitter using your existing GitHub account.
  • Open & Public: A Gitter space can be made public so that anyone can find, join, or even preview the chat before joining.
  • Infinite History: It is free and built on the open-source Matrix network, and it doesn't delete old messages.
  • Flexible: You can use Gitter in your browser or any client compatible with Matrix (like Element, Thunderbird, or Weechat).
  • GitHub Integration: We can link this repository to the chat room(s) and even add a badge to the README that might look like this:

Gitter

I personally never used Gitter before, but to me it looks like the perfect fit for this purpose.

I already created a Gitter space, which you can join using the badge above or this link to try it out:
https://matrix.to/#/#pypulseq:gitter.im?web-instance[element.io]=app.gitter.im

Of course this is just a suggestion and if the community is against it, I will delete the workspace again. However, I thought it's easier to build your opinion on this if you can already try it out.

Best,
Patrick

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions