Now Red/Core and Red/View are in the same repository (red/red). Each of them is a big project, they should be in different repository.
We attampted to split view into a standalone repo by making it a git module before. It did not work well. The view module integrates with the runtime so tightly. They are interdependent. While a git module works well only if it's one-way dependency.
Here I propose a new way to sperate it.
Simply fork red/red into a new repo red/view. ;-)
All the changes/issues related to red/core happens in red/red.
All the changes/issues related to red/view happens in red/view.
Merge or cherry-pick commits between those two repos regularly or when needed.
This gives us the following benefits.
Make it easier to have two teams to work on red/core and red/view.
Now Red/Core and Red/View are in the same repository (red/red). Each of them is a big project, they should be in different repository.
We attampted to split
view
into a standalone repo by making it a git module before. It did not work well. The view module integrates with the runtime so tightly. They are interdependent. While a git module works well only if it's one-way dependency.Here I propose a new way to sperate it.
red/red
into a new repored/view
. ;-)This gives us the following benefits.