-
Notifications
You must be signed in to change notification settings - Fork 43
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
Discord Community? #46
Comments
I think I'd prefer to stick with Slack for the time being. There's not so many questions on the Slack community at the moment that message history retention is a massive issue. It's also easier for me as I've got all my other work things in Slack - I'm not a fan of having to run lots of different messenging services at once. Thanks for the suggestion - maybe we can revisit in the future, but for the mo people should head to Slack. |
Oh, I didn't even know there was a Slack community, sorry! I looked for something on the website, maybe I'm being blind? |
Had another look, I can't find a link for it anywhere? |
Yeah good point, I need to add it to the website. See you've managed to find the link in the meantime! |
If anyone else is looking at this issue, here's the Slack link: https://join.slack.com/t/laraveljsonapi/shared_invite/zt-e3oi2r4y-8nkmhzpKnPQViaXrkPJHtQ |
I did, it was on the old repo :-) |
I'm very much aware that asking lots of questions inside of GitHub issues is likely to cause a bit of a mess for the maintainers. Would you be open to having a Discord community for general questions and support?
I say Discord because it can be used for free and retains the message history, as opposed to Slack.
The text was updated successfully, but these errors were encountered: