(style++) |
m (style++) |
||
Line 27: | Line 27: | ||
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. | 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. | ||
− | + | ;[[/Security Policy|Security Policy]] | |
+ | :How security problems can be reported to [mailto:security@kde.org security@kde.org] and how the security team responds to security issues. | ||
− | + | ;[[/Packaging Policy|Packaging Policy]] | |
+ | :This describes KDE's viewpoint on binary packages and elaborates the statement 'KDE provides source.' | ||
[[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.