11
submitted 1 month ago* (last edited 1 month ago) by somegeek@programming.dev to c/foss@beehaw.org

The basics about types of open-source software licenses, their differences, how to choose a license etc.

you are viewing a single comment's thread
view the rest of the comments
[-] TehPers@beehaw.org 5 points 1 month ago

We've managed to convince our workplace to allow us to use MIT on a few projects. We mainly share that code directly with customers, and it's easier to do that with permissively licensed code, plus we can make it public for an extra win (both at work and for the community).

There are definitely good uses for permissive licenses. In the same way that you should consider not using one, you should also consider whether one meets your specific needs.

[-] somegeek@programming.dev 1 points 1 month ago

Exactly. Everything has it's place.

Can I ask, what do you mean by "share code with out customers"? They modify this code? They only use this code? How are the dynamics?

[-] TehPers@beehaw.org 4 points 1 month ago

We are somewhat similar to contractors and directly help our customers write their code. Usually this means bringing in some kind of starting template, and it's easier to do this with a permissively licensed template than make them sign another legal agreement.

They own the code once we're done, and they don't need to make it open source (companies naturally don't like to open source their products). Our templates are open source and well-documented, though.

this post was submitted on 09 Aug 2026
11 points (82.4% liked)

Free and Open Source Software

22903 readers
43 users here now

If it's free and open source and it's also software, it can be discussed here. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 4 years ago
MODERATORS