(add a link to the CMake Coding Style page) |
(add a link to the new minor point release policy page) |
||
(3 intermediate revisions by 2 users not shown) | |||
Line 22: | Line 22: | ||
;[[/Kdelibs Coding Style|Kdelibs Coding Style]] | ;[[/Kdelibs Coding Style|Kdelibs Coding Style]] | ||
:This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formating of the source code files it is recommended to make use of it. | :This document describes the recommended coding style for kdelibs. Nobody is forced to use this style, but to have consistent formating of the source code files it is recommended to make use of it. | ||
+ | |||
+ | ;[[/New_KDE_Library_API_Policy|Adding New Classes to kdelibs]] | ||
+ | :Recommendations on how to add new classes or libraries to kdelibs. | ||
;[[/CMake Coding Style|CMake Coding Style]] | ;[[/CMake Coding Style|CMake Coding Style]] | ||
:This document describes the recommended coding style for CMake files in KDE. | :This document describes the recommended coding style for CMake files in KDE. | ||
+ | |||
+ | ;[[/CMake and Source Compatibility|CMake and Source Compatibility]] | ||
+ | :Keeping future KDE releases CMake-compatible. | ||
+ | |||
+ | ;[[/CMake Commit Policy|CMake Commit Policies]] | ||
+ | :Rules to follow when considering a change to the CMake buildsystem. | ||
;[[/Binary Compatibility Issues With C++|Binary Compatibility Issues With C++]] ([http://developer.kde.org/documentation/other/binarycompatibility.html Original]) | ;[[/Binary Compatibility Issues With C++|Binary Compatibility Issues With C++]] ([http://developer.kde.org/documentation/other/binarycompatibility.html Original]) | ||
:A quick overview of issues with binary compatibility with C++. Keep this in mind while altering the API of kdelibs. | :A quick overview of issues with binary compatibility with C++. Keep this in mind while altering the API of kdelibs. | ||
− | |||
− | |||
− | |||
;[[/URI & XML Namespaces Policy|URI & XML Namespaces Policy]] | ;[[/URI & XML Namespaces Policy|URI & XML Namespaces Policy]] | ||
Line 48: | Line 54: | ||
:This describes KDE's viewpoint on binary packages and elaborates the statement 'KDE provides source.' | :This describes KDE's viewpoint on binary packages and elaborates the statement 'KDE provides source.' | ||
+ | ;[[/Minor_Point_Release_Policy|Point Release Policy]] | ||
+ | :Discusses KDE policies for minor point releases. | ||
[[Category:Policies]] | [[Category:Policies]] |
There are a couple of written and unwritten rules KDE developers usually adhere to. The following documents summarize some of these policies. The list is still incomplete. If you are interested in helping out with formulating the KDE policies or would like to discuss them please use the kde-policies mailing list which was created for this purpose.
These policies apply to KDE developers and it is expected that all persons with a KDE SVN account follow these policies. The SVN commit policy is the most important one. Persons working on libraries (kdelibs mostly, but central libraries in other SVN modules fall under this as well) should read the library documentation policy (and the apidox howto as well).
Whereas policies are normative for individual developers -- that is, they describe how developers must behave -- procedures describe how 'the KDE project' as a whole has chosen to behave. We describe what we will do under certain circumstances and why.