Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [open-regulatory-compliance] Trial version of a Product vs “community”/FOSS version

Dear Matija,

I think Roman has already covered most points, but i'll do another runthrough to be sure:

1. A commercial software product, even under a FOSS licence is in scope of the CRA because there is sale with the intent to make a profit (among other reasons).

2. In all of these cases, a community edition is a separate thing from the commercial product, and in theory not subject to the CRA. The only issue would be if you are automatically the steward of that project if you manufacture the commercial edition. That remains to be seen, but in any case, it would make a lot of sense to be the steward, as it comes without risk of fines, and gives you some legal certainty on your community edition.

3. I don't think the CRA talks about "trial versions", so we don't really have any precedent, but my view would be that by default, the trial version is covered under the same rules as the paid proprietary product it is a trial of. I would highly recommend including a disclaimer that the trial version is for evaluation purposes only, and not including a CE mark on it (although keen to hear others opinions on this). Perhaps this is also something we should ask the Commission about?

I know it's a bit of a maze, but we will get there! As a side point, the approach to enforcement of the CRA will likely be very consensual: market surveillance authorities are unlikely to chase you down and fine you immediately, they might ask you to make changes or provide clarifications on certain things, but fines are really for cases where the developer is not complying and refusing to make any changes. I suspect a lot will become clearer when enforcement begins.

Kind regards,
--
Jordan Maris
EU Policy Analyst, The Open Source Initiative
EU Policy Officer, OSI Europe Foundation
matrix: @me:jmar.is
tel: +33613141427
book a meeting: book.jmar.is


On Fri, Sep 11, 2026 at 9:32 PM Matija Šuklje via open-regulatory-compliance <open-regulatory-compliance@xxxxxxxxxxx> wrote:
Thanks Roman,

your comments confirm some of my understanding.

To clarify, we are talking here about the following use cases:

1) a commercial software product that is available under both a EULA and a
FOSS license – in both cases, subscription benefits are paid on top and the
code is identical, in fact it is the same product, just offered under dual-
license

2) a FOSS “community edition”, different name/TM
    2.a) identical in functionality to 1), but for the sake of the argument of
easier differentiation, following a different versioning system
    2.b) open core of 1), so missing “enterprise features”
    2.c) unversioned and only offered as source code (no pre-build packages)

3) a proprietary “trial version” of 1) – can be of a different name/TM, if
that helps
    3.a) identical in functionality to 1), but following a different
versioning system
    3.b) offering most functionality of 1), but missing some “enterprise
features”

I find a lot of the the EC Guidelines quite helpful to explaining the CRA, but
in these edge-cases, I have to admit, it also confuses me.


cheers,
Matija
--
Liferay International
Director, Legal and Associate General Counsel
(FOSS Licensing & Community Legal Affairs)
matija.suklje@xxxxxxxxxxx




_______________________________________________
open-regulatory-compliance mailing list
open-regulatory-compliance@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

Back to the top