search

weaveworks / weave-gitops-private

This is for tracking weaveworks internal information on weave-gitops. Will include issues, internal roadmaps, etc.
2 stars 3 forks source link

ADR - create enterprise version of tf-controller #97

Closed chanwit closed 1 year ago

chanwit commented 1 year ago

This PR introduces an ADR for creating the enterprise version of TF-controller.

chanwit commented 1 year ago

cc @makkes

chanwit commented 1 year ago

Thanky you @enekofb

From the business perspective, it would be better for us as a company to start the enterprise version as a closed source. We would decide to open-sourcing it later when needed. What do you think @JamWils ?

makkes commented 1 year ago

From the business perspective, it would be better for us as a company to start the enterprise version as a closed source

I'm not sure I necessarily agree with this sentiment. Not revealing the source code doesn't automatically make it a hot seller and can even hurt adoption. But let's hear James' opinion on this.

JamWils commented 1 year ago

Alright,

Thank you everyone for your input and patience on this topic. I've been chatting to various folks and working on aligning our expectations.

I apologize as I have been not disentangling public vs private code alongside licensing. As I have been saying "let's make this repo OSS", I've really been saying "let's make this repo public, but put a strict license on it".

Right now, I think we need to make some features closed sourced and here are a few reasons

  1. Sales does not have a strong muscle for selling our open source software at the moment. Once we make something open source it tends to be dropped from sales conversations. We need this to change and it will take some time.
  2. I think this is an experiment that is worth trying out. We've had the product completed separated, but we haven't had any controllers that are both Open & Closed source. If sales had their way we would "fork" all of Flux and have enterprise versions for everything.
  3. We can walk this back if we want. Taking something closed source and opening up is a lot easier than the reverse; so let's see what happens and we can revisit this.
  4. This will open up opportunities to put the Terraform UI in Weave GitOps OSS eventually. If we can offer additional value in enterprise then we can have some more flexbility.

I know these aren't ideal answers for everyone, but let's be open minded and flexible.

chanwit commented 1 year ago

done! Thank you @enekofb!