Oofff, that's a hard one... if there is a block th...
# team-maintainers
j
Oofff, that's a hard one... if there is a block then I would say they have two options: 1. Continue to communicate via GitHub (given they still have access) - their question seems relevant for an issue anyway (not sure where they got the idea to ask on Slack from? From a previous issue?) 2. Backup: Maybe they could also try anbd see if they can access the Nextflow forum/discourse? If so maybe we could set up an alternative route there
party this 1
m
the community forum would be my best solution as well
this 2
p
We decided a while ago not to have any official nf-core presence there (eg. categories, tags etc) but we can revisit that at any time.
It's under the Seqera domain so I would hope that it doesn't get blocked
l
The bioconductor community mooved from Slack to Zulip as they have a free pricing for open community, but this would be a really big change for everyone.
m
I have tried zulip. Not too bad
p
We actually started on zulip for nf-core a million years ago
So there's probably still an nf-core zulip kicking around somewhere with messages from Alex and me trying it out 😅
😆 2
Generally speaking, I think that moving away from Slack would be ultra-disruptive and we would lose many / most of the community that is here 😞 But if we have to one day, my two contenders are probably mattermost and the Seqera community forum / our own Discourse instance (which now also offers chat).
k
Agree with this approach. The correct solution for Chinese researchers is unfortunately probably going to be using a VPN. We can't make major infrastructure changes to our community just to accommodate one country's restrictive policies. sweats in American
🫠 3