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
Part of my doubt is that I would like people to be able to build and sell devices based on this library.
I see GPLv2 as an obstacle for that.
Still I consider to publish the same initial code under GPLv2 for a true open source community
Please indicate if there are people in favour of that and would prefer to deliver their attributions to the GPLv2 distribution over the Apache2 distribution.
TIA,
HacK
The text was updated successfully, but these errors were encountered:
I guess this is up to you. If you don't mind about others writing proprietary code with your library, Apache, BSD or LGPL -like licenses is what you need, and they'll most likely facilitate adoption and traction of your project. If that is a problem, then GPL is the best option IMHO.
Part of my doubt is that I would like people to be able to build and sell devices based on this library.
I see GPLv2 as an obstacle for that.
Still I consider to publish the same initial code under GPLv2 for a true open source community
Please indicate if there are people in favour of that and would prefer to deliver their attributions to the GPLv2 distribution over the Apache2 distribution.
TIA,
HacK
The text was updated successfully, but these errors were encountered: