Skip to content
loading...

re: Which licence do you use for your open source projects? VIEW POST

FULL DISCUSSION
 

I tend to prefer Apache 2 as I would like attribution as well as protection from liability.

AGPL or GPL3.0 make businesses nervous. Like not even allow you to download it sometimes (if they don't have decent lawyers)!

That gets in the way of people adopting it, as businesses don't want to accidentally open source their secrets. It totally makes sense for something like dev.to to use AGPL but might prevent adoption for libraries that could be hidden away behind the scenes.

 

I don´t get why AGPL or GPLv3 could make them not allow to download software. Or I don't fully understood the license (i think the last is more feasible hahaha)

It totally makes sense for something like dev.to to use AGPL but might prevent adoption for libraries that could be hidden away behind the scenes.

I think, in that cases, that one could just talk to the developer and try luck. If they deny you the open-sourcing, you could use an alternative. There are always many!

Thanks for your reply!

 

The problem is the AGPL and GPL3 force you to make your code available to anyone that consumes that service, whether that's a website or and API. This applies even if you're just using a library this license.

To mitigate this this risk, it's easier for companies to just not use AGPL or GPL3 open source products at all.

code of conduct - report abuse