[Spike] Investigate merging 2 repos

[katya-makarevich]

Outcome:

• options to merge 2 repos OSS and Enterprise described on high level
• approx. effort for each option with the strategy to execute
• pros/cons vs current scenario in terms of current engineering pain points and other business opportunities
• recommendation on whether to do it or not

Timebox:

• 3 days

[JamWils]

Also tackle #3003 in tandem with this spike.

[enekofb]

• licensing under entitlements
• clear integration points between OSS and EE and how this situation enhances

[enekofb]

@jpellizzari adding notes out of scoping conversation for q2 planning

[enekofb]

@LappleApple just mentioned in our product engineering roundtable that we could leverage her opensource strategy experience ... i thought it would be useful here!

[lasomethingsomething]

Heya, any news on this front? Do we have a timeline?

[jpellizzari]

@LappleApple No timeline, still doing fact-finding on the "why/if" we should do this.

[jpellizzari]

Things we will need to think about:

• How do releases work?
• How does installation work?
• How do we "move" things over gradually?
• How do we check entitlements securely?

On combining the UIs:

My recommended design would be to have multiple entry points, one for OSS, one for EE. It would look something like this:

https://github.com/jpellizzari/wego-repo-example/blob/d2a385572bd76bfef0fb8317aa1c0892a010c39e/ui/Core.tsx#L10

https://github.com/jpellizzari/wego-repo-example/blob/d2a385572bd76bfef0fb8317aa1c0892a010c39e/ui/Enterprise.tsx#L7

This would allow us to easily control which features show up. The backend logic would also be simple, as the backend server (nginx) would just need to decide which .html file to load. This would probably be done with different docker images at build time.