Right now we test against Minio and Ceph for non-AWS implementations of S3. We've found issues where Rusoto works with AWS S3 but not third party services. Example: https://github.com/rusoto/rusoto/issues/1463 .
Questions:
My opinion: due to time constraints for the entirely volunteer effort backing Rusoto, maintainers should treat these non-AWS services as a low priority. I'm comfortable with accepting PRs around making Rusoto work with them but not actively spending time improving non-AWS services.
Feedback and discussion welcome! 馃槃
IMHO, I would prefer a robust AWS-centric Rusoto that works well with Amazon at the expense of not being so compatible with third parties than a half baked, "please everyone" library that does not work as well.
Focus is important to attain quality, I think.
I added info to the root README in https://github.com/rusoto/rusoto/pull/1518 . 馃憤
Most helpful comment
IMHO, I would prefer a robust AWS-centric Rusoto that works well with Amazon at the expense of not being so compatible with third parties than a half baked, "please everyone" library that does not work as well.
Focus is important to attain quality, I think.