Sponsor and repository management

[Eomm]

Prerequisites

• [x] I have written a descriptive issue title
• [x] I have searched existing issues to ensure the issue has not already been raised

Issue

I think the readme on this repo should be a bit cleaned up:

• the book could be added at https://fastify.dev/resources/#books
• the sponsor is not sponsoring the fastify org, so why is it there?
• I can see direct commit on dev (aka main) without a PR, if there is a team working on this repo, we should avoid that. If this is a one dev project we need at least to open a PR so we can get a notification and contribute to it
• Since it is a monorepo and it is the only repo in the org with this shape, I can't see any guideline on how to release it

At this time, I don't feel like I can publish a release here since dev branch was not stable until a week ago.

We should improve this repo in order to welcome other fastify collaborator to join it in the natural module lifecycle.

[galvez]

Thanks Manuel, this repo has indeed needed more structure and organization for some time now.

• I've opened a PR to fastify/website to add the book — good call :)
• Feature.fm is my employer and has sponsored this project specifically — what's the recommendation in this case?
• I'm changing the default branch to main — would like to continue exercising push freedom to dev directly, with PRs only being required when merging into main, does that make sense?
• It needs to be a monorepo for ease of testing — @fastify/vue and @fastify/react are renderer packages to @fastify/vite, so it's important to have quick access to the development version of @fastify/vite when developing.

Should we consider perhaps making this a reference for monorepos across the org, if they're ever needed elsewhere?

I'll update the README also!

Again, thanks for looking into this — and very eager to have you as a contributor to this project!

[Eomm]

what's the recommendation in this case?

This is a gray zone 😄

1. You may add them here: https://fastify.dev/organizations/#collaborators-organizations
2. ATM we list paying sponsors on this page https://github.com/fastify/fastify/blob/main/SPONSORS.md
3. BUT we have "legacy" sponsors (example) that used to provide developers time instead of money, so I think we are in this use case. So LGTM so far. Thanks for clarifying it

does that make sense?

That would be perfect - my main point is that we need a guideline or a dummy command to be sure that whoever in the plugin team could ship these modules if needed.

Should we consider perhaps making this a reference for monorepos across the org, if they're ever needed elsewhere?

Definitely. Maybe it was just not clear for me, but if we have some guidelines we can refer to them whenever needed!

[onlywei]

@galvez Let's add Changesets to this repo. Who do I request the ability to make releases from?