-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Set up an official slack or discord workspace #2715
Comments
I went ahead and created lerna.slack.com (updated 12.9.20) |
discord is the way to go |
Can you send a NEW LINK pls?); I have some complex problems with Lerna and dunno why; I want to speak with DEV's of Lerna |
Hi Folks 👋 Our team took over stewardship of the project last year, and the slack we recommend to join is the Nrwl Community one. There is a #lerna channel in there. Many thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is part of the proposal in #2703 (comment)
Set up an official slack workspace. Skip the heroku hosting, just do a free one. https://github.com/lerna/website/issues/47 as evidence supporting not hosting your own on heroku. You can also use the free plan with discord.com. Either one would work. I would suggest opening up the workspace to anyone interested and then restricting access via channels for maintainers (rather than requiring users to have a @thejameskyle.com email address — with this current setup, I'm discouraged from trying to become a maintainer and unable to just poke my head in and ask clarifying questions).
Problem
It's very unclear HOW to become a maintainer - This issue #1172 is calling for maintainers but provides no path for maintainers to answer the call. This issue https://github.com/lerna/website/issues/47 (that's been open since 2018) points out that https://slack.lernajs.io/ is down. I continued searching and I found this comment that mentions a lerna slack channel and so I tried to join the lernajs.slack channel and was told I needed to sign up with a @thejameskyle.com email address. This seems like a very odd barrier for interested maintainers to have to over come. I'm assuming that @jamiebuilds can elaborate on this decision because he owns the thejameskyle.com domain. I then checked out the lerna twitter account as suggested on lerna.js.org but found the last post is from 2018 and assumed any communication via that channel would be ignored.
The text was updated successfully, but these errors were encountered: