Very strict licensing requirements? #315

New issue

Closed

opened 2025-10-14 16:49:24 -06:00 by navan · 0 comments

navan commented

2025-10-14 16:49:24 -06:00

Owner

Originally created by @mkhalila on 8/3/2017

So I've used this guide to implement an email feature on simple static website for one of my clients and I've not yet finished the entire website yet, but the license for this feature is GPL 2.0. Which requires release the source code of my entire website to the public and to make my project GPL 2.0 too. This sort of kills off the whole benefit of "not having to use a third party for sending emails"? Since it's not practical for this to be used for any purpose other than where full disclosure of source code is an okay thing to do.

Am I missing the point here, or is the above correct? In which case I'll remove the code from the website. I mean I really don't want to do that, because I really appreciate the work that's gone into this. But I feel that GPL is a very strong license to use, for what is essentially a REST-based API hosted on google's servers + (an option js file for sending without redirect) that takes in data (as JSON?), and formats it and sends it through google's mail server.

*Originally created by @mkhalila on 8/3/2017* So I've used this guide to implement an email feature on simple static website for one of my clients and I've not yet finished the entire website yet, but the license for this feature is GPL 2.0. Which requires release the source code of my entire website to the public and to make my project GPL 2.0 too. This sort of kills off the whole benefit of "not having to use a third party for sending emails"? Since it's not practical for this to be used for any purpose other than where full disclosure of source code is an okay thing to do. Am I missing the point here, or is the above correct? In which case I'll remove the code from the website. I mean I really don't want to do that, because I really appreciate the work that's gone into this. But I feel that GPL is a very strong license to use, for what is essentially a REST-based API hosted on google's servers + (an option js file for sending without redirect) that takes in data (as JSON?), and formats it and sends it through google's mail server.