immich.app

avidamoeba , to Selfhosted in The Immich core team goes full-time | Immich
@avidamoeba@lemmy.ca avatar

Will the license change?

No. Immich will continue to be licensed under AGPL without a CLA.

SomeBoyo ,

good

potatopotato ,

I hate that it needs to be said but love that they said it so plainly

ScreaminOctopus ,

Isn't a huge part of the point of copy left licences that an author can't change the license without rewriting the code entirely?

CriticalMiss ,

For the license to be changed every team member needs to submit a written agreement that he agrees to the change, otherwise their contributions must be removed as they were written under a different license, the only exception is usually permissive licenses such as MIT/BSD 3 clause.

Usually, to rugpull FOSS contributors, companies who maintain FOSS software ask contributors to sign a CLA which waives their rights and lets the control their contributions. Immich isn’t doing any of that, and it will likely remain AGPL forever because changing the license will be a big hassle for them with the amount of contributors.

ALostInquirer ,

What's a CLA?

avidamoeba ,
@avidamoeba@lemmy.ca avatar

Contribution/contributor license agreement. It's a document that transfers the copyright from the original author - developer submitting a patch or PR - to the project owner, e.g. FUTO. If FUTO required CLA for all Immich contributions, then FUTO would own the copyright for all the source code of Immich. This allows FUTO to relicense Immich under a different license, other than GPL, for whatever purpose, without asking anyone. For example they could make modified Immich versions for sale, or sell the Immich source code to third parties under EULA or any other license. Without a CLA, FUTO would have to get written agreement from every Immich source code contributor to change the Immich license, which would happen in 2000 and never, at least not without ponying up cash.

Norgur , to Selfhosted in Immich is awesome

Noticed it stopped working yesterday, wasnt at home so I couldn't really get into it, just checked the docker logs via portainer on the go and was like "wtf is this error?!" Was relieved when I learned what the issue was and that it's just a restructuring of the containers.

While it can be unnerving that they don't shy away from breaking things in order to improve the service, it's actually a very good thing and keeps the app from getting bogged down in some "but backwards compatibility"legacy code hell (wonder what some people in Redmond would know about that). Let's just hope that they never publish an update that permanently breaks things when you haven't followed a very strict weird update procedure or something.

Discover5164 ,

you should exclude the immich stack from auto-updating and subscribe to immich releases.

most of the time will just be a docker compose pull && docker compose up -d && docker compose logs -f

Ramenator ,

And for the love of god don't go for latest, just stick to the release tags

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • kbinchat
  • All magazines
    •