KDE uses a central online repository to store our Source Code and to track changes made to the code. Currently, KDE is in the middle of migrating our main repository from Subversion (svn) to Sources/Git/Git, so some software modules currently live in Git while others are still only available from Subversion. This means you will need to become familiar with both systems.
For more information on using Git in KDE, please see the KDE Git page.
For more information on using Subversion, please see the following pages which may be outdated with regards to which modules live in SVN:
There are three main ways of doing this:
Note that Checkout has a different meaning in Git than it does in Subversion.
Within the KDE Source Repository the code is organized in Projects and Modules. There are also a number of high-level groupings of the Modules.
The KDE Support group is a set of tools and libraries that have been developed by KDE and that various KDE modules depend upon but are not themselves dependent on the KDE Development Platform. These libraries can thus be used by non-KDE applications without having to rely on KDE as well.
The KDE Software Compilation (aka KDE SC) is an informal term covering all the KDE Software which is released together on the regular KDE Release Cycle.
The KDE Development Platform group is defined as those KDE Modules that are required to run a KDE Application, i.e. the core libraries and runtime dependencies.
The KDE Workspace group (aka Plasma) is defined as those KDE Modules that are needed to run a workspace, such as the Desktop or Netbook. This group is not needed to run a KDE Application under another workspace such as Gnome or Windows.
The KDE Applications group is defined as those KDE modules built on the KDE Development Platform that are hosted by the KDE infrastructure and are released as part of the regular KDE Release Cycle, i.e. they are part of the KDE SC.
The KDE Extragear group is defined as those applications built on the KDE Development Platform that are hosted by the KDE infrastructure and have a stable release but are not part of a KDE Module and are not released as part of the regular KDE Release Cycle, i.e. they are not part of the KDE SC.
The KDE Playground group is defined as those applications built on the KDE Development Platform that are hosted by the KDE infrastructure but have not yet had a stable release and may never be released.
The KDE Review group is defined as those applications that are being reviewed for inclusion in a KDE Module or KDE Extragear, usually moving over from KDE Playground.