Proposal: move most of the repos as subpackages to CLI

[Shurtu-gal]

Why do we need this improvement?

Currently the repos are too granular. We should bring them under a monorepo as subpackages to make stuff easier.

How will this change help?

• Easier maintainence.
• Faster changes
• Overall less overhead.

Subpackages

How could it be implemented/designed?

The following repos are planned for initial:

• server-api: Deprecate this repo server-api#576
• bundler
• diff
• optimizer

🚧 Breaking changes

Yes

👀 Have you checked for similar open issues?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue?

Yes I am willing to submit a PR!

[Shurtu-gal]

Need your thoughts on this @Amzani @Souvikns @AayushSaini101. Of course this will be a gradual process, starting with server-api.

cc: @derberg

[derberg]

go ahead - just sync with codeowners from diff, optimizer and bundler.

but I believe it will significantly make work easier, updates easier, and collab easier.

you will only have to update the CONTRIBUTING file to explain ownership. So you know, PR for optimizer, depends on owners of optimizer and they should not be blocked by other maintainers. Modelina have nice Champions setup, just ask @jonaslagoni what he thinks of it after all these years - and if it is a good fit here

[derberg]

When you work on a final PR to move a project inside CLI, I recommend approach that I take in generator, to use https://github.com/newren/git-filter-repo to move the code with all the history. Yes we squash, so history will not end up in master, but we at least get a history of commits on PR level as a reference + after merging the PR all the contributors form history will be reflected in the system. Example: asyncapi/generator#1626

[Shurtu-gal]

When you work on a final PR to move a project inside CLI, I recommend approach that I take in generator, to use https://github.com/newren/git-filter-repo to move the code with all the history. Yes we squash, so history will not end up in master, but we at least get a history of commits on PR level as a reference + after merging the PR all the contributors form history will be reflected in the system. Example: asyncapi/generator#1626

Sure, I had already started some initial migration of server-api will rewrite that.

[derberg]

yeah in case of server-api I would not be surprised if you actually rewrite it instead of migrating, but yeah, others like optimizer, diff, bundler definitely needs this approach