Thanks for the feedback everyone, the ExAws v2.0 changes are in progress, and I hope to release soon!
At the core of this change is the hope that some of you out there who find a specific AWS service central to what you do can step up and take ownership of that service within ExAws. If you think you are such person, please let me know.
Although general contributions from anyone at any skill level are welcome, and the ExAws code is rather uncomplicated, service maintainers should have enough familiarity with Elixir to promote good coding practices.
Maintainers are NOT required to expand on or otherwise singlehandedly complete the service. The main duty is just being familiar with the AWS reference API docs, and handling issues / PRs. Improved test coverage would be nice if you’re inclined.
I will always be around to answer questions.
Available Services
Some services have clear original contributors, and those people get right of first refusal on the service projects. These projects are available for any who are interested, so please message me privately if that’s you!
- ex_aws_dynamo
- ex_aws_firehose
- ex_aws_kinesis
- ex_aws_lambda
- ex_aws_sns
More may become available as I hear back from those I’ve pinged for some of the other services. I’ll keep this thread updated.
Thank you everyone for your support!
