@crispyoz Thank you very much for your message. It is more clear now after also checking again and again the small details of GPL. Thanks again!
Best posts made by hc
Latest posts made by hc
RE: Developing Closed Product Based on Omega2
@Lazar-Demin @crispyoz Thank you very much! But I am a bit confused. I have also checked the GPLv2 license to get a bit more familiar as you already suggested.
My understanding is, if we are developing a software based on stack whose license is GPLv2 license (openWRT in this case), then we must publish it to somewhere which means it mush be open-source and publicly accessible.
But @crispyoz Your last post makes me a bit confused. You mentioned you have closed product because you did not change anything in openWRT.
Actually my plan is developing a closed product based on onion 2s+. But I am planning to disable ssh and also I will change the web interface which is used to configure the device.
To disable ssh and also o remove non-used modules, I am planning to rebuild the sources of onion omega. But sources are also based on openWRT.
In this case, what is my responsbility to onion.io & openWRT?
Should I make my new image publicly accessible?
Another question, I can also disable ssh and uhttpd in application. Then It will be a kind of application code. So, I guess I will not in change of publishing anything, correct?
Thanks again for details.
Developing Closed Product Based on Omega2
Not fully related to this topic but
Can I develop a closed product with your module by doing a few customizations in your firmware? e.g. domain, name / http server / and also some default applications in the customized firmware.
If yes, Should I follow any license of you? Any mark on the product regarding onion or any visualization on the user manual or http server about that I am powered by onion and/or openwrt etc?
If all is OK then what is your plan for the duration of availability? 2 years later, will still be producing this module?