Adding gatsby-plugin-s3 although I'm not the maintainer #377
Replies: 3 comments 5 replies
-
Hey @davidrhoderick! Yeah, I would love to see that happen. @jariz opened an issue a while back to do this but went silent. Ideally we'd get the repo and npm package from them but if not we can discuss options. I'll try reaching out again when I get sometime and see if I can get their attention to get this done. Thanks for bringing this up! |
Beta Was this translation helpful? Give feedback.
-
I'm going to try one last hail mary to get in touch with @jariz and if it fails we can move forward with forking and publishing under a new name. |
Beta Was this translation helpful? Give feedback.
-
Hi @moonmeister, I've transferred the project over to @joshuawalsh, a long time collaborator on the project, and personally do not maintain it anymore. |
Beta Was this translation helpful? Give feedback.
-
If you look up how to to deploy a Gatsby project to an AWS S3 bucket, you'll get this page, which points you in the direction of
gatsby-plugin-s3
. However, it looks as if this plugin is no longer maintained as I've pointed out here. Based on the discussion I started in the gatsby repo, I was suggested to add it here, and I think it would make a lot of sense to if it's part of the official documentation.However, I am not the maintainer of this plugin. I only just tried today to get involved in contributing without success and there haven't been any responses to issues in that repo in at least 6 months (and that response was to say that an issue was duplicated).
How could we revive this plugin and bring it into
gatsby-uc
? Should we fork it here? How would we go about the npm package? Should we rename it?Beta Was this translation helpful? Give feedback.
All reactions