Has anyone got any experience in relicensing a codebase from MIT to AGPL?

Ideally, an actually real case of it, with any of the complications or niggles that might arise.

@nicksellen the way you asked the question implies there are specific things that are causing concern.

The answer can be anything from "single git commit is all" to "never legally possible" and it depends on a few factors (number/contactability/agreeability of authors being a major one).

Say more?

Follow

@Greg two separate cases actually:

with github.com/yunity/karrot-front we *might* be able to contact the authors, although now I look at the list, maybe not... lots of 1-time small contributors..

with github.com/FediHospEx/federate it's a fork of an MIT project, and could likely not contact all authors. would also like to be able to pull (MIT) changes from upstream.

as MIT is so permissive, I thought they might be options to just change it to AGPL, but maybe need to keep some reference to MIT too....

Β· Β· 1 Β· 2 Β· 1

@nicksellen @Greg the primary advantage of it being MIT is that you can get away with just leaving all the unowned pieces MIT and relicensing the rest.

Only way to remove the MIT license is to get all contributors to consent to the license change.

@rune @Greg thanks! my reply over here social.coop/@nicksellen/106556 has some follow-up questions... wondering how it works when wanting to make an AGPL change to an MIT file...

Sign in to participate in the conversation
social.coop

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!