4 ms·

Links please, also it's literally FSF and OSI approved, how come you call it fake open source?

• dilyevsky 4y ago
  https://github.com/minio/minio/discussions/13571#discussioncomment-1583482 https://github.com/minio/minio/discussions/13571#discussionc... https://github.com/minio/minio/issues/13308#issuecomment-929254690 https://github.com/minio/minio/issues/13308#issuecomment-929... Lets just say they have a weird take on what constitutes agpl-compliant
  • phoronixrly 4y ago
    Seems like people misunderstanding the AGPL. (btw, I don't think this makes it fake open-source!)
    • dilyevsky 4y ago
      Actual agpl is legit open-source, projects that try to twist agpl into more restrictive license are not
  • jenadine 4y ago
    > the AGPL license requires that all software connecting with MinIO be 100% open source for you/your users Indeed, I don't think that's correct. That depends on the definition of "connecting" but I was under the impression that if you use MinIO on a server, the services that connects to MinIO don't need to be open-source. Only the server component that include MinIO need to be, and only if end users are connecting to that component. But correct me if I'm wrong.
    • dilyevsky 4y ago
      According to commonly understood agpl interpretation you’re correct but not as minio understands it: > Combining MinIO software as part of a larger software stack triggers your GNU AGPL v3 obligations. > The method of combining does not matter. When MinIO is linked to a larger software stack in any form, including statically, dynamically, pipes, or containerized and invoked remotely, the AGPL v3 applies to your use. What triggers the AGPL v3 obligations is the exchanging data between the larger stack and MinIO. https://min.io/compliance https://min.io/compliance