-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New maintainer or at least contributor #278
Comments
@aristidb is seeking a new maintainer for aws, per this tweet: |
My own interest in aws is limited to the S3 part of it so I would not want to take over full maintenance, but I would be willing to be part of a team of maintainers. At the moment, there is a pressing need for a release fixing #275. Both as a potential security fix and to support use with recent stackage. @aristidb if you granted me write access I'd use it responsibly.. |
@jwiegley is listed as a co-maintainer, but has certainly not been active in a long time on aws. Are you still co-maintaining? |
@joeyh Sent you an invite to be "Collaborator", which I think should give you the write access you need. |
Thank you @aristidb. I still can't upload aws to hackage, but I'll worry about that once I've gotten a release together. |
I tried adding you as a Hackage maintainer on the web interface now, maybe that helps with that. |
Thank you @aristidb! I have now released 0.22.1 to hackage. |
@joeyh No, I'm not longer working on this project. You can remove me as a maintainer. |
Hi!
I’m interested in helping here. I have some work experience with AWS and have some knowledge of Haskell through side projects. I don’t have a lot of time either but I do have interest in helping this package.
The text was updated successfully, but these errors were encountered: