Accepting Plugins

[moonmeister]

I think almost any plugin that wants to be moved into the GUC should be accepted. Saying no should be an exception. Here's a rough idea of the process may look like.

Process:

• Package Author
  • Move current repo to gatsby-uc org
  • Move npm package owndership to gatsby-uc
• GUC Admin/Maintainer
  • Accept Repo transfer and give Admin access
  • move code into plugins repo, making sure it conforms to any best practices in the community, setting up any configs for testing and publishing, and opening a PR to merge all this.
  • open PR on old repo readme to notify of location change and remove any automation there
  • Review and Merge
  • Archive old repo

Why use a monorepo?

Benefits

I want some input here. On one hand a single package in it's own repo would simplify npm deployments. But if we ever change a process we'd have to update and merge configs and process across multiple repos. As the community grows it'll be much better to have a central repo where everything is managed. I really don't want to be working across 10 repos if I need to update a peer dep or something else simple...I'd rather just work on one repo.

drawbacks

• Abandoning the old repo. This is an initial effort but I don't see a long term issue here. We can have a README template for those old repos that notifies anyone arriving there of the changes. Additionally, the repo can be archived to prevent interaction there.
• Publishing: this maybe not be an issue, just my ignorance. but I imaging configuring automated releases in CI might be simpler on 1 repo = 1 package. This doesn't seem insurmountable by any means...I just don't know what it'll look like yet.

[moonmeister]

Transferring npm ownership is interesting at first. You go to the team you want to give permissions to, "Packages", enter package name, "Add existing package". Not sure what this looks like if you don't own the package. 🤔