source base organization and "Open Core"

weaveworks / weave-gitops-private

This is for tracking weaveworks internal information on weave-gitops. Will include issues, internal roadmaps, etc.

2 stars 4 forks source link

source base organization and "Open Core" #19

Open palemtnrider opened 3 years ago

palemtnrider commented 3 years ago

Do we merge into a single mono-repo? Have a repo for MCCP containing the UI and BFF? Do we create a UI repo (private?) containing all UI bits? Core, Team WS, MCCP?

What does open core mean for us?

palemtnrider commented 2 years ago

We are thinking 2 repos

weave-gitops
weave-gitops-enterprise

The enterprise build will pull in code from the core repo.

We will have 2 UIs - one built in core and one built in enterprise - with core pieces pulled into it.

palemtnrider commented 2 years ago

Need to writeup a ADR on this approach

palemtnrider commented 2 years ago

https://github.com/weaveworks/weave-gitops-private/pull/25

palemtnrider commented 2 years ago

Reviewed the ADR with the UI team. Outcome - the ADR will remain in a Proposal state while the UI team builds a POC to ensure we can effectively consume the wego core UI into the wego enterprise UI.