Interesting case. Based upon the screenshots, it doesn't looking like they're trying to hide things though. Not like a typical fork and hide-via-rebrand. The web UI still shows Minio, and the CLI example shows the Minio copyright and link to the codebase repo.
I'd be interested to know if the "About" link in show shown WebUI screenshot goes to Minio or Weka. If it goes to Minio, could that be considered (combined with the minio branding) showing attribution? Has a Weka customer been rejected sources upon request for the AGPL works (Or been told they're soley using the apache code)?
There's also an interesting question of how the GPL/AGPL copyleft acts in this mode of distribution. From the screenshot, they're distributed in a single ZIP but the (potential AGPL) works appear to be in their own image. So does that act as separate networked applications, and therefore copyleft does not affect the other images (bit still with a requirement to share sources with the AGPL) or does that count as a single combined works?
The screenshots weren't of Weka's UI, but of Minio's after you manually extract those binaries. I'm not familiar with Weka, but it would be easy enough to stand up the Minio server and communicate internally over the S3 protocol, and never show any native Minio screens.
But it explicitly shows that it's using Minio when the application is actually used?
Sure, it's totally uncool to not mention Minio on their site and that's a massive shame but, as far as I'm aware, nothing in the license would require Weka to explicitly mention they're using Minio in their advertising/marketing like the provided link?
> Based upon the screenshots, it doesn't looking like they're trying to hide things though.
The screenshots are produced by manually mounting a squashfs, locating a minio binary and running it. It's not a very clear (and completely convincing) demonstration, and IMO could better have been left out.
I'd be interested to know if the "About" link in show shown WebUI screenshot goes to Minio or Weka. If it goes to Minio, could that be considered (combined with the minio branding) showing attribution? Has a Weka customer been rejected sources upon request for the AGPL works (Or been told they're soley using the apache code)?
There's also an interesting question of how the GPL/AGPL copyleft acts in this mode of distribution. From the screenshot, they're distributed in a single ZIP but the (potential AGPL) works appear to be in their own image. So does that act as separate networked applications, and therefore copyleft does not affect the other images (bit still with a requirement to share sources with the AGPL) or does that count as a single combined works?