search

rust-cuda / wg

rust-cuda working group
Apache License 2.0
65 stars 7 forks source link

Interactive communication channel #3

Closed gnzlbg closed 5 years ago

gnzlbg commented 5 years ago

We are already enough people to create an "official" working group. There are a couple of things to do before an announcement, which might attract even more people to work together, but I think that the first thing is to find a place to interactively be able to communicate.

Expressed preferences

These are the expressed preferences for an interactive communication tool:

@gnzlbg -> preferably zulip, but discord would work too @denzp -> slack for work so its open most of the time, but zulip would work too @bheisler -> preferably slack/discord, but zulip could work too, @vadixidav -> @termoshtt -> preberable slack, but discord/zulip could work too

Would be cool if you could chime in, even if just to say "no strong preference".

Requirements and candidates

So what's your preference, if any?

Also, keep in mind that the tool has to work for us, we can try Discord, or Zulip, and if it doesn't work, we can move to something else. This is completely up to us.

gnzlbg commented 5 years ago

My personal preference is Zulip. It's currently used by the wg-unsafe-code-guidelines, wg-nll, wg-secure-code, and wg-traits. I hate having multiple tools open, and at one point I had IRC, Discord, and Zulip open, but I've mostly cutted on IRC and Discord because I found Zulip to just be nicer for these kind of use cases - I still join Discord occasionally to interact with the wg that use it, and I will keep it open all the time if that's what we choose.

There are pros and cons to zulip:

For me the big pro is that all conversations are threaded, so you always know what people are talking about, be it a github issue, a topic, a meeting, etc. And you can filter the chat by conversation and follow along even though there might be multiple conversations going on at the same time. This makes it trivial to e.g. collect meeting minutes.

termoshtt commented 5 years ago

I usually use slack, but discord/zulip would work.

denzp commented 5 years ago

I tried Zulip today and enjoyed the threads conversation model. Alternatively, I use Slack for work and it's open most of the time, so it should work for me as well.

gnzlbg commented 5 years ago

There appears to be a strong preference for Slack. There does not seem to be an official rust-lang channel/organization, so I worry that we might have problem attracting new people and interacting with the rest of the community if we host it there (e.g. sometimes it is useful to just ping somebody from the compiler team or the libs team).

Is this worry unfounded ?

denzp commented 5 years ago

@gnzlbg I think your concerns are correct. Interaction with the rest of the community in the best case will be limited. TIL there is no easy way to make a "public" workspace in Slack, only workarounds with automatic inviting.

And yes, free accounts in Slack are subjected to message history limit. So I think Slack is not really an option for us...

I would say that now I prefer Zulip, but I'm also open to any other platform as well.

Regards to Zulip and Discord comparison (never really used both before) it feels to me, that Discord Rust community is bigger / more active. The argument might be a game changer if we want to get more feedback from community.

gnzlbg commented 5 years ago

Regards to Zulip and Discord comparison (never really used both before) it feels to me, that Discord Rust community is bigger / more active. The argument might be a game changer if we want to get more feedback from community.

You are completely right! I just checked and there are ~400 Discord users. Zulip does not provide an exact count AFAICT, but quickly counting them it appears to have 100-150 users.

I would say that now I prefer Zulip, but I'm also open to any other platform as well.

I still prefer Zulip for collaborating, talking about implementation-related work, etc. But as a channel for beginner and new users to ask questions, Discord might be a better place.

The trade-offs are unclear, so I've done the following: I've asked for a wg-cuda channel in both Zulip and Discord. We can start using Zulip to collaborate, and those of us who will hang on Discord anyways, can also use the wg-cuda channel to give us some visibility, and so that we can answer beginner questions if any.

We can decide at a later time whether we move exclusively to Zulip, or to Discord, or just keep both. If we decide at a later time to move to Discord, I'll ask for a "group of channels" instead, so that we can keep conversations related to different topics (implementation, meetings, questions, etc.) separated.

gnzlbg commented 5 years ago

So I managed to contact the people in charge, and until the edition is released the policy is to not charter any more working groups. After the edition, the plan is to first create a process about how to create working groups, and decide on what to work next for the next edition.

What does this mean for us? For now, we won't have a channel in the official Discord / Tulip rust-lang organizations, nor a tag on Discord, etc.

It doesn't mean that we can't work together on solving issues that are important for us.

I've created a Zulip organization for rust cuda, please join: https://rust-cuda.zulipchat.com

If we feel like we should use Discord, we can just create a Discord organization in the future and move there.

Dylan-DPC-zz commented 5 years ago

@gnzlbg can't join. people need an invitation to join the zulip channel

gnzlbg commented 5 years ago

I’ve set the Zulip channel to no invite required, it should work now.

On Mon 12. Nov 2018 at 18:17, Dylan DPC notifications@github.com wrote:

@gnzlbg https://github.com/gnzlbg can't join. people need an invitation to join the zulip channel

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rust-cuda/wg/issues/3#issuecomment-437951188, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3NpqxisIwm-3bJ5WMMp91JHF34EuiBks5uuaZ-gaJpZM4YZNae .