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

[vote] Process for getting user references #13

Closed
dhmlau opened this issue Jan 7, 2022 · 1 comment · Fixed by #14
Closed

[vote] Process for getting user references #13

dhmlau opened this issue Jan 7, 2022 · 1 comment · Fixed by #14

Comments

@dhmlau
Copy link
Member

dhmlau commented Jan 7, 2022

Background

We have been getting user references via this github issue. The general process is to either post a message there or email me.

Towards the end of the year, @achrinza suggested to better document this user reference process, so that everyone (users and maintainers) know how to proceed.

There are mainly two things we're looking for user/company who would like to showcase their company in our web site because of their LoopBack usage.
1/ company logo to put on the main page "Who's using LoopBack?" section
2/ Optionally, a few sentences about their usage and experience with LoopBack - to be added in https://loopback.io/what-our-users-say.html.

Proposal

So far, we've been having good experience with the community in getting their reference. I'm thinking whether it would be even better to ask them to submit PRs to update our web site with their references. As maintainers would still be the ones who're approving (and rejecting) the PR, we can do our own validations.

@achrinza
Copy link
Member

achrinza commented Jan 8, 2022

+1 To document this process in this repo for consistency.

I'm thinking whether it would be even better to ask them to submit PRs to update our web site with their references.

I think this can be done, though we should be open to assisting them in creating the PR if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants