-
Notifications
You must be signed in to change notification settings - Fork 429
Description
Feature Description
This repo uses several packages from kcp-dev/kcp and hence requires importing it. This is however a nightmare from the maintenance standpoint because kcp is such a huge repository/dependency.
Proposed Solution
To make it easier to maintain this repo, we should check if it's possible to extract packages that are needed from this repo into a staging repository. This would make maintaining this project easier, but also would make it much easier to build external Virtual Workspaces.
We should only extract the framework and dynamic, concrete implementations of built-in Virtual Workspaces (e.g. APIExport, Replication...) should remain in the kcp repo and pkg/virtual. Packages that need to be extracted should ideally be extracted to the sdk repo and there should be no new dependencies in the SDK module.
There might be some other packages outside of pkg/virtual that are used and should be moved. contrib-filteredapiexport-vw can be used as an example what's needed outside pkg/virtual (e.g. search for "github.com/kcp-dev/kcp in the repo and check results).
Alternative Solutions
No response
Want to contribute?
- I would like to work on this issue.
Additional Context
No response