(→Current tool) |
(Add translation section.) |
||
| Line 116: | Line 116: | ||
== Marketing and expectations == | == Marketing and expectations == | ||
=== current process === | === current process === | ||
| − | The [https://mail.kde.org/mailman/listinfo/kde-promo KDE marketing team] manage marketing and promotion from official kde sources. | + | * The [https://mail.kde.org/mailman/listinfo/kde-promo KDE marketing team] manage marketing and promotion from official kde sources. |
| − | http://dot.kde.org is the community forum around promotional announcements. | + | * http://dot.kde.org is the community forum around promotional announcements. |
| − | http://www.kde.org/announcements is the official source of promotional announcements regarding KDE. | + | * http://www.kde.org/announcements is the official source of promotional announcements regarding KDE. |
| + | * Design and maintenance of KDE websites is organised on the [https://mail.kde.org/mailman/listinfo/kde-www kde-www mailing list] | ||
=== People === | === People === | ||
* [http://wadejolson.wordpress.com/ Wade Olsen] | * [http://wadejolson.wordpress.com/ Wade Olsen] | ||
* [http://troy-at-kde.livejournal.com/ Troy Unrau] | * [http://troy-at-kde.livejournal.com/ Troy Unrau] | ||
| + | * [http://nowwhatthe.blogspot.com/ Jos Poortvliet] | ||
| Line 192: | Line 194: | ||
=== People === | === People === | ||
[http://www.kdedevelopers.org/blog/531 Alexander Neundorf] | [http://www.kdedevelopers.org/blog/531 Alexander Neundorf] | ||
| + | |||
| + | == Translation == | ||
| + | === Current tools === | ||
| + | * http://i18n.kde.org/ is used for level of completion of translations in KDE. | ||
| + | * GNU gettext is used for translation in KDE. | ||
| + | * <tt>.po</tt> files are edited directly in KDE svn to update translations. | ||
| + | * A kde4 based translation client (lokalize) is being developed in kdesdk/. | ||
| + | * krazy includes sanity checks/plurals checking for translation. | ||
| + | |||
| + | |||
| + | === Alternative tools === | ||
| + | launchpad.net features a web-based tool called rosetta, which allows for easier fly-by translations. | ||
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.
Subversion 1.4 is used for source control management in KDE.
Dirk Muller and the kde sysadmin team maintain the KDE SVN servers.
There is interest in migrating to a distributed source control management tool, such as GIT. Discussion of this is taking place on the kde-scm-interest mailing list.
Bug tracking in KDE is managed using Bugzilla 2.x.
Matt Rogers and the kde sysadmin team maintain the KDE bugzilla installation.
There is work being done on a transition to Bugzilla 3.0, which provides some additional features.
David Solbach and the kde sysadmin team maintain the Plasma review-board installation.
Review-board may be suitable for adoption by more of the KDE project, or by individual modules.
Unknown
Unknown
Design review takes place on mailing lists/wikis and in face-to-face/BOF sessions at conferences and sprints.
techbase.kde.org is a mediawiki powered site used for collaborating on technical tasks such as tutorials, schedules, and project information.
Danimo is the mediawiki admin for techbase.kde.org.
krazy hosted at englishbreakfastnetwork is used for static code analysis.
Adriaan de Groot and Allen Winters maintain krazy.
Additional checks are always welcome for adding to krazy. See http://websvn.kde.org/trunk/quality/.
doxygen is used to generate api documentation from documentation strings in code. It is generated nightly and hosted on http://api.kde.org.
Allen Winters administers api.kde.org.
Unknown
doxygen is used to generate user documentation from module doc/ folders and is hosted on http://docs.kde.org.
techbase.kde.org is currently used for feature planning, specifically Schedules/KDE4/4.1_Feature_Plan etc.
The release team mailing list is used for release planning, and release plans maintained on techbase at Schedules.
http://lxr.kde.org is used for searching for existing use of classes in KDE.
Unit tests may be written with the QTest framework. Tests can be run with the command 'make test'.
Run the tests automatically. Possibly on EBN.
The early adopter/user community tests beta versions of KDE. Additionally some work is done by SQO-OSS on quality in KDE.
Adriaan de Groot and Paul Adams work on SQO-OSS and quality in KDE.
It may be possible to obtain metrics such as bugs per kloc, defect injection rate etc.
A community management group is being worked on.
The kde-artists team creates offical artwork for KDE. Additional contributed artwork is available on http://kde-look.org.
Tutorials on how to create artwork for kde?
CMake is the current KDE build tool.
launchpad.net features a web-based tool called rosetta, which allows for easier fly-by translations.
KDE TechBase 