Programming

28,471 readers

3,327 active

153 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago

moderators

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Licenses are boring but you really need one! (distractedmind.home.blog)

submitted 1 year ago by snaggen@programming.dev to c/programming@programming.dev

29 comments fedilink hide all child comments

It seems people have a hard time understanding the implications of licenses, so I have written a something to help with that.

you are viewing a single comment's thread
view the rest of the comments

[–] Colloidal@programming.dev 1 point 1 year ago (2 children)

AGPL and GPL v3 are explicitly compatible, IIRC. You can run into some trouble with v2.

permalink

fedilink

source

parent

hideshow 2 child comments

[–] paperplane@lemmy.world 2 points 1 year ago (1 child)

What I mean is that you (IIUC) can't use an AGPL library in a GPL app without relicensing the whole thing to AGPL. For many larger projects relicensing is a huge hassle and often a non-starter if there aren't very good reasons for it.

permalink

fedilink

source

parent

hideshow 1 child comment

[–] Colloidal@programming.dev 1 point 1 year ago

You're right, the explicit permission is only the other way around.

permalink

fedilink

source

parent