Hubbry Logo
KDE Software CompilationKDE Software CompilationMain
Open search
KDE Software Compilation
Community hub
KDE Software Compilation
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
KDE Software Compilation
KDE Software Compilation
KDE Software Compilation
View on Wikipedia
from Wikipedia

KDE Software Compilation
DeveloperKDE
Initial release1.0 / 12 July 1998; 27 years ago (1998-07-12)
Final release4.14.3 (November 11, 2014; 10 years ago (2014-11-11)) [±][1]
Written inMainly C++ (Qt), some C
Operating systemEntire DE: Unix-like with X11 or Wayland and also Windows XP–7.[2]
Applications only: Mac OS X 10.4–10.6
Available in86 languages[3]
List of languages
  • Full (52): Arabic, Basque, Bosnian, Brazilian Portuguese, British English, Catalan, Catalan (Valencian), Chinese Simplified, Chinese Traditional, Croatian, Czech, Danish, Dutch, Esperanto, Estonian, Farsi (Persian), Finnish, French, Galician, German, Greek, Hebrew, Hindi, Hungarian, Icelandic, Indonesian, Interlingua, Irish Gaelic, Italian, Japanese, Kazakh, Khmer, Korean, Latvian, Lithuanian, Low Saxon, Marathi, Norwegian Bokmål, Norwegian Nynorsk, Polish, Portuguese, Punjabi, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swedish, Turkish, Ukrainian, Uyghur
  • Partial (34): Afrikaans, Armenian, Assamese, Asturian, Belarusian (Latin), Bengali, Bengali (India), Breton, Bulgarian, Chhattisgarhi, West Frisian, Gujarati, Kannada, Kashubian, Kurdish, Macedonian, Maithili, Malay, Malayalam, Northern Sami, Oriya, Pashto, Sinhala, Tajik, Tamil, Tatarish, Telugu, Thai, Upper Sorbian, Uzbek, Uzbek (Cyrillic), Vietnamese, Walloon
TypeDesktop environment
LicenseGNU GPL, GNU LGPL, BSD License, MIT License[4]
Websitekde.org

The KDE Software Compilation (KDE SC) was an umbrella term for the desktop environment plus a range of included applications produced by KDE. From its 1.0 release in July 1998 until the release of version 4.4 in February 2010, the Software Compilation was simply known as KDE, which stood for K Desktop Environment until the rebrand.[5] The then called KDE SC was used from 4.4 onward until the final release 4.14 in July 2014. It consisted of the KDE Plasma 4 desktop and those KDE applications, whose development teams chose to follow the Software Compilation's release schedule. After that, the KDE SC was split into three separate product entities: KDE Plasma, KDE Frameworks and KDE Applications, each with their own independent release schedules.

History

[edit]

Origins

[edit]

KDE was founded in 1996 by Matthias Ettrich, who was then a student at the University of Tübingen. At the time, he was troubled by certain aspects of the Unix desktop. Among his qualms was that none of the applications looked, felt, or worked alike. He proposed the formation of not only a set of applications, but, rather, a desktop environment, in which users could expect things to look, feel and work consistently. He also wanted to make this desktop easy to use; one of his complaints with desktop applications of the time was that his girlfriend could not use them. His initial Usenet post spurred a lot of interest, and the KDE project was born.[6]

Ettrich chose to use Trolltech's Qt framework for the KDE project. Other programmers quickly started developing KDE/Qt applications, and by early 1997, a few applications were being released.

First series

[edit]
K Desktop Environment 1.0
Main article: K Desktop Environment 1

On 12 July 1998, K Desktop Environment 1.0 was released. In November 1998, the Qt toolkit was dual-licensed under the free/open source Q Public License (QPL) and a proprietary license for proprietary software developers. Debate continued about compatibility with the GNU General Public License (GPL), so in September 2000, Trolltech made the Unix version of the Qt libraries available under the GPL, in addition to the QPL. Trolltech continued to require licenses for developing proprietary software with Qt. The core libraries of KDE are collectively licensed under the GNU LGPL, but the only way for proprietary software to make use of them was to be developed under the terms of the Qt proprietary license.

Second series

[edit]
K Desktop Environment 2.0
Main article: K Desktop Environment 2

Beginning 23 October 2000, the second series of releases, K Desktop Environment 2, introduced significant technological improvements.[7] These included DCOP (Desktop COmmunication Protocol), KIO (an application I/O library), KParts (a component object model, which allows an application to embed another within itself), and KHTML (an HTML rendering and drawing engine).[7]

Third series

[edit]
KDE 3.2 with Konqueror and the About screen[8]
Main article: K Desktop Environment 3

The third series was much larger than previous series, consisting of six major releases starting on 3 April 2002. The API changes between K Desktop Environment 2 and K Desktop Environment 3 were comparatively minor, meaning that the KDE 3 can be seen as largely a continuation of the K Desktop Environment 2 series. All releases of K Desktop Environment 3 were built upon Qt 3, which was only released under the GPL for Linux and Unix-like operating systems, including Mac OS X. It is marked stable running on Mac OS X since 2008. Unlike KDE SC 4, however, it requires an X11 server to operate.[9] In 2002, members of the KDE on Cygwin project began porting the GPL licensed Qt/X11 code base to Windows.[10]

Fourth series

[edit]
Latest Plasma Desktop in KDE Software Compilation 4.10
Main article: KDE Software Compilation 4

KDE Software Compilation 4, first released on 11 January 2008, is based on Qt 4, which is also released under the GPL for Windows and Mac OS X. Therefore, KDE SC 4 applications can be compiled and run natively on these operating systems as well. KDE Software Compilation 4 on Mac OS X is currently considered beta,[11] while on Windows it is not in the final state, so applications can be unsuitable for day to day use.[12][13]

KDE SC 4 includes many new technologies and technical changes. The centerpiece is a redesigned desktop and panels collectively called Plasma, which replaces Kicker, KDesktop, and SuperKaramba by integrating their functionality into one piece of technology; Plasma is intended to be more configurable for those wanting to update the decades-old desktop metaphor. There are a number of new frameworks, including Phonon (a new multimedia interface making KDE independent of any one specific media backend) Solid (an API for network and portable devices), and Decibel (a new communication framework to integrate all communication protocols into the desktop). Also featured is a metadata and search framework, incorporating Strigi as a full-text file indexing service, and NEPOMUK with KDE integration.[14]

Starting with Qt 4.5, Qt was also made available under the LGPL version 2.1,[15] a major step for KDE adoption in corporate and proprietary environments, as the LGPL permits proprietary applications to link to libraries licensed under the LGPL.

Post-fourth series

[edit]
KDE Plasma 5.26 with Breeze Twilight theme, mix of dark and light color scheme.

As of August 2014, KDE no longer provides synchronized releases of the entire software compilation; instead the software is split into three parts:

  • KDE Frameworks 5, a collection of libraries and software frameworks (5.0 released on July 7, 2014, and new major releases are made monthly)[16]
  • KDE Plasma 5, a desktop environment (5.0 released on July 15, 2014, and new major releases are made every three months)[17]
  • KDE Applications, a bundle of applications and supporting libraries (14.12 was the first version incorporating Frameworks 5 based applications, and introduced date-based version numbers).[18]

Major changes include a move from Qt 4 to Qt 5, support for the next-generation display server protocol Wayland, support for the next-generation rendering API Vulkan and modularization of the KDE core libraries.[19] Initial releases of Frameworks 5 and Plasma 5 were made available in July 2014.[16][17]

The releases KDE Frameworks 5, KDE Plasma 5 and KDE Applications 5 are not one singular entity. These parts have been only released together, and cobbling them up under one name really has not been helpful. 3rd party developers thought they would only target Plasma Workspaces, Plasma users have thought you’ll only be able to run “KDE apps”, potential users of applications will assume that you can only use them inside Plasma workspaces — all of them untrue, all of them taken right out of my daily experience.[20]

Development

[edit]

Source code

[edit]

KDE SC releases are made to the KDE FTP server[21] in the form of source code with configure scripts, which are compiled by operating system vendors and integrated with the rest of their systems before distribution. Most vendors use only stable and tested versions of KDE SC, providing it in the form of easily installable, pre-compiled packages. The source code of every stable and development version of KDE SC is stored in the KDE source code repository, using Git.[22] KDE Platform is licensed under the LGPL, BSD license, MIT license, or X11 license. Applications also allow GPL. Documentation also allow FDL. CMake modules must be licensed under the BSD licence.[23]

Major releases

[edit]

Major releases are releases that begin a series (version number X.0). These releases are allowed to break binary compatibility with the predecessor, or to put it differently, all following releases (X.1, X.2, ...) will guarantee binary portability (API & ABI). This means, for instance, that software that was developed for KDE 3.0 will work on all (future) KDE 3 releases; however, an application developed for KDE 2 is not guaranteed to be able to make use of the KDE 3 libraries. KDE major version numbers follow the Qt release cycle, meaning that KDE SC 4 is based on Qt 4, while KDE 3 was based on Qt 3.

Qt 5.0 was released 19 December 2012, Qt 5.2 12 December 2013. And for example KDE Frameworks 5.21.0 requires Qt >= 5.4, and no longer supports Qt 5.3 (cf. Qt version history).

Standard releases

[edit]

There are two main types of standard releases: Feature releases and bugfix releases.

Feature releases have two version numbers, for example 3.5 and contain new features. As soon as a feature release is ready and announced, work on the next feature release starts. A feature release needs several months to be finished and many bugs that are fixed during this time are backported to the stable branch, meaning that these fixes are incorporated into the last stable release by bugfix releases. During the KDE SC 4 series, KDE SC had a feature release roughly every six months. Since the split, KDE Plasma releases a new feature version roughly every 3–4 months.

Bugfix releases have three version numbers, e.g. KDE 1.1.1, and focus on fixing bugs, minor glitches, and making small usability improvements. Bugfix releases in general do not allow new features, although some releases include small enhancements. A shortened release schedule is used. Starting with the KDE SC 4 series, KDE SC has a maintenance release roughly every month, except during the month of a feature release, while with Plasma 5, bugfix releases tend to happen even shorter like 2–3 weeks.

Release cycle

[edit]
Timeline of major releases
Date Release
14 October 1996 Project announced by Matthias Ettrich[24]
KDE 1
12 July 1998 KDE 1.0[25]
6 February 1999 KDE 1.1[26]
KDE 2
23 October 2000 KDE 2.0[27]
26 February 2001 KDE 2.1[28]
15 August 2001 KDE 2.2[29]
KDE 3
3 April 2002 KDE 3.0[30]
28 January 2003 KDE 3.1[31]
3 February 2004 KDE 3.2[32]
19 August 2004 KDE 3.3[33]
16 March 2005 KDE 3.4[34]
29 November 2005 KDE 3.5[35]
KDE SC 4
11 January 2008 KDE 4.0[36]
29 July 2008 KDE 4.1[37]
27 January 2009 KDE 4.2[38]
4 August 2009 KDE 4.3[39]
9 February 2010 KDE SC 4.4[40]
10 August 2010 KDE SC 4.5[41]
26 January 2011 KDE SC 4.6[42]
27 July 2011 KDE SC 4.7[43]
25 January 2012 KDE SC 4.8[44]
1 August 2012 KDE SC 4.9[45]
5 February 2013 KDE SC 4.10[46]
14 August 2013 KDE SC 4.11[47] KDE Plasma 4 feature freeze + LTS until August 2015
18 December 2013 KDE SC 4.12[48]
16 April 2014 KDE SC 4.13[49]
31 July 2014 KDE SC 4.14 released; Some Applications are based on KDE Platform 4, some on KDE Frameworks 5[50]
KDE Qt5-based software
Date Release Date Release Date Release
KDE Frameworks 5 KDE Plasma 5 KDE Applications / KDE Gear
7 July 2014 KDE Frameworks 5.0[51] 15 July 2014 KDE Plasma 5.0[52]
7 August 2014 KDE Frameworks 5.1[53]
12 September 2014 KDE Frameworks 5.2[54]
7 October 2014 KDE Frameworks 5.3[55] 15 October 2014 KDE Plasma 5.1[56]
6 November 2014 KDE Frameworks 5.4[57]
11 December 2014 KDE Frameworks 5.5[58] 17 December 2014 KDE Applications 14.12[59]
8 January 2015 KDE Frameworks 5.6[60] 27 January 2015 KDE Plasma 5.2[61]
14 February 2015 KDE Frameworks 5.7[62]
13 March 2015 KDE Frameworks 5.8[63]
10 April 2015 KDE Frameworks 5.9[64] 28 April 2015 KDE Plasma 5.3[65] 15 April 2015 KDE Applications 15.04[66]
8 May 2015 KDE Frameworks 5.10[67]
12 June 2015 KDE Frameworks 5.11[68]
10 July 2015 KDE Frameworks 5.12[69]
12 August 2015 KDE Frameworks 5.13[70] 25 August 2015 KDE Plasma 5.4[71] 19 August 2015 KDE Applications 15.08[72]
12 September 2015 KDE Frameworks 5.14[73]
10 October 2015 KDE Frameworks 5.15[74]
13 November 2015 KDE Frameworks 5.16[75]
12 December 2015 KDE Frameworks 5.17[76] 8 December 2015 KDE Plasma 5.5[77] 16 December 2015 KDE Applications 15.12[78]
9 January 2016 KDE Frameworks 5.18[79]
13 February 2016 KDE Frameworks 5.19[80]
13 March 2016 KDE Frameworks 5.20[81] 22 March 2016 KDE Plasma 5.6[82]
9 April 2016 KDE Frameworks 5.21[83] 20 April 2016 KDE Applications 16.04 LTS[84]
15 May 2016 KDE Frameworks 5.22[85]
13 June 2016 KDE Frameworks 5.23[86]
9 July 2016 KDE Frameworks 5.24[87] 5 July 2016 KDE Plasma 5.7[88]
13 August 2016 KDE Frameworks 5.25[89] 18 August 2016 KDE Applications 16.08[90]
10 September 2016 KDE Frameworks 5.26[91]
8 October 2016 KDE Frameworks 5.27[92] 4 October 2016 KDE Plasma 5.8 LTS[93]
15 November 2016 KDE Frameworks 5.28[94]
12 December 2016 KDE Frameworks 5.29[95] 15 December 2016 KDE Applications 16.12[96]
14 January 2017 KDE Frameworks 5.30[97] 31 January 2017 KDE Plasma 5.9[98]
11 February 2017 KDE Frameworks 5.31[99]
11 March 2017 KDE Frameworks 5.32[100]
8 April 2017 KDE Frameworks 5.33[101] 20 April 2017 KDE Applications 17.04[102]
13 May 2017 KDE Frameworks 5.34[103] 30 May 2017 KDE Plasma 5.10[104]
10 Jun 2017 KDE Frameworks 5.35[105]
8 July 2017 KDE Frameworks 5.36[106]
13 August 2017 KDE Frameworks 5.37[107] 17 August 2017 KDE Applications 17.08[108]
9 September 2017 KDE Frameworks 5.38[109]
14 October 2017 KDE Frameworks 5.39[110] 10 October 2017 KDE Plasma 5.11[111]
11 November 2017 KDE Frameworks 5.40[112]
10 December 2017 KDE Frameworks 5.41[113] 14 December 2017 KDE Applications 17.12[114]
13 January 2018 KDE Frameworks 5.42[115]
12 February 2018 KDE Frameworks 5.43[116] 6 February 2018 KDE Plasma 5.12 LTS[117]
10 March 2018 KDE Frameworks 5.44[118]
14 April 2018 KDE Frameworks 5.45[119] 19 April 2018 KDE Applications 18.04 LTS[120]
12 May 2018 KDE Frameworks 5.46[121]
9 June 2018 KDE Frameworks 5.47[122] 12 June 2018 KDE Plasma 5.13[123]
14 July 2018 KDE Frameworks 5.48[124]
11 August 2018 KDE Frameworks 5.49[125] 16 August 2018 KDE Applications 18.08[126]
8 September 2018 KDE Frameworks 5.50[127]
15 October 2018 KDE Frameworks 5.51[128] 9 October 2018 KDE Plasma 5.14[129]
10 November 2018 KDE Frameworks 5.52[130]
8 December 2018 KDE Frameworks 5.53[131] 13 December 2018 KDE Applications 18.12[132]
12 January 2019 KDE Frameworks 5.54[133]
9 February 2019 KDE Frameworks 5.55[134] 12 February 2019 KDE Plasma 5.15[135]
9 March 2019 KDE Frameworks 5.56[136]
13 April 2019 KDE Frameworks 5.57[137] 18 April 2019 KDE Applications 19.04[138]
13 May 2019 KDE Frameworks 5.58[139]
8 June 2019 KDE Frameworks 5.59[140] 11 June 2019 KDE Plasma 5.16[141]
13 July 2019 KDE Frameworks 5.60[142]
10 August 2019 KDE Frameworks 5.61[143] 15 August 2019 KDE Applications 19.08[144]
14 September 2019 KDE Frameworks 5.62[145]
12 October 2019 KDE Frameworks 5.63[146] 15 October 2019 KDE Plasma 5.17[147]
10 November 2019 KDE Frameworks 5.64[148]
14 December 2019 KDE Frameworks 5.65[149] 12 December 2019 KDE Applications 19.12[150]
11 January 2020 KDE Frameworks 5.66[151]
2 February 2020 KDE Frameworks 5.67[152] 11 February 2020 KDE Plasma 5.18 LTS[153]
7 March 2020 KDE Frameworks 5.68[154]
5 April 2020 KDE Frameworks 5.69[155] 23 April 2020 KDE Applications 20.04 LTS[156]
2 May 2020 KDE Frameworks 5.70[157]
6 June 2020 KDE Frameworks 5.71[158] 9 June 2020 KDE Plasma 5.19[159]
4 July 2020 KDE Frameworks 5.72[160]
1 August 2020 KDE Frameworks 5.73[161] 13 August 2020 KDE Applications 20.08[162]
6 September 2020 KDE Frameworks 5.74[163]
10 October 2020 KDE Frameworks 5.75[164] 13 October 2020 KDE Plasma 5.20[165]
7 November 2020 KDE Frameworks 5.76[166]
12 December 2020 KDE Frameworks 5.77[167] 10 December 2020 KDE Applications 20.12[168]
9 January 2021 KDE Frameworks 5.78[169]
13 February 2021 KDE Frameworks 5.79[170] 16 February 2021 KDE Plasma 5.21[171]
13 March 2021 KDE Frameworks 5.80[172]
10 April 2021 KDE Frameworks 5.81[173] 22 April 2021 KDE Gear 21.04[174]
8 May 2021 KDE Frameworks 5.82[175]
12 June 2021 KDE Frameworks 5.83[176] 8 June 2021 KDE Plasma 5.22[177]
10 July 2021 KDE Frameworks 5.84[178]
13 August 2021 KDE Frameworks 5.85[179] 12 August 2021 KDE Gear 21.08[180]
11 September 2021 KDE Frameworks 5.86[181]
9 October 2021 KDE Frameworks 5.87[182] 14 October 2021 KDE Plasma 5.23[183]
13 November 2021 KDE Frameworks 5.88[184]
11 December 2021 KDE Frameworks 5.89[185] 9 December 2021 KDE Gear 21.12[186]
8 January 2022 KDE Frameworks 5.90[187]
13 February 2022 KDE Frameworks 5.91[188] 8 February 2022 KDE Plasma 5.24 LTS[189]
12 March 2022 KDE Frameworks 5.92[190]
9 April 2022 KDE Frameworks 5.93[191] 21 April 2022 KDE Gear 22.04 LTS[192]
14 May 2022 KDE Frameworks 5.94[193]
12 June 2022 KDE Frameworks 5.95[194] 14 June 2022 KDE Plasma 5.25[195]
9 July 2022 KDE Frameworks 5.96[196]
14 August 2022 KDE Frameworks 5.97[197] 18 August 2022 KDE Gear 22.08[198]
12 September 2022 KDE Frameworks 5.98[199]
9 October 2022 KDE Frameworks 5.99[200] 11 October 2022 KDE Plasma 5.26[201]
14 November 2022 KDE Frameworks 5.100[202]
10 December 2022 KDE Frameworks 5.101[203] 8 December 2022 KDE Gear 22.12[204]
14 January 2023 KDE Frameworks 5.102[205]
11 February 2023 KDE Frameworks 5.103[206] 14 February 2023 KDE Plasma 5.27 LTS[207]
12 March 2023 KDE Frameworks 5.104[208]
8 April 2023 KDE Frameworks 5.105[209] 20 April 2023 KDE Gear 23.04[210]
13 May 2023 KDE Frameworks 5.106[211]
10 June 2023 KDE Frameworks 5.107[212]
8 July 2023 KDE Frameworks 5.108[213]
17 August 2023 KDE Frameworks 5.109[214] 24 August 2023 KDE Gear 23.08[215]
10 September 2023 KDE Frameworks 5.110[216]
18 October 2023 KDE Frameworks 5.111[217]
12 November 2023 KDE Frameworks 5.112[218]
14 December 2023 KDE Frameworks 5.113[219]
13 January 2024 KDE Frameworks 5.114[220]
10 February 2024 KDE Frameworks 5.115[221]
19 May 2024 KDE Frameworks 5.116[222]
KDE Qt6-based software
Date Release Date Release Date Release
KDE Frameworks 6 KDE Plasma 6 KDE Gear
28 February 2024 KDE Frameworks 6.0[223] 28 February 2024 KDE Plasma 6.0[223] 28 February 2024 KDE Gear 24.02[223]
12 April 2024 KDE Frameworks 6.1[224]
10 May 2024 KDE Frameworks 6.2[225] 23 May 2024 KDE Gear 24.05[226]
7 June 2024 KDE Frameworks 6.3[227] 18 June 2024 KDE Plasma 6.1[228]
12 July 2024 KDE Frameworks 6.4[229]
9 August 2024 KDE Frameworks 6.5[230] 22 August 2024 KDE Gear 24.08[231]
13 September 2024 KDE Frameworks 6.6[232]
11 October 2024 KDE Frameworks 6.7[233] 8 October 2024 KDE Plasma 6.2[234]
8 November 2024 KDE Frameworks 6.8[235]
13 December 2024 KDE Frameworks 6.9[236] 12 December 2024 KDE Gear 24.12[237]
9 January 2025 KDE Frameworks 6.10[238]
14 February 2025 KDE Frameworks 6.11[239] 11 February 2025 KDE Plasma 6.3[240]
14 March 2025 KDE Frameworks 6.12[241]
11 April 2025 KDE Frameworks 6.13[242] 17 April 2025 KDE Gear 25.04[243]
9 May 2025 KDE Frameworks 6.14[244]
13 June 2025 KDE Frameworks 6.15[245] 17 June 2025 KDE Plasma 6.4[246]
11 July 2025 KDE Frameworks 6.16[247]
8 August 2025 KDE Frameworks 6.17[248] 14 August 2025 KDE Gear 25.08[249]
12 September 2025 KDE Frameworks 6.18[250]

The KDE team releases new versions on a regular basis.[251]

Lines of Code

[edit]

Implementation

[edit]

Most KDE software uses Qt which runs on most Unix and Unix-like systems (including Mac OS X), Android and Microsoft Windows. As of 2011 CMake serves as the build tool. This allows KDE to support a wider range of platforms, including Windows.[254] GNU gettext is used for translation. Doxygen is used to generate api documentation.[255]

Overview

[edit]
  • KDE Software Compilation: KDE Software Compilation (KDE SC) is the coordinated releases of new software versions, gathering elements from the previous components to build an integrated core of software. The KDE SC is not a product as a single entity.
  • Calligra Suite: Integrated office suite.
  • KDEWebdev: Web development tools.
  • KDE-Extragear: Extragear is a collection of applications associated with KDE. Those applications are not part the official software compilation, but they are still part of the project.
  • KDE-Playground: This package contains pre-release and unstable software. It is a place for applications to mature.[256]

Packages

[edit]
Default login sound of KDE SC

The Software Compilation consists of the following packages:

Base technologies

[edit]

Applications

[edit]
For a more comprehensive list, see KDE Applications.
The Kontact personal information manager and Konqueror file manager/web browser running on KDE Plasma 5.2

Major applications by KDE Software Compilation include:

Licensing

[edit]

In November 1998, the Qt framework was dual-licensed under the free and open-source Q Public License (QPL) and a commercial license for proprietary software developers. The same year, the KDE Free Qt foundation was created which guarantees that Qt would fall under a variant of the very liberal BSD license should Trolltech cease to exist or no free version of Qt be released during 12 months.[258]

Debate continued about compatibility with the GNU General Public License (GPL), hence in September 2000 Trolltech made the Unix version of the Qt libraries available under the GPL in addition to the QPL which eliminated the concerns of the Free Software Foundation.[259] Trolltech continued to require licenses for developing proprietary software with Qt. The core libraries of KDE are collectively licensed under the GNU LGPL but the only way for proprietary software to make use of them was to be developed under the terms of the Qt proprietary license.

Starting with Qt 4.5, Qt was also made available under the LGPL version 2.1,[260] now allowing proprietary applications to legally use the open source Qt version.

See also

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

KDE Software Compilation

View on Grokipedia
from Grokipedia
The KDE Software Compilation (KDE SC) was a synchronized collection of developed by the community, serving as a comprehensive and application suite for operating systems, including the Plasma workspace, foundational libraries, and productivity tools released together under a unified versioning scheme from 2009 to 2014. Introduced during the KDE 4 series, the term "KDE Software Compilation" first appeared in announcements starting with version 4.3.4 in late , reflecting a shift toward branding the project as a broader beyond just a . This approach allowed for cohesive releases that integrated user interfaces, development frameworks, and applications, emphasizing modularity, performance improvements, and cross-platform compatibility, with major versions like 4.4 ("Caikaku") in 2010 introducing features such as netbook interfaces and enhanced web integration. The compilation evolved through 11 minor releases, culminating in 4.14 in August 2014, which focused on stability and refinements to core components. Key components of the KDE SC included the KDE Plasma Workspaces, providing customizable desktop and netbook interfaces; the KDE Development Platform, offering shared libraries and runtime dependencies for building applications; KDE Base Applications, such as file managers and text editors essential for daily use; and a broader set of KDE Applications for tasks like multimedia, office productivity, and system administration. These elements were designed to work seamlessly together, supporting the Qt framework and promoting , , and community-driven enhancements. By the mid-2010s, as KDE transitioned to version 5, the unified compilation model was restructured into independent release cycles for KDE Plasma (the desktop shell), KDE Frameworks (modular libraries), and (later rebranded as KDE Gear in 2022), allowing for more flexible development and faster iteration while maintaining . This evolution marked the end of the KDE SC as a formal entity but preserved its legacy in powering millions of and Unix desktops worldwide.

Overview

Definition and Scope

The KDE Software Compilation (KDE SC) was a branded, synchronized release model encompassing the desktop environment, foundational libraries, and a suite of applications, designed to deliver a unified software for users. Bundled KDE releases began with KDE 1.0 in 1998, representing an integrated package of built primarily on the Qt toolkit, allowing for modular development while maintaining a cohesive across and other operating systems. The term "KDE Software Compilation" was formally adopted starting with version 4.3.4 in 2009 and explicitly rebranded for the 4.4 release in 2010 to better reflect the community's output as a comprehensive set of workspaces, applications, and development platforms. The primary purpose of the KDE SC was to offer a user-friendly, integrated desktop solution that emphasized , customization, and , addressing the needs of both novice and advanced users in environments. By bundling components such as the Plasma workspace, KDE Platform libraries, and applications like and , it promoted modularity—enabling independent use or extension—while ensuring synchronized updates for stability and feature alignment. This approach fostered community-driven development, with contributions from global volunteers coordinated through the KDE project, ultimately aiming to rival desktops in functionality and polish. The initiative stemmed from the late 1990s gap in available free, Qt-based graphical desktop alternatives for systems, where existing options like the were seen as inconsistent or overly complex for everyday use. In 1996, founded to create a "consistent, nice-looking free " that leveraged Qt's capabilities under an open license, responding directly to this void and enabling rapid prototyping of a full-featured interface. The SC was active from the version 4.3.4 release in 2009 until the final KDE 4.14 version on August 20, 2014, spanning the 4 series with a unified versioning scheme. Earlier releases from July 12, 1998, used a similar bundling approach without the SC branding. Following 4.14, the model transitioned to independent release cycles for Plasma (the workspace), KDE Frameworks (libraries), and KDE Applications, allowing greater flexibility in development and distribution.

Key Components and Evolution

The KDE Software Compilation (KDE SC) primarily consisted of three core components designed to provide a cohesive : KDE Plasma Workspaces, the KDE Platform, and KDE Applications. KDE Plasma Workspaces served as the desktop shell and workspace, offering customizable panels, widgets, and a for user interaction, with features like hardware integration via the framework for device management and power handling. In early versions, Plasma emphasized a unified visual experience through technologies like the Oxygen artwork style for consistent vector-based theming across the interface. The KDE Platform provided foundational libraries and technologies, including and KJS for web rendering in applications like the browser, as well as multimedia support through and multi-threading via ThreadWeaver to optimize performance on multi-core systems. These libraries formed the base for cross-platform development on Qt, enabling seamless integration of hardware and software resources. The Platform was later restructured as KDE Frameworks starting in 2014. KDE Applications encompassed a suite of productivity and utility tools, such as the , document viewer, and , with historical inclusions like KOffice for office tasks; later iterations expanded to over 200 actively maintained applications focused on stability and user needs. The evolution of KDE SC shifted from tightly integrated, monolithic bundles in the KDE 1-3 series—where applications and libraries were closely coupled for a uniform C++-based ecosystem—to a more modular architecture starting with the KDE 4 series, which introduced Activities for task organization and the semantic desktop for context-aware data management, enhancing user experience through better resource handling and customization. This modularity continued post-SC in KDE Frameworks 5, splitting the former monolithic Platform into over 70 independent libraries to improve accessibility for Qt developers and allow independent evolution of components. Central to KDE SC's design is its bundling philosophy, where Plasma Workspaces, the Platform, and Applications were released simultaneously under a unified version number to ensure compatibility and a seamless integrated experience, encompassing over 100 applications in mature series to support diverse user workflows.

History

Origins and Early Development

The project originated on October 14, 1996, when German computer science student posted a message on the de.comp.os.linux.misc announcing the creation of the "Kool Desktop Environment" (). Ettrich expressed dissatisfaction with the fragmented state of graphical user interfaces available for systems at the time, particularly the (), which was proprietary and lacked a consistent, free alternative. He proposed building a new desktop using the Qt toolkit from Trolltech, praising its signal-slot mechanism for simplifying development of consistent applications and its potential for cross-platform compatibility, while noting Qt's free license for non-commercial use as sufficient for an open-source project. Early development encountered substantial hurdles stemming from Qt's licensing model, which was not fully aligned with standards. Trolltech's Qt was distributed under the Q Public License (QPL), a proprietary arrangement that permitted free use for non-commercial purposes but restricted modifications and commercial redistribution without permission, drawing sharp criticism from the (FSF). The FSF argued that relying on such a toolkit undermined the principles of by creating dependencies on non-free components, and they publicly discouraged the distribution of software on FSF-endorsed platforms like /Linux distributions. These concerns prompted the community to establish e.V., a non-profit association, on November 27, 1997, in , , to provide legal and financial representation for the project and to negotiate safeguards for Qt's ongoing availability to open-source developers. Qt's licensing issues persisted until 2000, when Trolltech dual-licensed it under the GNU General Public License (GPL), resolving much of the controversy. Pre-release development emphasized constructing a cohesive suite rather than isolated components, with the first beta version (KDE 0.0 Beta 1) issued on October 20, 1997, coinciding roughly with the project's first anniversary. This beta introduced core elements of the K Desktop Environment, including the KWM window manager (later evolved into KWin), the kfm file manager (a precursor to Konqueror that integrated file browsing and basic web viewing), and the kpanel for task management and applets, all designed to deliver a unified, intuitive interface for Unix workstations. Subsequent betas refined these features, prioritizing network transparency, drag-and-drop functionality, and integration with existing Unix tools. The efforts culminated in KDE 1.0, released on July 12, 1998, as the project's inaugural stable offering and the foundation of the KDE Software Compilation, encompassing KDE Core libraries for foundational services, a suite of applications like the K Desktop and file utilities, and supporting tools for a complete desktop experience.

KDE 1 to 3 Series

The 1 series, spanning from 1998 to 2000, marked the initial stable releases of the , beginning with version 1.0 on July 12, 1998. This version introduced a network-transparent graphical desktop for Unix workstations, featuring an easy-to-use interface inspired by contemporary systems like MacOS and /NT. Core components included the KPanel for and applets, the File Manager (KFM) for handling files and directories, and the K Window Manager (KWM) for window decoration and management. The series emphasized integration with the Qt toolkit for application development, providing the KOM/OpenParts framework to enable component-based software creation, alongside a preview of the KOffice suite for productivity tasks. Focus areas included stability enhancements and Qt compatibility, with iterative updates addressing usability and internationalization. The final release, 1.1.2, arrived in late 2000, solidifying the foundation for subsequent iterations. Building on this base, the 2 series (2000–2002) introduced versions from to 2.2.2, with the inaugural launch on October 23, 2000. Key advancements centered on modularity and internet integration, involving contributions from hundreds of developers across over 30 countries. A major addition was the Desktop COmmunication Protocol (DCOP), a lightweight system for inter-application messaging built on the X11 library, supporting bindings in , C++, Python, and experimental to facilitate seamless desktop interactions. The (Analog Real-Time Synthesizer) sound server enabled concurrent handling of multiple audio and video streams, including formats like /2/4, , and , with for distributed playback. Multilingual support expanded to 15 languages at launch, with and bidirectional script handling for languages like and Hebrew, alongside 20 more translations in progress. Developer tools gained prominence, including KDevelop as an integrated environment for C++ and other languages, promoting with components like KParts for embedding and for protocol-agnostic I/O. The series culminated in 2.2.2 on November 22, 2001, incorporating security fixes and performance optimizations. The KDE 3 series (2002–2008) represented a long-term stability milestone, with releases from 3.0 to 3.5.10, starting with 3.0 on April 3, 2002. Renowned for its rock-solid reliability, this era enhanced productivity through refined applications and system integration, earning praise from distributors like SuSE and Turbolinux for performance gains. Konqueror evolved into a versatile tool serving as a full-featured web browser, file manager, and document viewer, powered by the KHTML rendering engine supporting ECMAScript, Java, HTML 4.0, CSS levels 1 and 2, SSL, and plugins such as Flash and RealAudio. Semantic desktop elements emerged via the KDE Personal Information Management (PIM) suite, including KOrganizer for group scheduling with iTIP support and KMail with OpenPGP encryption, alongside KIOSlaves for network-transparent access to files and data sources. Optical media handling advanced with K3b, a graphical burning application for audio, video, and data discs, introduced during the series to simplify CD/DVD creation. Version 3.5, released on November 29, 2005, broadened accessibility to over 80 languages, incorporating usability improvements like ad-blocking in Konqueror and better removable media support. Maintenance continued through 3.5.10 on August 26, 2008, ensuring compatibility and bug fixes for enterprise and legacy users. Across the KDE 1 to 3 series, the project expanded significantly, growing from approximately 10 core applications in the initial releases to over 50 by the end of KDE 3, encompassing utilities for office, multimedia, and development. Source code lines increased from around 1 million in KDE 1 to roughly 2.6 million by KDE 3.1, reflecting broader contributions and feature depth. Cross-platform efforts began in earnest during KDE 3, with initial ports to Windows and macOS enabling portability beyond systems. DCOP laid groundwork for future architectures.

KDE 4 Series

The KDE 4 series marked a significant redesign of the , beginning with the release of 4.0 on January 11, 2008. This version introduced the Plasma desktop shell, which provided a flexible widget-based interface for panels, menus, and activities, along with the multimedia framework for cross-platform audio and video handling using backends like Xine. Additional innovations included for hardware abstraction and device integration, such as power management and network detection, and the initial integration of for semantic data storage and search capabilities across files and applications. However, KDE 4.0 faced substantial criticism for its immaturity, with frequent crashes in the Plasma workspace attributed to incomplete widget rendering and configuration issues, leading to user backlash and calls for forking the project to preserve KDE 3 stability. Subsequent releases from KDE 4.1 (July 29, 2008) through 4.3 (August 4, 2009) focused on maturation and stabilization of core components. These updates refined Plasma widgets for better responsiveness and reduced memory usage, while introducing activities as customizable desktop configurations to group related tasks and applets. The term "KDE Software Compilation" (KDE SC) first appeared in announcements starting with version 4.3.4 in December 2009. KDE 4.4, released on February 9, 2010, marked the first major release under this branding to emphasize its modular structure of platform, workspace, and applications, and included enhancements to KWin's compositing engine, such as native window tiling via screen-edge snapping and improved OpenGL support for smoother animations. The series progressed with KDE 4.5 (August 10, 2010) to 4.10 (February 6, 2013), emphasizing adaptability across devices. Plasma Netbook, introduced in 4.4 and refined in these versions, offered a touch-optimized interface with stacked application launchers and full-screen previews tailored for small screens and low-resolution displays. Similarly, Plasma Active emerged during this period, providing a gesture-based mobile shell built on Qt components for tablets and embedded systems, with features like declarative QML-based activities for convergence between desktop and touch interactions. KDE 4.11 (August 14, 2013) through 4.14 (August 20, 2014) prioritized performance optimizations, including reduced startup times for Plasma and better resource management in KWin, culminating in the final release that supported over 200 applications ranging from productivity tools to multimedia editors. Throughout its run, the KDE 4 series encountered ongoing challenges, particularly early Plasma instability that prompted widespread user complaints and delayed adoption by distributions. Comprising 14 feature releases from 4.0 to 4.13, followed by the concluding 4.14, the codebase expanded significantly, reaching approximately 10 million lines by the end, reflecting contributions from hundreds of developers on modular Qt-based frameworks.

Transition and Discontinuation

The decision to discontinue the monolithic Software Compilation ( SC) was announced in 2013, driven by the recognition that its bundled release model had led to bloat from unnecessary dependencies and hindered independent development paces among components. By early 2014, developers emphasized that the Plasma Workspaces, Development Platform, and Applications were evolving at different speeds, making synchronized releases inefficient. Consequently, SC 4.14, released on August 20, 2014, marked the final bundled version, focusing on stability and incremental improvements across its over 200 applications. The new modular structure emerged with KDE 5 in 2014, separating the project into three independent entities: KDE Frameworks 5 for modular libraries released quarterly, for the with feature releases every 4-6 months, and KDE Applications (later renamed in 2022) with releases approximately every three months. The inaugural releases included Frameworks 5.0 on July 7, 2014, and Plasma 5.0 on July 15, 2014, both built on Qt 5 to enable cross-platform flexibility and reduced bloat by allowing developers to adopt only required modules. This shift eliminated the need for a unified "compilation" term, as components could now advance autonomously without compatibility constraints from a single release cycle. Post-split milestones highlighted the structure's longevity and evolution. The Plasma 5 series progressed from 5.0 in 2014 to its final feature release, 5.27, on February 14, 2023, incorporating refinements like enhanced theming and performance optimizations. The transition to the next generation occurred in 2024, with Frameworks 6.0 and Plasma 6.0 both releasing on February 28, 2024, leveraging Qt 6 for modern and broader device support. By 2025, had matured into quarterly bundles, with the latest, 25.08, released on August 14, 2025, encompassing over 180 programs and libraries. This modular approach facilitated faster innovation by decoupling release schedules, enabling targeted advancements such as comprehensive Wayland protocol support in Plasma 5.20 on October 13, 2020, which included operational clipboard utilities and screencasting without monolithic overhead. Independent versioning further alleviated compatibility burdens, allowing applications to integrate newer features while Frameworks and Plasma addressed foundational changes separately, ultimately supporting a growing ecosystem of over 200 applications by 2025.

Development

Source Code and Collaboration

The source code for the KDE Software Compilation was managed through a series of version control systems to facilitate collaborative development. Initially, from 1998 to 2005, the project relied on the Concurrent Versions System (CVS), which supported the early releases including KDE 1 through parts of the KDE 3 series. In May 2005, KDE completed a major migration to Subversion (SVN), converting the entire repository in a 38-hour process that preserved all historical commits dating back to the first import in 1997; this shift improved branching, directory handling, and atomic commits for ongoing KDE 3 maintenance and the impending KDE 4 development. By 2009, during the KDE 4 era, KDE began transitioning to Git, starting with individual projects like Amarok and gradually adopting it project-wide for its distributed nature and offline capabilities, with repositories hosted on KDE's servers and later centralized at invent.kde.org. Collaboration on the KDE Software Compilation followed an open-source model coordinated by e.V., a non-profit organization founded in 1997 to provide legal and financial support to the global community of volunteers. Thousands of contributors participated via asynchronous tools such as mailing lists for discussions and issue resolution, IRC channels for real-time coordination, and platforms like Review Board for patch submissions and feedback, ensuring modular development across repositories such as kdelibs (core libraries) and kdebase (essential applications and infrastructure). This distributed approach emphasized and incremental contributions, allowing developers worldwide to work on isolated components while maintaining overall integration. To maintain code quality, the community employed the Krazy tool, a static analysis suite designed to detect common errors, style violations, and potential bugs in C++ and related codebases specific to frameworks. For building and packaging, adopted starting with the 4 series in 2008, replacing the GNU autotools system to simplify cross-platform compilation on , Windows, and macOS; 's declarative syntax enabled more reliable dependency management and generated native build files for various IDEs. Security practices included regular community-driven audits of the codebase, with vulnerabilities reported and patched through dedicated channels. By the conclusion of the KDE 4 series around 2014, the project had cultivated a robust with hundreds of active monthly developers and thousands of total contributors, reflecting steady growth from its origins. Localization efforts, handled by dedicated L10n teams, supported translations into approximately 90 languages, broadening and fostering international participation in refining applications and documentation.

Release Management

The KDE Software Compilation followed a disciplined approach to coordinate updates across its integrated , libraries, and applications, ensuring compatibility and stability from its in 1998 until its discontinuation in 2014. Releases operated on an approximate six-month cycle for major versions, exemplified by KDE 3.0 in 2002 and KDE 3.1 in 2003, supplemented by incremental bugfix updates released every 1-2 months to address stability issues without introducing new features. To prepare for each major release, a feature freeze was enforced roughly two months in advance, allowing developers to focus solely on polishing and bug fixes, followed by community-driven beta testing phases where pre-release tarballs were distributed for feedback and validation. Distinctions existed between major releases, such as 1.0 and 2.0, which introduced groundbreaking features often tied to Qt library upgrades, and standard releases like 4.5, which refined existing functionality; however, all were synchronized across KDE SC components to preserve interoperability and ease adoption by distributors. The KDE Release Team oversaw the entire process, tagging stable versions in the source code repository, generating source tarballs for distribution, and issuing official announcements on kde.org that included detailed changelogs and digest summaries of changes. This pre-split synchronization emphasized (ABI) stability within each series, enabling long-term compatibility for third-party developers and users; notably, the KDE 4.x series upheld API and ABI consistency for six years from 2008 to 2014. After the KDE SC's transition and discontinuation, subsequent projects like adopted a quarterly release cadence to accelerate modular development.

Scale and Metrics

The KDE Software Compilation demonstrated substantial growth in codebase size throughout its development. KDE 1 in 1998 comprised approximately 1 million lines of code, mainly in C++. This expanded to around 4-5 million lines by KDE 3.5 in 2007, incorporating contributions in Python and alongside C++. By KDE 4.14 in 2014, the compilation peaked at roughly 10-12 million lines of code across its modules. Contributor involvement scaled dramatically, reflecting the project's increasing maturity and global appeal. In the early 2000s, around 100 developers were actively contributing, as seen during key events like the 2003 KDE meeting. By 2014, the community had grown to over 2,000 participants, with steady increases in both total and new contributors tracked monthly since 1997. Approximately 20% of the code stemmed from paid developers supported by KDE e.V. or corporate sponsors such as , which employed several KDE developers for initiatives like integration. The number of applications bundled in the compilation also proliferated, underscoring its evolution into a comprehensive desktop suite. KDE 2 featured 20-30 core applications, focusing on basic utilities and tools. This grew to over 150 by KDE 4, spanning categories like (e.g., Amarok), productivity (e.g., KOffice), utilities (e.g., Dolphin file manager), and games (e.g., KPatience). Additional metrics highlight the compilation's reach and . Translation efforts supported approximately 90 languages by 2014, enabling broad . Download statistics indicated millions of users adopting KDE SC through distributions like , contributing to its widespread deployment.

Implementation

Architectural Foundations

The KDE Software Compilation (KDE SC) employed a layered to ensure and reusability across its components. At the base level, the KDE Platform provided foundational libraries for core functionalities such as networking, I/O operations, and elements, serving as a unified development framework for applications. Middleware layers facilitated (IPC) through mechanisms like DCOP in earlier iterations and its successor in KDE 4, enabling seamless interaction between processes and services. The user-facing layer centered on the Plasma shell, which managed the , while a robust plugin system—leveraging frameworks like KParts—allowed for extensibility, permitting developers to add or customize components without altering core code. Integration within KDE SC adhered to component-based principles, promoting and shared resources to enhance . Configurations were centralized using KConfig, a system that stored application settings in a unified, hierarchical format accessible across components, reducing redundancy and ensuring consistent user experiences. The architecture adopted an event-driven model inherited from Qt, utilizing for asynchronous communication between objects, which facilitated responsive interactions in both single-process and distributed scenarios. A pivotal architectural shift occurred with the KDE 4 series, introducing QGraphicsView as the rendering engine for Plasma widgets, which supplanted the rigid panel-based structure of prior versions with a more fluid, scalable canvas supporting and dynamic layouts. This change enabled adaptive interfaces, such as composited desktops and widget stacking, improving visual flexibility. Additionally, the introduction of the semantic layer provided an RDF-based metadata framework for resource description and querying, allowing applications to annotate and retrieve data semantically, thereby supporting advanced features like intelligent search and file tagging integrated across the desktop. While primarily designed for the X11 windowing system to leverage environments, KDE SC incorporated portability considerations from its inception, with early support for Microsoft Windows and macOS enabled through Trolltech's (later Qt Company) cross-platform Qt ports. These efforts, culminating in KDE 4, abstracted platform-specific dependencies—such as hardware access via —allowing compilation and partial functionality on non-Linux systems, though full desktop features like Plasma remained optimized for X11.

Core Technologies

The KDE Software Compilation (KDE SC) relied on the Qt framework as its primary foundation for graphical user interfaces, networking, and XML processing. Early versions, such as KDE 3, were built on Qt 3, which provided cross-platform widgets, event handling, and basic input/output capabilities essential for desktop applications. With the release of KDE 4 in 2008, the project transitioned to Qt 4, leveraging its enhanced performance, improved multimedia support, and reduced memory footprint to enable more advanced visual effects and hardware acceleration. Qt's networking module formed the basis for KDE's KIO (KDE Input/Output) system, which implemented "slaves"—modular protocol handlers that enabled transparent access to virtual filesystems, such as remote FTP servers or archived files, treated as local directories. KDE extended Qt with specialized libraries to enforce consistent user experiences and facilitate component reuse. The KParts library provided a component embedding framework, allowing applications to integrate reusable "parts" like document viewers or text editors seamlessly; for instance, Konqueror's multi-pane interface embedded file previews and web views using KParts. KDELibs, the core library collection, standardized user interface elements such as dialogs and toolbars while supporting through gettext-based i18n functions, enabling efficient translation of strings and handling of locale-specific formatting. For multimedia, offered an abstraction layer that decoupled applications from backend engines like or Xine, allowing developers to implement audio and video playback without platform-specific code. Similarly, served as a layer, providing device detection, , and storage querying independent of the underlying operating system, such as through HAL or UDisks backends. Additional foundational components enhanced system integration and aesthetics. In KDE 4, replaced the earlier DCOP (Desktop COmmunication Protocol) for , offering a more flexible, system-wide message bus that supported and broadcast interactions across applications. Strigi powered by rapidly indexing files and extracting metadata, using a low-memory daemon to crawl directories and support queries via a pluggable analyzer architecture. The Oxygen style defined KDE's default theming, applying a clean, semi-transparent aesthetic to widgets, icons, and window decorations for visual coherence across the desktop. Over time, KDE SC evolved to incorporate modern web and graphics technologies. KDE 4 integrated QtWebKit, derived from the engine, as an optional rendering backend to improve web compatibility and standards support in browsers like , addressing limitations in the original KHTML implementation. By 2014, with the maturation of KDE 4.14 and the transition toward Plasma 5, the window manager fully supported OpenGL-based for smooth animations, transparency effects, and handling, enhancing desktop fluidity on capable hardware.

Packages and Applications

The KDE Software Compilation (KDE SC) encompasses a wide array of packages and applications designed to provide a cohesive and productivity suite for users on systems. At its core, KDE SC integrates essential components for desktop functionality with a diverse set of user-facing applications, all built upon shared libraries to ensure seamless interoperability. By the release of KDE SC 4.14 in 2014, the compilation included over 200 actively maintained applications, ranging from system utilities to specialized tools, which could be installed via distribution-specific meta-packages such as kde-full for a complete setup, kde-standard for a balanced selection, or kde-plasma-desktop for a minimal base installation. Central to KDE SC are the core packages that form the foundation of the desktop experience. The KDE Workspace package provides the Plasma desktop shell, the compositing window manager for handling window decorations and effects, and KScreensaver for screen locking and power management features. Complementing this is the KDE Runtime (part of the KDE Development Platform), which supplies shared libraries and services essential for executing and integrating applications, including components like Phonom for multimedia backend abstraction and for . These core elements ensure that applications launch efficiently and adhere to consistent behaviors across the environment. In the realm of productivity, KDE SC offers robust tools for document handling and communication. serves as a versatile document viewer supporting PDF, , and other formats with advanced annotation capabilities. The , forked from the earlier KOffice project in December 2010, provides office applications including Words for word processing, Sheets for spreadsheets, and Stage for presentations, emphasizing open standards like ODF. For email and , KMail functions as a feature-rich client with support for IMAP, POP3, and integration with Akonadi for contact and calendar synchronization. Multimedia and utility applications enhance everyday tasks within KDE SC. Amarok acts as a powerful music player with library management, podcast support, and dynamic playlist generation. K3b offers a comprehensive CD and DVD burning tool, supporting data, audio, and video disc creation with drag-and-drop interfaces. Dolphin, introduced in KDE 4 as the primary , replaced Konqueror's file-handling role with a modern dual-pane view, tagging support, and preview thumbnails, while maintaining for embedded uses. Graphics and web-related tools round out the compilation's offerings. , a professional digital painting application, emerged prominently around 2010 with advanced brush engines and layer support tailored for artists. remains a hybrid and universal viewer, leveraging for rendering and supporting plugins for extended functionality. These applications, along with others like Gwenview for image viewing, exemplify KDE SC's emphasis on modularity and shared frameworks, such as KActions, which standardize menu structures and user interactions across the suite for consistent usability.

Licensing and Legacy

Licensing Model

The KDE Software Compilation (KDE SC) primarily utilized the GNU General Public License version 2 or later (GPL-2.0-or-later) for most of its source code, a practice established with the release of KDE 1.0 in 1998 to ensure protection and encourage collaborative development. Libraries within the Platform, however, were licensed under the GNU Lesser General Public License version 2.1 or later (LGPL-2.1-or-later) to facilitate dynamic linking with the Qt toolkit, which was initially available under the proprietary-friendly Q Public License (QPL) before 2000. To safeguard Qt's availability for projects like , the KDE Free Qt Foundation was established in 1998, securing special licensing rights from Trolltech to maintain open access in case of discontinuation. Specific components of the KDE SC adhered to tailored licenses to balance openness and reusability. Applications, such as those in the productivity and multimedia suites, fell under the GPL-2.0-or-later to enforce strong for end-user software. Platform libraries and frameworks used LGPL-2.1-or-later, permitting integration with non-free code where necessary while preserving source access. Documentation was licensed under the GNU Free Documentation License version 1.2 or later (FDL-1.2-or-later), allowing derivative works with attribution and share-alike requirements. Artwork, including themes and icons, employed the Attribution-ShareAlike license (CC-BY-SA), promoting communal contributions while ensuring modifications remained openly shared. The licensing model evolved to address compatibility and enforcement needs. In September 2000, Trolltech dual-licensed Qt under the GPL alongside the QPL, resolving prior concerns about proprietary dependencies and fully aligning KDE SC with principles. The project allows GPL version 3 or later (GPL-3.0-or-later) for approved components, enhancing protections against threats and hardware restrictions as outlined in the updated GPL. The KDE e.V., as the project's legal entity, enforced compliance through the Fiduciary Licensing Agreement (FLA), an optional contributor tool that assigned copyrights to the organization for streamlined relicensing decisions and violation defense without full transfer. Distribution of KDE SC emphasized open access, with official source tarballs provided freely via the KDE website for compilation and modification under the respective licenses. Binary packages were distributed through distributions and independent builds, all adhering to the core open-source terms without proprietary elements in the standard compilation.

Impact and Successors

The KDE Software Compilation significantly influenced the development of free and open-source desktop environments by establishing a model for integrated, customizable software suites that prioritized user productivity and extensibility. Founded in as one of the earliest comprehensive free desktops built on the Qt framework, it set precedents for collaboration between graphical toolkits and applications, indirectly shaping competitors like , which emerged in response to Qt licensing concerns but later adopted similar integration strategies. Its innovations, such as the Activities feature introduced in Plasma workspaces, enabled task-specific virtual desktops with custom widgets and configurations, inspiring modern workflow tools that separate personal, work, and creative environments to enhance focus and efficiency. The compilation powered key distributions, including as its default environment and the KDE Spin, which leveraged its full suite to deliver polished user experiences and contributed to broader adoption in enterprise and consumer settings. By 2014, commanded a substantial share of the desktop market, estimated at around 10% among users based on usage analytics from that period, underscoring its role in elevating free software's viability for everyday computing. KDE's community legacy endures through KDE e.V., the non-profit organization founded in 1997, which has expanded to include over 100 active members coordinating global contributions, events, and funding. Educational outreach remains a cornerstone via the KDE Education project, offering specialized applications like Kig for geometry and for interactive globes to support learning in schools and universities worldwide. Economically, the compilation's reliance on Qt fostered growth in The Qt Company, creating employment opportunities in cross-platform development and sustaining an ecosystem that powers devices from simulations to infotainment systems. As of 2025, the direct successors to the Software Compilation operate under the unified " Projects" branding, emphasizing modular yet cohesive releases: serves as the latest stable (released October 2025), providing a refined interface for diverse hardware; (November 2025) delivers foundational libraries for application development across platforms; and (August 2025) bundles over 180 updated applications for and . This structure maintains the compilation's bundled ethos through optional meta-packages in distributions, ensuring seamless integration while allowing flexibility. The compilation's model continues to drive relevance, with a robust user base sustained by editions like —built on LTS with continuous KDE updates—and KDE, which attract millions of users seeking stable, feature-rich desktops in 2025. The 2014 shift from monolithic releases to this modular approach preserved KDE's influence without fragmenting its core vision.

References

  1. https://timeline.kde.org/
  2. https://kde.org/announcements/4/4.14.0/
  3. https://techbase.kde.org/Getting_Started/Sources/en
  4. https://userbase.kde.org/History_of_KDE/en
  5. https://linuxreviews.org/KDE
  6. https://kde.org/presspage/
  7. https://dot.kde.org/2010/02/08/kdeorg-relaunched-software-compilation-44/
  8. https://dot.kde.org/2009/11/24/repositioning-kde-brand/
  9. https://20years.kde.org/book/20yearsofKDE.pdf
  10. https://kde.org/announcements/1-2-3/1.0/
  11. https://mail.kde.org/pipermail/kde-cvs-announce/2014/000147.html
  12. https://kde.org/announcements/4/4.0/
  13. https://develop.kde.org/products/frameworks/
  14. https://apps.kde.org/
  15. https://kde.org/announcements/4/4.5.0/plasma/
  16. https://community.kde.org/Promo/Guidance/Branding/Rebranding_KDE_v1.1.0
  17. https://www.gnu.org/philosophy/fsfs/rms-essays.pdf
  18. https://dot.kde.org/2012/11/27/15-years-kde-ev-early-years/
  19. https://ev.kde.org/whatiskdeev/
  20. https://kde.org/announcements/1-2-3/1.0-beta1/
  21. https://www.linuxjournal.com/article/3111
  22. https://kde.org/announcements/1-2-3/1.89/
  23. https://kde.org/announcements/1-2-3/2.0/
  24. https://dot.kde.org/2001/11/22/kde-222-released/
  25. https://kde.org/announcements/1-2-3/3.0/
  26. https://apps.kde.org/k3b/
  27. https://kde.org/announcements/1-2-3/3.5/
  28. https://kde.org/announcements/1-2-3/3.5.10/
  29. https://kde.org/info/1-2-3/3.1/feature_guide_12.html
  30. https://community.kde.org/Research/Nepomuk
  31. https://arstechnica.com/information-technology/2008/07/the-critics-are-wrong-kde-4-doesnt-need-a-fork/
  32. https://kde.org/announcements/4/4.1.0/
  33. https://kde.org/announcements/4/4.3.4/
  34. https://community.kde.org/Schedules/KDE4/4.4_Release_Goals
  35. https://kde.org/announcements/4/4.5.0/
  36. http://www.kde.com/announcements/4.4/
  37. http://www.linux-magazine.com/Online/Blogs/Off-the-Beat-Bruce-Byfield-s-Blog/How-I-Learned-to-Love-the-KDE-4-Series
  38. https://blog.cornelius-schumacher.de/2009/10/4273291-lines-of-code.html
  39. https://dot.kde.org/2013/09/04/kde-release-structure-evolves/
  40. https://kde.org/announcements/frameworks/5/5.0.0/
  41. https://dot.kde.org/2014/07/07/kde-frameworks-5-makes-kde-software-more-accessible-all-qt-developers/
  42. https://dot.kde.org/2014/07/15/plasma-5.0/
  43. https://kde.org/announcements/plasma/5/5.27.0/
  44. https://kde.org/announcements/megarelease/6/
  45. https://kde.org/announcements/gear/25.08.0/
  46. https://kde.org/announcements/plasma/5/5.20.0/
  47. https://dot.kde.org/2005/05/05/kdes-switch-subversion-complete/
  48. https://dot.kde.org/2009/07/20/kde-reaches-1000000-commits-its-subversion-repository/
  49. https://ev.kde.org/
  50. https://kde.org/support/mailinglists/
  51. https://community.kde.org/Infrastructure/Review_Board
  52. https://community.kde.org/Guidelines_and_HOWTOs/Code_Checking
  53. https://dot.kde.org/2007/02/22/road-kde-4-cmake-new-build-system-kde/
  54. https://dot.kde.org/2009/07/14/growth-metrics-kde-contributors/
  55. https://community.kde.org/KDE_Core/ISO_Codes
  56. https://community.kde.org/Schedules/KDE_3.0_Release_Schedule
  57. https://community.kde.org/Schedules/KDE_3.1_Release_Schedule
  58. https://community.kde.org/Schedules/KDE4/4.1_Release_Schedule
  59. https://dot.kde.org/2001/01/11/kde-21-release-schedule/
  60. https://community.kde.org/Frameworks/Git_Workflow
  61. https://blog.martin-graesslin.com/blog/2012/08/after-4-9-there-will-be-4-10/
  62. https://community.kde.org/Schedules/Frameworks
  63. http://aseigo.blogspot.com/2009/10/ah-stats.html
  64. https://dot.kde.org/2008/01/28/nokia-acquiring-trolltech/
  65. https://kde.org/announcements/4/4.0.5/
  66. https://planet.kde.org/kubuntu-news-2025-10-09-kubuntu-25-10-questing-quokka-released/
  67. https://techbase.kde.org/Development/Architecture/KDE4
  68. https://osnews.com/story/23630/kde-sc4-architecture-and-what-it-means-for-the-future/
  69. https://www.w3.org/2001/sw/sweo/public/UseCases/Nepomuk/Nepomuk.pdf
  70. https://arstechnica.com/information-technology/2008/01/kde-goes-cross-platform-with-windows-mac-os-x-support/
  71. https://techbase.kde.org/Development/Tutorials/Programming_Tutorial_KDE_4
  72. https://api.kde.org/legacy/3.5-api/kdelibs-apidocs/kparts/html/index.html
  73. https://techbase.kde.org/Development/Tutorials/KDE3/Makefile.am
  74. https://userbase.kde.org/Phonon/en
  75. https://develop.kde.org/docs/features/solid/
  76. https://techbase.kde.org/Development/Tutorials/Porting_to_D-Bus
  77. https://dot.kde.org/2007/04/11/road-kde-4-strigi-and-file-information-extraction/
  78. https://techbase.kde.org/Projects/Oxygen
  79. https://dot.kde.org/2006/07/12/webkit-ported-qt-4/
  80. https://techbase.kde.org/Projects/KWin/4.0-release-notes
  81. https://packages.debian.org/sid/kde-full
  82. https://kde.org/announcements/4/4.4.0/guide/
  83. https://dot.kde.org/2010/12/06/kde-announces-calligra-suite/
  84. https://develop.kde.org/docs/getting-started/kxmlgui/using_actions/
  85. https://community.kde.org/Policies/Licensing_Policy
  86. https://invent.kde.org/multimedia/kdenlive/-/blob/v24.08.1/LICENSES/GPL-2.0-only.txt
  87. https://wiki.qt.io/Qt_History
  88. https://kde.org/community/whatiskde/kdefreeqtfoundation/
  89. https://community.kde.org/Guidelines_and_HOWTOs/Licensing
  90. https://www.zdnet.com/article/good-news-for-kde-trolltech-adds-gpl-option-to-qt/
  91. https://ev.kde.org/rules/fla/
  92. https://piana.eu/kde-uses-ftfs-fla-to-receive-fiduciary-assignment-of-copyright/
  93. https://news.ycombinator.com/item?id=15873274
  94. https://linux.slashdot.org/story/04/03/23/2352216/kde-and-gnome-together-at-last
  95. https://www.howtogeek.com/be-more-productive-in-linux-with-kde-activities/
  96. https://www.everydaylinuxuser.com/2013/04/opensuse-real-alternative-to-ubuntu.html
  97. https://netrunner-mag.com/best-kde-distro-of-2014/
  98. https://blogs.kde.org/2014/02/09/kde-plasma-movies/
  99. https://apps.kde.org/categories/education/
  100. https://www.qt.io/resources/videos/kde-eco-achievements-impact-and-to-dos
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.