A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
Looking for support?
Looking for a community?
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
Usually (A)GPL for my own, personal projects. I don't want my effort to be commercially successful elsewhere when I see nothing of it. Theoretically, it would still allow licensing to other parties if any show interest - although that never happened and I doubt it ever will.
Otherwise - I guess mostly when I work on other projects that are not personal / self-created - MIT or BSD. I generally don't have a problem with contributing permissively.
Depends on what I'm making and which ecosystem it will be a part of. For libraries, I use the MIT license most of the time, although I'm probably going to switch to Apache 2.0 for future stuff. It's a bit more robust and has a helpful licensing framework.
When I make applications (and if possible), I tend to use (A)GPLv3. GPL sometimes doesn't work though (for example, for my primary language, Clojure). I like the MPL 2.0 as a weak copyleft alternative.
However, recently, I've been reconsidering the whole open source/free software ideology, especially the focus on granting unconditional freedoms. I think the view that engineers shouldn't care what is done with their work is outdated and irresponsible, and it applies to software devs as well. So I'm keeping an eye on the development of alternative source models such as ethical source or licenses like the Anti-Capitalist License.
I've been considering copyfarleft licenses like the Anti-Captialist Licence and the Peer Production Licence for a while now; I like the licenses themselves, my only issue is that since there is no body like the FSF to enforce them, a company large enough is likely just to steal the code or break licence.
Yeah. I really like the idea of the ACL, but I wouldn't use it for anything serious right now because it hasn't undergone proper legal review and its enforceability itself is rather questionable. The author said he was going to work on getting that done this year, we'll see what happens.
To clarify, I also don't think the problem I've mentioned can be fixed with licenses alone and I still support FOSS in general. The fact that there's organisations like the SFC and FSF is a bonus, of course.
I'm still a student so I'm not exactly the target audience of this question, but still: It's either MIT or no license at all, because it's not like I'm going to enforce the license or something. People can do whatever they want with my code
No license at all means that no one can use it. Even if you aren't enforcing it the person who wants to use it doesn't know that.
I mean, that's not stopping people from copypasting or something, and, as I said, I'm not going to try to enforce it so I just don't bother
It definitely stops anyone who is at least a little bit serious about what they're doing.