Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

source base organization and "Open Core" #19

Open
palemtnrider opened this issue Jul 22, 2021 · 4 comments
Open

source base organization and "Open Core" #19

palemtnrider opened this issue Jul 22, 2021 · 4 comments
Labels
type/architecture Used for architecture items

Comments

@palemtnrider
Copy link
Contributor

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 palemtnrider added the type/architecture Used for architecture items label Jul 22, 2021
@palemtnrider
Copy link
Contributor Author

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
Copy link
Contributor Author

Need to writeup a ADR on this approach

@palemtnrider
Copy link
Contributor Author

#25

@palemtnrider palemtnrider self-assigned this Jul 27, 2021
@palemtnrider
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/architecture Used for architecture items
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@palemtnrider