You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 29, 2019. It is now read-only.
I was wondering : Since this project is deprecated do you envisage to MIT it ? That's way it will give the ability to loopback's developper (and more globally every developper) to use, modify and enhance this code.
I'm very confused with Strongloop/IBM open source approach. In one hand the documentation of open source projects like loopback-component-oauth2 refers to repo like this one about "how to implement it" but on the other hand, when looking at the code to have some ideas, we understood that we cannot reuse even part of the code.
Now that I saw this code, how can I be sure that the way I'll implement it myself will not imply breaking the law since it gives me some ideas ...
I'd like Stronloop team to know that I put so many interest in because I thought "Such an impressive way to deal with your vision of API, their lifecycle, the universality of code regardless the data source, of how can APIs interact with each others. That's the way I see the modern web which is lot of services of different companies, communicating, permanently looking for the more efficient way to enhance customer experience."
Strongloop did it.
But I feel not comfortable with the idea of an open source going straight to the river of a cloud services provider (missing the rain to close the (strong)loop :) ) even far the services they offer are great !
Joking aside, my simple questions are :
Do you envisage to change this license ?
If no, what can I do with this code sample and don't ?
Thank you for you answer
The text was updated successfully, but these errors were encountered:
Hi strongloop team !
I was wondering : Since this project is deprecated do you envisage to MIT it ? That's way it will give the ability to loopback's developper (and more globally every developper) to use, modify and enhance this code.
I'm very confused with Strongloop/IBM open source approach. In one hand the documentation of open source projects like loopback-component-oauth2 refers to repo like this one about "how to implement it" but on the other hand, when looking at the code to have some ideas, we understood that we cannot reuse even part of the code.
Now that I saw this code, how can I be sure that the way I'll implement it myself will not imply breaking the law since it gives me some ideas ...
I'd like Stronloop team to know that I put so many interest in because I thought "Such an impressive way to deal with your vision of API, their lifecycle, the universality of code regardless the data source, of how can APIs interact with each others. That's the way I see the modern web which is lot of services of different companies, communicating, permanently looking for the more efficient way to enhance customer experience."
Strongloop did it.
But I feel not comfortable with the idea of an open source going straight to the river of a cloud services provider (missing the rain to close the (strong)loop :) ) even far the services they offer are great !
Joking aside, my simple questions are :
Thank you for you answer
The text was updated successfully, but these errors were encountered: