14
Open-source Licensing 101 - alavi.me (alavi.me)
submitted 3 months ago by to c/foss@beehaw.org
6 comments fedilink hide all child comments
 

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
[–] 6 points 3 months ago (2 children)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 2 points 3 months ago (1 child)

    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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 3 months 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.

  • permalink
  • fedilink
  • source
  • parent