|
It's generally considered to be the case that under the GPL providing a webservice based on opensource software does not constitute "distribution". This is why the AGPL exists - under the AGPL using software to provide a service does constitute distribution and thus requires you to provide the source code of software which links to AGPL-covered code to the users of your site. |
|||
|
|
Thank you Katrina, this is very helpful. |
|||
|
|
Any data that you create entirely yourself from scratch and serve using a lamp server is not bound by license and you get to decide the license(s) you want to use to distribute your data. You can use different licenses for different parts of the site. |
|||
|
|
Any code you write is yours. If you are modifying any GPL code then you have to release your code under GPL only. |
|||
|
|
GPL v2 it's just one kind of license you can use to distribute web services, it's not the only one as you see from other comments. |
|||
|
|
By the way, Apache, the actual HTTP server possibly accessed by clients of your web app, is not GPL, it's Apache License. That means you may use Apache source code to create proprietary software, with the restriction that you keep the Apache copyright notice and disclaimer. Furthermore, it's probably not right to modify Apache and to then try to license it as GPL--Apache has not determined that the Apache license is compatible with GPL, per se. |
|||
|
|
10
Answers
|
|
21
Answers
|
|
8
Answers
|
|
2
Answers
|
|
1
Answer
|
|
1
Answer
|
|
1
Answer
|
|
3
Answers
|
|
2
Answers
|
|
1
Answer
|
The Linux Foundation is a non-profit consortium dedicated to the growth of Linux.
Join / Linux Training / Board