-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stay with GPLv3? #1
Comments
I love GPL and copyleft. But for tools that we want lots of people to pick up, I do tend to go with MIT or perhaps Apache, to avoid complications for anyone. |
I've gone back and forth on strong copyleft (e.g. GPLv2, GPLv3, AGPLv3) and very permissive (e.g. MIT, various BSD) over the years. I've thought about switching to AGPLv3, because if some mooch takes my code, builds their interactive website with it (maybe making a few private tweaks to my code), and doesn't bother to acknowledge my work or even contact me in any way, I want that decision to be complicated for them. My goal with this tool is to facilitate conversations about interoperability with the ABIF format. My hope is that people will want the ABIF format itself to be stable (and to serve as an API to their software). Over time, I'm hoping that add many more input and output formats to this tool (and I'm hoping to get help doing so). If I have to change the license to get the help, I'm willing to do that, but I kinda need someone who offers "consideration" (to use lawyer speak) in some way. I'm a cheap date, so "consideration" in my book could be a promise to integrate my code into their published code that has much greater notability than my code (in a way that doesn't cut me out of the loop). |
Well put. I think AGPLv3 is a better choice than GPL since web sites are the sort of thing people want for format conversions. And you can make it clear that you're very willing to dual-license for proper consideration if they're worried about AGPL and the rest of their web site. |
I'm choosing AGPL3.0 per rationale provided at electorama/abiftool#1 . In short, I think I want a "no moochers" license for this.
My work over the past week has been a mish-mash of all sorts of cleanup and debugging, and I got exhausted. The previous version did a better job of handling weird characters inside of square brackets or inside of double quotes, but this version fails with a candidate token of "[Doña #1]" or "Steve #1" or whatever. One of these days, I'll fix that problem, but not today.
I haven't fully decided on the following on what the long-term license for abiftool.py will be. It's currently licensed under GPLv3), but as of this writing (in August 2023), I can probably be convinced to switch to an MIT, BSD, or Apache license of some sort. As other contributors contribute under GPLv3, it will become more difficult me to convince other contributors to change license. Stay with GPLv3, or change now while I can?
The text was updated successfully, but these errors were encountered: