Archive:Development/Software Engineering Framework (zh CN): Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 479: | Line 479: | ||
{{SEFBox | {{SEFBox | ||
| name= | | name=赞助与合作 | ||
| currentState= | | currentState= | ||
* [http://ev.kde.org/supporting-members.php Supporters of KDE] contribute sponsorship money to KDE e.v. | * [http://ev.kde.org/supporting-members.php Supporters of KDE] contribute sponsorship money to KDE e.v. | ||
Revision as of 06:26, 13 February 2009
Development/Software_Engineering_Framework
Languages: عربي | Asturianu | Català | Česky | Kaszëbsczi | Dansk | Deutsch | English | Esperanto | Español | Eesti | فارسی | Suomi | Français | Galego | Italiano | 日本語 | 한국어 | Norwegian | Polski | Português Brasileiro | Română | Русский | Svenska | Slovenčina | Slovenščina | српски | Türkçe | Tiếng Việt | Українська | 简体中文 | 繁體中文
此网页的目的是总结KDE项目在软件工程方面所使用的工具和程序；覆盖所有编码工作。这包括错误修正，审查，测试，文档，需求等等。
目前所使用的KDE的工具集列出了其使用范围，已知的替代品，和优点/缺点。
开发工具
| Current State | People |
|
The kde sysadmin team: | |
| Get Involved | Alternative Tools |
Subversion 1.4 is currently used for source control management in KDE on a server hosted in Frankfurt. A separate server is used for access to the read-only mirror anonsvn.kde.org.
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. It is likely git will be used along with a tool such as repo.
| Current State | People |
| Get Involved | Alternative Tools |
|
n/a |
CMake is the build tool currently used by KDE. It is Free Software developed by kitware inc and available on multiple platforms supported by KDE.
This tool was chosen as the buildsystem for the KDE4 series, and there are no plans currently to migrate away from it. CMake version 2.6.2 will be required to build KDE 4.2 final.
| Current State | People |
|
The kde sysadmin team: | |
| Get Involved | Alternative Tools |
|
n/a |
n/a |
LXR indexes classes and methods used in KDE. This can be useful for finding examples of how to use a class, and finding all uses of a class while refactoring or updating API.
审阅
| Current State | People |
|
|
| Get Involved | Alternative Tools |
|
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. 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. 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.
| Current State | People |
|
Unknown |
| Get Involved | Alternative Tools |
|
The commit filter is used by several projects to forward all commits to the relevant mailing list.
| Current State | People |
|
Design review takes place on
|
Unknown |
| Get Involved | Alternative Tools |
|
n/a |
KDE does not have an offical design review process. Some design review takes place as part of the kdereview process. It may be possible to further formalise this or encourage design documentation.
文档
| Current State | People |
| |
| Get Involved | Alternative Tools |
|
n/a |
techbase.kde.org is a 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.
| Current State | People |
|
|
| Get Involved | Alternative Tools |
|
|
KDE API documentation is generated nightly and hosted on http://api.kde.org. It is also possible to generate the same documentation locally for use in an IDE for example.
It is possible to create man pages and qthelp documentation from kde sources.
| Current State | People |
|
Unknown |
| Get Involved | Alternative Tools |
|
n/a |
User documentation is generated from module doc/ folders and hosted on http://docs.kde.org.
meinproc is a KDE tool (written by Stephen Kulow which uses libxslt to transform docbook into (bzipped) html. At runtime kio_help opens that bzipped html and displays it to the user in khelpcenter.
http://userbase.kde.org is intended to be the primary source of user documentation on the web. Content will possibly be packaged for offline use in the future.
测试和质检
| Current State | People |
|
|
| Get Involved | Alternative Tools |
|
|
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.
Bugzilla can be difficult to use and daunting to newbies.
| Current State | People |
|
|
| Get Involved | Alternative Tools |
|
|
n/a |
Additional checks are always welcome for adding to Krazy. See http://websvn.kde.org/trunk/quality/.
| Current State | People |
|
|
| Get Involved | Alternative Tools |
|
n/a |
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.
Builds are planned for the following platforms:
- Windows
- MacOS
- FreeBSD 6 (gcc)
- FreeBSD 7 (gcc)
- Solaris (S10, S11) on SPARC and amd64
| Current State | People |
|
Unit tests may be written with the QTest framework. Tests can be run with the command 'make test'. |
Unknown |
| Get Involved | Alternative Tools |
|
n/a |
It may be possible run run these tests automatically possibly on EBN or on Dirks dashboard.
| Current State | People |
|
|
| Get Involved | Alternative Tools |
|
n/a |
It may be possible to obtain metrics such as bugs per kloc, defect injection rate etc.
| Current State | People |
|
Unknown |
| Get Involved | Alternative Tools |
|
n/a |
Tutorials may be provided in the future to help developers optimize their code.
| Current State | People |
|
|
| Get Involved | Alternative Tools |
|
n/a |
| Current State | People |
|
|
| Get Involved | Alternative Tools |
|
n/a |
Marketing and Expectations
| Current State | People |
|
Unknown |
| Get Involved | Alternative Tools |
|
n/a |
| Current State | People |
|
|
| Get Involved | Alternative Tools |
|
n/a |
| Current State | People |
|
|
| Get Involved | Alternative Tools |
|
n/a |
| Current State | People |
|
Developers communicate with each other through
Developers communicate with users though
Users communicate with each other and developers through |
|
| Get Involved | Alternative Tools |
|
n/a |
发布
| Current State | People |
|
|
| Get Involved | Alternative Tools |
|
n/a |
| Current State | People |
| Get Involved | Alternative Tools |
|
|
Currently techbase is used for feature planning but there may be better alternatives.
| Current State | People |
|
Unknown |
| Get Involved | Alternative Tools |
|
n/a |
Theming and Translations
| Current State | People |
|
|
| Get Involved | Alternative Tools |
|
n/a |
Additional contributed artwork is available on http://kde-look.org.
There may be a need to create tutorials on how to create artwork for kde.
| Current State | People |
|
Unknown |
| Get Involved | Alternative Tools |
|
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. |
法律与支持
| Current State | People |
|
Unknown |
| Get Involved | Alternative Tools |
|
N/A |
| Current State | People |
|
Unknown |
| Get Involved | Alternative Tools |
|
n/a |
N/A |
| Current State | People |
|
Unknown |
| Get Involved | Alternative Tools |
|
n/a |
N/A |