Clarify license options with ag grid

[ekaterinamishina]

We opensource a packaged or packagable product, which can either be run locally, or deployed somewhere. According to the page from ag grid there are several license components, SA (single application) and DL (deployment license). SA we need as many as front end javascript devs, which after 9.2. will be only one internally; DL has to be paid one per production instance for external users - does not matter if they run it locally or deployed, and how many users there will be, what counts is deployed instance.
The package can be done in a way that the person using it has to insert the license for DL component (not sure if it is purchasable without SA part). For SA, if we freeze internal development and make an open source, then in theory we should not pay any more, and whoever will download the code and start development as javascript developer, they would technically need to pay the license on their own, SA + potentially some DA.
This model has to be clarified with ag-grid.

[ekaterinamishina]

@Kleiner60 fyi, pls help me to set up a call with ag grid since you are the contact person

[ekaterinamishina]

@Kleiner60 as a summary after our call with ag-grid, we should ship the code without any license, then end user will see watermark indicating they need a license when they launch the solution (disappears shortly). If client is using it for demo purpose - no license is needed. If they start to use the product internally, they have to purchase SA license (one per javascript dev) or use existing agreement within the company if they already use ag-grid in the other projects (MA option). If end user start using it for clients external to them, then SA/MA+DL will be needed. In the latter two cases end user should have license agreement with ag-grid.
@akravets-sm is preparing ui in a way that license will be taken from the env var. We should have it written somewhere transparently for end users if they will need a license at some point in time.