Skip to content
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

Welcome users and contributors to loopbackio Slack workspace #5048

Closed
dhmlau opened this issue Apr 6, 2020 · 2 comments
Closed

Welcome users and contributors to loopbackio Slack workspace #5048

dhmlau opened this issue Apr 6, 2020 · 2 comments

Comments

@dhmlau
Copy link
Member

dhmlau commented Apr 6, 2020

We've created a Slack workspace for our users to join. Since Slack is quite commonly used, we think it is a good time for us to modernize our tooling for the LoopBack community helping out each out. Also, the LoopBack core team is using Slack on a daily basis, it helps us to get notifications and respond.

📣 Here we are: the loopbackio.slack.com Slack workspace.

How to join

Simply click this invitation link to join:
https://join.slack.com/t/loopbackio/shared_invite/zt-8lbow73r-SKAKz61Vdao~_rGf91pcsw

Channels

Currently, there are 4 public channels:

  • #general: general announcements (read-only). Only admins and owners can post in this channel. Members automatically join this channel.
  • #loopback-users: for LB4 users. Members automatically join this channel.
  • #loopback-contributors: for contributing to LoopBack, e.g. development setup, direction of PRs, etc.
  • #loopback3: for LB3 discussion

We're happy to hear from you on how to make things better. Please let us know!

Note: This Slack workspace is a platform for the community to help each other out. The core team and maintainers will also try our best to respond, but please keep in mind that our bandwidth is limited. ❤️

achrinza added a commit to achrinzafork/loopback-next that referenced this issue Apr 7, 2020
Replaces community chat link from Gitter to Slack workspace

see loopbackio#5048

Signed-off-by: Rifa Achrinza <[email protected]>
achrinza added a commit to achrinzafork/loopback.io that referenced this issue Apr 7, 2020
achrinza added a commit to achrinzafork/loopback.io that referenced this issue Apr 7, 2020
@dhmlau dhmlau self-assigned this Apr 7, 2020
achrinza added a commit to achrinzafork/loopback-next that referenced this issue Apr 7, 2020
Replaces community chat link from Gitter to Slack workspace

see loopbackio#5048

Signed-off-by: Rifa Achrinza <[email protected]>
achrinza added a commit that referenced this issue Apr 7, 2020
Replaces community chat link from Gitter to Slack workspace

see #5048

Signed-off-by: Rifa Achrinza <[email protected]>
raymondfeng pushed a commit that referenced this issue Apr 8, 2020
Replaces community chat link from Gitter to Slack workspace

see #5048

Signed-off-by: Rifa Achrinza <[email protected]>
achrinza added a commit to achrinzafork/loopback-next that referenced this issue Apr 16, 2020
raymondfeng pushed a commit that referenced this issue Apr 16, 2020
@stale
Copy link

stale bot commented Dec 25, 2020

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale stale bot added the stale label Dec 25, 2020
@stale
Copy link

stale bot commented Jul 14, 2021

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

@stale stale bot closed this as completed Jul 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant