* SVN <tt>BUG:</tt> feature used to close bugs, and also notifies all bug subscribers of the commit.

* SVN <tt>BUG:</tt> feature used to close bugs, and also notifies all bug subscribers of the commit.

Line 139:

Line 128:

| currentState=

| currentState=

* http://techbase.kde.org

* http://techbase.kde.org

−

* http://wiki.kde.org

−

* http://wiki.koffice.org

| getInvolved=

| getInvolved=

* {{KDEML|kde-www}}

* {{KDEML|kde-www}}

Line 148:

Line 135:

}}

}}

−

techbase.kde.org is a [http://www.mediawiki.org MediaWiki] powered site used for collaborating on technical tasks such as tutorials, schedules, and project information. wiki.kde.org is a tiki-wiki site with the same function. Both are actively used. It might make sense to merge the two sites.

+

techbase.kde.org is a [http://www.mediawiki.org MediaWiki] powered site used for collaborating on technical tasks such as tutorials, schedules, and project information.

−

+

{{SEFBox

{{SEFBox

Line 166:

Line 152:

It is possible to create [http://www.kdedevelopers.org/node/3010 man pages] and [http://thread.gmane.org/gmane.comp.kde.devel.core/55578 qthelp documentation] from kde sources.

It is possible to create [http://www.kdedevelopers.org/node/3010 man pages] and [http://thread.gmane.org/gmane.comp.kde.devel.core/55578 qthelp documentation] from kde sources.

−

{{SEFBox

{{SEFBox

Line 173:

Line 158:

* http://userbase.kde.org

* http://userbase.kde.org

* [http://i18n.kde.org/docs/doc-primer/check-docs.html meinproc] is used to generate user documentation.

* [http://i18n.kde.org/docs/doc-primer/check-docs.html meinproc] is used to generate user documentation.

* [[Projects/KDE_Relicensing|Projects/KDE_Relicensing]] Effort to relicence KDE code to use version 3 of GNU GPL and LGPL. This work is unfinished but not still being performed. Many contributors are no longer contactable.

* [[Projects/KDE_Relicensing|Projects/KDE_Relicensing]] Effort to relicence KDE code to use version 3 of GNU GPL and LGPL. This work is unfinished but not still being performed. Many contributors are no longer contactable.

* [http://ev.kde.org/getinvolved/supporting-members.php Become a supporting member]

}}

}}

Latest revision as of 15:37, 29 October 2013

This page is intended to be a summary of the tools and processes used by the KDE
project for Software Engineering tasks, i.e. everything around coding
work. This includes bugfixing, review, testing, documentation,
requirements etc.

The current tool used by KDE should be listed along with the extent of
its use, known alternatives, and advantages/disadvantages.

In general KDE does not have a formal patch review policy for individual
patches. Some patches do get reviewed prior to committing to svn by the
relevant mailing lists or on the Review Board. This is the case for particularly large patches or patches by new developers.

As an official policy kdereview is used to review new applications and
new classes for kdelibs prior to inclusion in KDE trunk. See Application Lifecycle for some more details.

A drawback of this system is that not all reviewers report that they have reviewed the new content. It may make sense to have a checklist for reviewers to use, eg,

All new classes documented [x]

Private classes and d-pointers used where appropriate [x]

Passes all krazy checks [ ]

No obvious security concerns [ ]

Designed well/maintainable [ ]

etc...

This was discussed to some extent here, but has not yet been refined into a techbase page.

Bug tracking in KDE currently is managed using Bugzilla 3.0. Work was recently merged on a transition to Bugzilla 3.0 from Bugzilla 2.16. There is still cleanup work going on but most features of the previous Bugzilla installation already work.

There is interest in more build testing for KDE especially on non-linux platforms. Improvements include some standard ctest scripts that can be used to build and submit a dashboard result for kdelibs to CDash. This would be run on a cronjob for simplicity.

launchpad.net features a web-based tool called rosetta, which allows for easier fly-by translations. This is considered not to be useful as fly-by translators often do not follow guidelines or consistency rules when translating.

A Fiduicary Licence Agreement is available, which will allow KDE developers to optionally assign copyright of their contributions to KDE e.v. This would allow easier relicencing of contributors content in the event that KDE needs to move to another licence. It also allows the e.v. to more easily represent the work in the unlikely event of a court dispute involving KDE code.

KDE licencing policy allows commercial and non-commercial development and proprietry and non-proprietry development.

Projects/KDE_Relicensing Effort to relicence KDE code to use version 3 of GNU GPL and LGPL. This work is unfinished but not still being performed. Many contributors are no longer contactable.