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

void #3199

Closed
ghost opened this issue Feb 12, 2017 · 3 comments
Closed

void #3199

ghost opened this issue Feb 12, 2017 · 3 comments

Comments

@ghost
Copy link

ghost commented Feb 12, 2017

No description provided.

@zbarbuto
Copy link
Member

zbarbuto commented Feb 16, 2017

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.

@raymondfeng raymondfeng changed the title [PROJECT] Reduce the Excessive Ammount of Open Issues [PROJECT] Reduce the Excessive Amount of Open Issues Feb 17, 2017
@superkhau
Copy link
Contributor

@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.

@bajtos
Copy link
Member

bajtos commented Mar 1, 2017

@ghost ghost changed the title [PROJECT] Reduce the Excessive Amount of Open Issues void Apr 1, 2017
@ghost ghost closed this as completed Apr 1, 2017
This issue was closed.
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

No branches or pull requests

3 participants