Paid Add-Ons

Permalink
Hi - Does anyone know how I would go about using a paid add-on on multiple versions of the same site.. eg. I have a production, development and staging version of the site and need to use the add-on on all 3?

Does the market place allow non-production copies of paid add-ons?

Thanks

5fly
 
citytech2 replied on at Permalink Reply
citytech2
You can use it in all the versions as it uses the same database instance.

Citytech
Mainio replied on at Permalink Reply
Mainio
Actually if you carefully read the license terms:
1.    License Grant.  Subject to the provisions of this Agreement, Customer is granted a limited, non-transferable, non-exclusive license to use the Software Application for a single website and a single staging or development version.  Customer may not offer the System for resale without expressed permission from DEVELOPMENT PARTNER.


And to highlight the interesting part:
--- to use the Software Application for a single website AND a single staging OR development version. ---


1 AND (1 OR 1) = 1 + 1 = 2 sites in total

So the default marketplace license allows you legally to use the add-on for 2 publicly available sites. So if we want to be very accurate, this takes away the possibility for 3-step deployment process where you have:
- Testing
- Staging
- Production

(if these all are publicly available but very rarely all of them are)

At least with our add-ons you can "stretch" this statement to include all the development (=non-production) versions of the site although if you asked from a lawyer, they'd said it is what it states.


Antti / Mainio
5fly replied on at Permalink Reply
5fly
Thanks, yep the licence is a little ambiguous around the publicly available part... If thats the case our only publicly available site is production. Dev, Test and Staging are all internal only....
Mainio replied on at Permalink Reply
Mainio
Yeah, it's a bit unclear but I'd believe it means publicly available sites. The funny part here is that AFAIK you can connect even 100 sites with the same marketplace token to the community and they all fall under the same "project" and allows you to use the add-ons assigned to that project. But I guess it is left on purpose for the site owner / developer to make sure the license is followed.
JohntheFish replied on at Permalink Reply
JohntheFish
Although what the automated licence checking achieves is less restricted that what the actual licence means, its the actual licence that 'is the rules'.
Mainio replied on at Permalink Reply
Mainio
Yes of course. And we should also remember that the marketplace allows the developers to define their own license terms as well, so this topic only applies to the default marketplace license and its unclear/ambiguous parts.
frz replied on at Permalink Best Answer Reply
frz
The intention of the license is to limit you to one active website, meaning an instance of concrete5.

Yes, you can map multiple domains to a single instance and that's fine with this license.
Yes, you can have development stages and copies. I see what you're saying about the implied total, but I can tell you we will not be enforcing anything around limiting number of staging or development copies you have.

The idea here is one install requires one add-on license. Feel free to make as many development copies as you need to support that one install.

At some point in the future we will look at further clarifying that in the license.