Hiya Ben,

Since I’m already a committer on ExAws.SNS and a heavy user of several other service modules, I would definitely be interested in seeing what my team and I can to support ExAws as well. We’re heavily committed to open source and always looking for ways to contribute back, and this might be a good fit for us.

That includes one or more of us taking on the role of Maintainer if we can swing it, but it would help to have some idea of the number/frequency of pull requests, issues, support needs, etc. so that I can make a case to my supervisor(s) that it would be a worthwhile thing for us to devote some time to.

I’m really pleased to see you reaching out to the community to ask for help. This is a huge project that a lot of companies rely on, I’m sure you’ll get somebody stepping up.

I’ll be linking this to a couple people.

Hey everyone.

I really do appreciate the outpouring of support. If all that was needed to move forward with the library was willing and helpful people then the project would be in great hands.

However what the community really needs is someone who has the time and vision to re-imagine how to do an AWS client from the ground up. ExAws’s approach places far too high a burden on maintainers to keep everything up to date.

CargoSense has officially moved off of AWS to GCP, which seems like the right time to declare what is already true: ExAws is deprecated and will not receive further updates.

https://github.com/ex-aws/ex_aws#deprecation-notice

Thanks to all of you who have put time and effort into it over the years. I’m sure the next library will benefit from that same interest and passion.