22 ms·
IANAL, but AFAIK the GPLv3 has only the requirement that all software that is built upon the licenced software (and couldn't work without the licenced software)
by mattashii 9y ago
IANAL, but AFAIK the GPLv3 has only the requirement that all software that is built upon the licenced software (and couldn't work without the licenced software) musto be released under that license. Likely, your backend will be REST/GraphQL/some well-known alternative-enabled, meaning you could reasonably use [relevant request debugging tool] as the only endpoint for your APIs, which makes your backend loosely coupled to the frontend and therefore it does not have to be released under GPL. Maybe when your backend e.g. is going to send implementation-specific data for the frontend, it can be considered for a licence-lock. Again, IANAL, but this is what I think read while checking the GPL-FAQ
- btown 9y agoMy interpretation of Sencha's reading is that because the user-facing web application overall is built upon GPL software, and it requires the backend to function, the backend is part of that application, regardless of whether it has other merits. Again, IANAL but presumably Sencha hired some to advise that FAQ.
- mattashii 9y agothen they'd basically saying "because you depend on software X and our GPL-software, you need to make software X GPL as well. That probably won't hold in court.
- deleted 9y ago[deleted]