-
Notifications
You must be signed in to change notification settings - Fork 7
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
Broken Slack invite link and issue with lists.carpentries.org #89
Comments
Thanks for reporting, @rmsds. I have opened #90 to fix the Slack link. The mailing list is currently set up to only allow messages from people subscribed to the group. Have you joined (at https://carpentries.topicbox.com/groups/maintainers-hpc)? @hpc-carpentry/steering-committee given that this address is listed for general enquiries on your contact page, I think this configuration is not ideal! Would you like me to adjust the settings so that messages from non-members are also allowed? (Warning: this usually results in a whole load of spam messages -- messages can be held for review and moderated, but it creates a bit more work.) |
You are welcome, thanks for the quick fix @tobyhodges I had not joined, I just placed the request. |
My mental model is that "discuss-hpc" is meant for general discussion and "maintainers-hpc" is for a narrower audience, but I'm not sure how widely shared that mental model is, or whether it's aligned with the intent of whoever created those addresses. |
I have approved the mailing list membership for @rmsds for now. |
On closer inspection, any messages sent to the list by non-members should be held for moderation & approval. So I do not think I got to the root cause of the error message @rmsds encountered. |
An inspection of the repo shows that the "maintainers-hpc" list is the default contact channel in several places, it's in the top-level config file, in the contribution guide, and in the recent incubation announcement blog post. Notwithstanding that @rmsds's issue may still be undiagnosed, how do we want to proceed? Given that the maintainers list is in fact closed, should we make the discuss-hpc list the default e-mail address? That makes sense to me, but also I think that was my mental model all along. |
I heard additional, independent reports of problems with TopicBox mailing lists recently, which appeared to be transient. I suggest closing this issue and keeping the current maintainers-hpc list, as messages can be sent to it, but will be held for approval: if we encounter any more issues like the one reported by @rmsds, we can re-open and investigate further. |
In the "Get involved" section in your landing page, the link to the Slack invite is broken (I get an Heroku "No such app" page).
In the topic of getting in contact with your team, I am also encountering an error when trying to send an email to the address listed in the contact page, although this might be a transient issue:
I sent you a message through Twitter with the same information, but I'm not sure if you are monitoring that account.
The text was updated successfully, but these errors were encountered: