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

[Discussion] Extensions contributed by the community #5076

Closed
dhmlau opened this issue Apr 9, 2020 · 3 comments
Closed

[Discussion] Extensions contributed by the community #5076

dhmlau opened this issue Apr 9, 2020 · 3 comments

Comments

@dhmlau
Copy link
Member

dhmlau commented Apr 9, 2020

Originated from #3047 (comment).

Cross posting #3047 (comment) from by @ckoliber

I want to add more extensions:

loopback-history-extension: For adding history feature to models
loopback-acl-extension: A generalized base application with User, Role, Permission models and controllers with an advanced controller generator supports model relations and access controlling
And now i'm trying to implement loopback-connector-processmaker

Please give me the required access to create these projects in strongloop organization

Things to discuss

  1. For extensions contributed by the community, where would be a good location? the contributor's github org, strongloop-community, etc? The good thing to leave them in the contributor's org is that they can get the credits for creating/maintaining them. Also, the community is free to create any extensions any time, so it is not necessary to put it in the strongloop org.

  2. With an increasing number of extensions created by the core maintains and community, it might make sense to have an "Extensions" page similar to the Example page. If someone wants to share an extension with the community, they can submit a PR to add it on the extension page.

Would like to hear inputs from @ckoliber @strongloop/loopback-maintainers. Thanks!

@mhmnemati
Copy link

Thanks @dhmlau

Self GH organization is a good choice, but as we know, open source projects will grow up faster by community contributors help,
I thing keeping these types of extensions in a centralized origanization can help to finding them by community more easier

@achrinza
Copy link
Member

We already have a LoopBack community projects page. Though it’s quite hidden and it’s not LoopBack 4-specific.

So we probably want to create a separate page for LoopBack 4 community projects and then link to it.

@dhmlau
Copy link
Member Author

dhmlau commented Jul 16, 2020

Fixed via PR #5707.

@dhmlau dhmlau closed this as completed Jul 16, 2020
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

3 participants