4 ms·

Didn't know that MinIO used to be Apache licensed. This [0] is the commit that changed it. Since the S3 API largely remained the same over the last two years,

by nikeee 4y ago

Didn't know that MinIO used to be Apache licensed. This [0] is the commit that changed it. Since the S3 API largely remained the same over the last two years, it might be an option to use the Apache version, if AGPL is not possible. Of course, that would lack security fixes that were done in the meantime. There is also a discussion [1] about that license change. [0]: https://github.com/minio/minio/commit/069432566fcfac1f1053677cc925ddafd750730a https://github.com/minio/minio/commit/069432566fcfac1f105367... [1]: https://github.com/minio/minio/issues/12143 https://github.com/minio/minio/issues/12143

phoronixrly 4y ago
I hope more people start using AGPL from the get-go for their projects.
- wmf 4y ago
  Companies are using AGPL not to benefit users or the community but to extort users and competitors into paying them. It's becoming fake open source.
  - phoronixrly 4y ago
    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
  - jenadine 4y ago
    They're not extorting anyone. Or is anyone having paid product "extorting" their customer? AGPL is true open source.
- tensor 4y ago
  If you are in the business of making money like minio, you may as well just use a commercial license. No business will touch AGPL, they will just opt to pay for a commercial license.
  - deleted 4y ago
    [deleted]
  - jenadine 4y ago
    > No business will touch AGPL That's not true, I am in contact with many business using AGPL software. (Not Minio specifically) Some businesses choose not to touch it, but that's their losses.
  - phoronixrly 4y ago
    In fact, I am starting to ask myself the opposite... 'Since project X is MIT-licensed, do they need my contribution at all? Probably not, their license probably brings them many high-quality corporate contributions.'
    - mrtweetyhack 4y ago
      Except these "high-quality corporate contributions" are kept to themselves for corporate reasons.
  - akvadrako 4y ago
    That's kinda why the AGPL is good; it lets non-businesses and open-source companies use it and encourages closed companies to purchase a license.
    - dilyevsky 4y ago
      It’s not good bc it ties survivability of a project with a single company. If company folds so does your open-source project. Also imagine if linux wouldn’t be able to receive contributions from google and other big tech

by nikeee 4y ago

phoronixrly 4y ago

I hope more people start using AGPL from the get-go for their projects.

wmf 4y ago
Companies are using AGPL not to benefit users or the community but to extort users and competitors into paying them. It's becoming fake open source.
- phoronixrly 4y ago
  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
- jenadine 4y ago
  They're not extorting anyone. Or is anyone having paid product "extorting" their customer? AGPL is true open source.
tensor 4y ago
If you are in the business of making money like minio, you may as well just use a commercial license. No business will touch AGPL, they will just opt to pay for a commercial license.
- deleted 4y ago
  [deleted]
- jenadine 4y ago
  > No business will touch AGPL That's not true, I am in contact with many business using AGPL software. (Not Minio specifically) Some businesses choose not to touch it, but that's their losses.
- phoronixrly 4y ago
  In fact, I am starting to ask myself the opposite... 'Since project X is MIT-licensed, do they need my contribution at all? Probably not, their license probably brings them many high-quality corporate contributions.'
  - mrtweetyhack 4y ago
    Except these "high-quality corporate contributions" are kept to themselves for corporate reasons.
- akvadrako 4y ago
  That's kinda why the AGPL is good; it lets non-businesses and open-source companies use it and encourages closed companies to purchase a license.
  - dilyevsky 4y ago
    It’s not good bc it ties survivability of a project with a single company. If company folds so does your open-source project. Also imagine if linux wouldn’t be able to receive contributions from google and other big tech