Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MinIO is now in maintenance-mode

github.com

Post reply on HN
Print view View original

141–150 of 338 posts

Re: MinIO is now in maintenance-mode

#141

Post by christina97 »

candiddevmike wrote: post #72
tlarkworthy wrote: post #45

Earlier quoted context omitted.

? Its like GET /object, PUT /object. To me its the most obvious mapping of HTTP to immutable object key value storage you could imagine. It is bad that the control plane responses can be malformed XML (e.g keys are not escaped right if you put XML control characters in object paths) but that can be forgiven as an oversight. Its not perfect but I don't think its a strange API at all.

Everything uses poorly documented, sometimes inconsistent HTTP headers that read like afterthoughts/tech debt. An S3 standard implementation has to have amazon branding all over it (x-amz) which is gross.

I mean… it’s straight up an Amazon product, not like it’s an IETF standard or something.

Re: MinIO is now in maintenance-mode

#142

Post by [deleted] »

nikeee wrote: post #137
st3fan wrote: post #60

What a story. EOL the open source foundation of your commercial product, to which many people contributed, to turn it into a closed source "A-Ff*ing-I Store" .. seriously what the ...

Didn't contribute to MinIO, but if they accepted external contributions without making them sign a CLA, they cannot change the license without asking every external contributor for consent to the license change. As it is AGPL, they still have to provide the source code somewhere. IANAL, of course

[deleted]

Re: MinIO is now in maintenance-mode

#144

Post by maxloh »

cantagi wrote: post #33

They have been removing features from the open source version for a while. The closest alternative seems to be RustFS. Has anyone tried it? I was waiting until they support site replication before switching.

Although promising, RustFS is a Chinese product. This would be a non-starter for many.

Re: MinIO is now in maintenance-mode

#145

Post by drob518 »

candiddevmike wrote: post #72
tlarkworthy wrote: post #45

Earlier quoted context omitted.

? Its like GET /object, PUT /object. To me its the most obvious mapping of HTTP to immutable object key value storage you could imagine. It is bad that the control plane responses can be malformed XML (e.g keys are not escaped right if you put XML control characters in object paths) but that can be forgiven as an oversight. Its not perfect but I don't think its a strange API at all.

Everything uses poorly documented, sometimes inconsistent HTTP headers that read like afterthoughts/tech debt. An S3 standard implementation has to have amazon branding all over it (x-amz) which is gross.

I suspect they learned a lot over the years and the API shows the scars. In their defense, they did go first.

Re: MinIO is now in maintenance-mode

#146

Post by kragen »

roblabla wrote: post #129
kragen wrote: post #115

Earlier quoted context omitted.

Yes, it is. Although https://www.gnu.org/licenses/agpl-3.0.html says > All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. it also says > You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically termin…

> I don't think a GPL violation case has yet been litigated. It has, though it has mainly been under the "breach of contract" approach and not under "copyright infringement" approach. See https://en.wikipedia.org/wiki/Open_source_license_litigation

Of course you're correct. I meant to say no GPL termination case, and I've corrected my comment to say that. By that I mean cases where the defendant had cured their breach of the GPL but continued exercising the rights the GPL would have given them but for the termination clause.

Re: MinIO is now in maintenance-mode

#147

Post by kragen »

mbreese wrote: post #139
kragen wrote: post #110

Earlier quoted context omitted.

> AGPL also doesn't necessarily mean you have to make the code publicly available, just available to those that you give the program to (I'm assuming AGPL is like the GPL in this regard). This is the crucial difference between the AGPL and the GPL: the AGPL requires you to make the code available to users for whom you run the code, as well as users you give the program to.

But, for minio, the users aren't the public... the users are their enterprise customers (now). So, to fulfill the AGPL, they'd have to give the code to their users, but that doesn't necessarily mean to the public at large (via GitHub). But, what I don't know is -- is there any other AGPL code that minio doesn't own, but that was otherwise contributed to minio? Because, presumably, they aren't actually giving their cu…

I agree with all of that.

Re: MinIO is now in maintenance-mode

#148

Post by lima »

gethly wrote: post #132

There is https://github.com/seaweedfs/seaweedfs I haver not used it but will be likely a good minio alternative for people who want to run a server and don't use minio just as s3 client.

Is it stable now? Last time I checked, the amount of correctness bugs being fixed in the Git history wasn't very confidence-inspiring.
Post reply on HN