There is interest in migrating to a distributed source control management tool, such as GIT. Discussion of this is taking place on the

+

[http://mail.kde.org/pipermail/kde-scm-interest kde-scm-interest]

+

mailing list.

+

| altTools=

+

* [http://git.or.cz/ git]

+

* [http://bazaar-vcs.org/ bazaar]

+

* [http://www.selenic.com/mercurial/ mercurial]

+

}}

−

=== Future work ===

−

There is work being done on a transition to Bugzilla 3.0, which provides some additional features.

−

=== Alternative tools ===

+

{{SEFBox

−

* Launchpad.net offers bug tracking via bugs.launchpad.net

+

| name=Identifier search

+

| currentState=

+

http://lxr.kde.org is used for searching for existing use of classes in KDE.

+

}}

−

== Patch review (pre commit) ==

+

−

=== Current tool ===

+

== Review ==

+

{{SEFBox

+

| name=Patch review (pre commit)

+

| currentState=

* [http://reviewboard.vidsolbach.de/ Review-board] used by plasma project. In KDE in general this process does not take place, except for some specific patches which may be sent to the relevant mailing list.

* [http://reviewboard.vidsolbach.de/ Review-board] used by plasma project. In KDE in general this process does not take place, except for some specific patches which may be sent to the relevant mailing list.

* trunk/kdereview is used to review major new features and new applications prior to inclusion in KDE trunk.

* trunk/kdereview is used to review major new features and new applications prior to inclusion in KDE trunk.

−

+

| people=

−

=== People ===

+

David Solbach and the kde sysadmin team maintain the Plasma review-board installation.

David Solbach and the kde sysadmin team maintain the Plasma review-board installation.

−

+

| futureWork=

−

=== Future work ===

+

Review-board may be suitable for adoption by more of the KDE project, or by individual modules.

Review-board may be suitable for adoption by more of the KDE project, or by individual modules.

The [http://mail.kde.org/mailman/listinfo/kde-artists kde-artists team] creates offical artwork for KDE. Additional contributed artwork is available on http://kde-look.org.

+

| people=

+

* [http://pinheiro-kde.blogspot.com/ Nuno Pinheiro]

+

| futureWork=

+

Tutorials on how to create artwork for kde?

+

}}

−

== Translation ==

+

−

=== Current tools ===

+

{{SEFBox

+

| name=Translation

+

| currentState=

* http://i18n.kde.org/ is used for level of completion of translations in KDE.

* http://i18n.kde.org/ is used for level of completion of translations in KDE.

* GNU gettext is used for translation in KDE.

* GNU gettext is used for translation in KDE.

Line 204:

Line 270:

* A kde4 based translation client (lokalize) is being developed in kdesdk/.

* A kde4 based translation client (lokalize) is being developed in kdesdk/.

* Krazy includes sanity checks/plurals checking for translation.

* Krazy includes sanity checks/plurals checking for translation.

−

+

| altTools=

−

+

−

=== Alternative tools ===

+

launchpad.net features a web-based tool called rosetta, which allows for easier fly-by translations.

launchpad.net features a web-based tool called rosetta, which allows for easier fly-by translations.

+

}}

Revision as of 13:15, 1 July 2008

This page is intended to be a summary of the tools 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.