Out of sync license message in the console

[dulacp]

IMHO the license message displayed in the console is not in sync with the license message displayed on your compliance page.

To be more specific, the section in the console under the section Making combined or derivative works of MinIO says:

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.

Whereas the public page on compliance under the very same section Making combined or derivative works of MinIO says:

Creating combined or derivative works of MinIO requires all such works to be released under the same license.

If MinIO source code is included in the same executable file, they are definitely combined in one program. If modules are designed to run linked together in a shared address space, that almost surely means combining them into one program.

By contrast, pipes, sockets, RESTful APIs, and command-line arguments are communication mechanisms normally used between two separate programs. So when they are used for communication, the modules normally are separate programs. But if the semantics of the communication are intimate enough, exchanging complex internal data structures, that too could be a basis to consider the two parts as combined into a larger program.

Merely aggregating MinIO software into your distribution does not constitute derivative works. For more information, please refer to the GPL FAQ.

The public min.io/compliance page would logically be the source of truth. Can you confirm that?

Best regards,
Pierre

[cniackz]

Thank you @jinapurapu for helping me with this issue