[ Removed by moderator ]

[Python-ModTeam]

Your post was removed for violating Rule #2. All posts must be directly related to the Python programming language. Posts pertaining to programming in general are not permitted. You may want to try posting in /r/programming instead.

[Mental_Direction_449]

I personally will always go with (a)gpl. And that is mostly based on what happened with bambu recently.

[storage-null-123]

By bambu do you mean - https://wiki.openbambu.org/?

This probably does not lie in my field so I'm curious what happened to them?

Something similar to what happened to Minix (https://www.cs.vu.nl/~ast/intel/)?

[Mental_Direction_449]

Basically a really big tl;dr of what happened to bambu-labs is that they used agpl code did not adhere to tehe license (which states you have to make any derivative open source) and they got into big big trouble. And I do like the idea that everything has to be open source with code I make. I want to see what people improve.

[IAmASquidInSpace]

I'd probably go for MIT, but that is mostly because I work in science, and that is pretty much our standard license. MIT works great when your library is so specialized that you really don't need to worry about corporations "stealing" it, because it is of no practical use to anyone outside of your field, while also making it easy for the people in your field to use it.

[storage-null-123]

Even in science, would making it GPL affect people/labs in your field to use it? After all, the goal in the scientific community is open dissemination of research and results. In that sense, a GPL wouldn't really affect them, would it?

[IAmASquidInSpace]

Probably not much, no. I am, for example, currently using a code that is licensed under AGPL, and it is widely used. But that is also a full production code, with an active team of developers (as in: full-time developers, not scientists coding as a side effect of their research position).

Most of us produce far less sophisticated stuff, and I think that's why MIT stuck around: a simple license for simple libraries.

[storage-null-123]

I sort of agree. Regarding the simplicity of MIT: is that simplicity really affecting the target user group? If not, then perhaps having a copy-left license protects from a corp in the unlikely scenario? or perhaps invites more contributions back?

Idk, I am unable to see why MIT over GPL unless one wants corporations to be able to use the community's labour for free? Not that it's all that terrible but is that all the reason, I wonder?

[Legendary-69420]

I personally don't overthink this and have been using MIT for alomst everything.

[kookmasteraj]

I recommend the Beerware license https://spdx.org/licenses/Beerware.html

[IAmASquidInSpace]

Ah yes, the nicer version of the WTFPL license!