add: gatsby-plugin-s3

[jariz]

Info

• Plugin Name: gatsby-plugin-s3
• Plugin Repository: https://github.com/jariz/gatsby-plugin-s3/
• Plugin NPM page: https://www.npmjs.com/package/gatsby-plugin-s3

Overview

Hi, I saw this repo and I think it quite fits with my situation.
I maintain gatsby-plugin-s3, the recommended way to deploy to S3 in the gatsby docs itself.
I've largely declared the project as 'done' as it has generally achieved all the goals I personally set out for it, however, there's still quite the backlog of additional features people would like to see.
Me and my co-maintainer have largely moved on from this project however.
People have suggested me to ask Gatsby itself to pick up the plugin, but because it is a direct concurrent of their own service, I very much doubt they're interested in picking it up. 😉

Tasks

Contributor Tasks:

• Move Repo to gatsby-uc
• Add moonmeister as a maintainer on your npm package.

Admin Tasks:

• Move Code into gatsby-uc/plugins repo
  • Update Readme in old repo to redirect folks to new location
  • Archive old Repo
  • Close any irrelevant PRs/Issues
  • Move/Comment on still applicable issues
• Update Plugin with best practices
• Publish new version

[moonmeister]

Hello! This is the perfect case for moving this here. Thanks for the contribution.

There's a couple things only you can do:

• Transfer the GitHub repo to this org. (GitHub wil automatically redirect folks with the old url)
• Add me (moonmeister) as a collaborator (write access) on the npm package and I'll give the gatsby-uc publisher's team access (for now it's just me).

https://docs.npmjs.com/adding-collaborators-to-private-packages-owned-by-a-user-account

I've sent you an invite to the NPM org and GitHub Org.

Finally, if you have time to open a PR for merging the plugin into this repo that'd be great, if not I should have time.

[moonmeister]

the one thing I don't know how to handle would be moving issues/PRs from the current repo. I'll take a look once the repo is over and see what can be done. I'm not against leaving it in it's own repo if that's better.

[jariz]

Hi, great!
I'll look into this somewhere today / tomorrow.
I'm fine with creating the PR myself.

[moonmeister]

Still hoping to get this done if you have time @jariz

[moonmeister]

Hey @jariz , I'll be talking at Gatsby Conf in March regarding the GUC and some of the cool plugins we are maintaining. I'd love for gatsby-plugin-s3 to be apart of that. Let me know if you have any questions. The two actions I need from you (moving the repo and giving me npm permissions) shouldn't take more than 5 minutes. Some time this week or next would be prefered. Thanks!

[YoshiWalsh]

Hi @moonmeister ,

Sorry for the lengthy delay on this one, my life has been busy recently. I tried transferring the repo and it said "You don’t have the permission to create public repositories on gatsby-uc". Could you please add me to the org?

Thanks,
Josh

[moonmeister]

@JoshuaWalsh Invite sent!

[YoshiWalsh]

I have transferred the repository and added you to the npm package. Regarding moving in to the monorepo, gatsby-plugin-s3 already has a monorepo structure (in order to house our test suite and example projects). How do you want to handle this? Should we nest our existing projects in a folder within the UC monorepo, or should we make all our projects top-level within the UC monorepo?

[moonmeister]

Thanks Josh. I'll see about getting this into the monorepo unless you are able to.

[moonmeister]

Oops, missed the questions you asked. We have a folder for full Gatsby sites that implement testing - integration-tests. If you have more unit testing those can go along side the plugin in its folder. As for examples, I think creating a top-level 'examples` folder would be fine.