Skip to content
Snippets Groups Projects
Commit 4a1a02ae authored by Seth Schoen's avatar Seth Schoen
Browse files

Add some specific material about Qt DOSP contract

parent febc2eb4
No related branches found
No related tags found
No related merge requests found
......@@ -121,9 +121,25 @@ for licenses.
% a "traditional" dual license but so far have not found references to a
% scheduled relicensing practice.
% TrollTech story is complicated...
% https://tinf2.vub.ac.be/~dvermeir/manual/KDE20Development-html/ch19lev1sec4.html
% and more
As part of the controversies surrounding adoption of the Qt library by the
KDE project, various Qt copyright holders have also agreed to DOSP practices
as a contractual backstop to ensure that future versions of Qt remain
usable in free software. A series of contracts between KDE community
nonprofit entities and Qt copyright holders include commitments to release
future Qt versions under specific license terms with a ``within a timeframe
of not more than 12 months" relative to any proprietary
release.\footnote{See \otsurl{https://kde.org/community/whatiskde/kdefreeqtfoundation/}, which includes the exact language of the licensors' contractual
commitments;
a portion of the historical context is described in
\otsurl{https://tinf2.vub.ac.be/$\sim$dvermeir/manual/KDE20Development-html/ch19lev1sec4.html}.}
These rights to delay the application of the free software license have not
% TODO - ever? to what extent?
usually
% TODO
been exercised in practice; Qt versions have generally been promptly
licensed under the required licenses. The possibility of a delay together
with a specific timeframe represented a compromise between the Qt developers'
and KDE developers' views of their respective interests.
\numberedsection{Scheduled Relicensing}\label{scheduled}
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment