-
Notifications
You must be signed in to change notification settings - Fork 1.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
void #3199
Comments
Agree 100%. And this is only issues in the main loopback project. This doesn't include the data source juggler and various other connectors and components (the Postgres connector has 50 open issues and 19 open pull requests has been barely touched in months for example). I appreciate the framework as a whole but it would be great if strongloop was a bit more open about what their priorities are and why so many issues (in some cases major ones) are left open and untouched for years. |
@lazaridis-com @zbarbuto We've been at this issue for awhile now and I've brought this up many times as one of our top priorities. I've been advocating opening up many of the repos to community so that members like you can help triage/maintain issues, docs, etc etc. Make it more open to the general public so that we can scale accordingly. There are discussions of what to do going forward with the next version of LoopBack -- no formal plans yet but there have been strategy discussions. Opinions are welcome -- I'll see what I can do to get your voices to the right people. |
Inspiring reading: http://words.steveklabnik.com/how-to-be-an-open-source-gardener |
No description provided.
The text was updated successfully, but these errors were encountered: