Archive:Development/Software Engineering Framework (zh CN): Difference between revisions
No edit summary |
No edit summary |
||
Line 51: | Line 51: | ||
http://lxr.kde.org | http://lxr.kde.org | ||
| people= | | people= | ||
KDE系统管理团队: | |||
* [http://wire.dattitu.de/authors/2-Dirk Dirk Müller] | * [http://wire.dattitu.de/authors/2-Dirk Dirk Müller] | ||
* [http://www.kdab.net/~dfaure/ David Faure] | * [http://www.kdab.net/~dfaure/ David Faure] | ||
Line 72: | Line 72: | ||
}} | }} | ||
通常KDE并不对单个补丁提供正规审阅策略。有些补丁在检入SVN之前就有邮件组审阅过了。这通常是针对一个大补丁或有新手开发的补丁。 | |||
As an official policy kdereview is used to review new applications and | As an official policy kdereview is used to review new applications and | ||
Line 95: | Line 92: | ||
| name=递交审阅(递交后) | | name=递交审阅(递交后) | ||
| currentState= | | currentState= | ||
* {{KDEML|kde-commits}} | * {{KDEML|kde-commits}} 邮件组记录所有KDE svn的检入。 | ||
* | * [http://commit-filter.org 检入过滤]用于过滤那些基于检入的相关检入。 | ||
* SVN <tt>CCMAIL:</tt> feature used to notify relevant mailing lists or individuals of specific commits. | * SVN <tt>CCMAIL:</tt> feature used to notify relevant mailing lists or individuals of specific commits. | ||
* 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 106: | Line 103: | ||
}} | }} | ||
检入过滤用于将相关键入内容发送给相关邮件列表。 | |||
Line 115: | Line 112: | ||
* mailing lists | * mailing lists | ||
* project wikis | * project wikis | ||
* face-to-face/BOF | * face-to-face/BOF 会话和精神 | ||
* kdereview | * kdereview | ||
| getInvolved= | | getInvolved= | ||
Line 134: | Line 131: | ||
* {{KDEML|kde-www}} | * {{KDEML|kde-www}} | ||
| people= | | people= | ||
* [[User:Danimo|Danimo]] | * [[User:Danimo|Danimo]] 是techbase.kde.org 的MediaWiki管理员 | ||
| futureWork= | | futureWork= | ||
}} | }} | ||
Line 144: | Line 141: | ||
| name=API文档 | | name=API文档 | ||
| currentState= | | currentState= | ||
* [http://www.stack.nl/~dimitri/doxygen/ Doxygen] | * [http://www.stack.nl/~dimitri/doxygen/ Doxygen]用于将源文件中的文字抽出产生API文档。 | ||
| getInvolved= | | getInvolved= | ||
* [[Development/Tutorials/API_Documentation| | * [[Development/Tutorials/API_Documentation|APIDOX教程]] 优化KDE API文档、 | ||
| people= | | people= | ||
* [http://www.kdedevelopers.org/blog/1451 Allen Winter] | * [http://www.kdedevelopers.org/blog/1451 Allen Winter], api.kde.org 管理员。 | ||
| altTools= | | altTools= | ||
* [http://labs.trolltech.com/blogs/2008/06/20/introducing-doxygen2qthelp-create-qch-files-from-doxygen-finally/ doxygen2qthelp] | * [http://labs.trolltech.com/blogs/2008/06/20/introducing-doxygen2qthelp-create-qch-files-from-doxygen-finally/ doxygen2qthelp] trolltech用来创建QT文档。 | ||
}} | }} | ||
Line 162: | Line 159: | ||
| currentState= | | currentState= | ||
* http://userbase.kde.org | * http://userbase.kde.org | ||
* [http://i18n.kde.org/docs/doc-primer/check-docs.html meinproc] | * [http://i18n.kde.org/docs/doc-primer/check-docs.html meinproc] 用于产生用户文档。 | ||
* {{KDEML|kde-docbook}} Records all SVN commits with the <tt>GUI</tt> magic word. | * {{KDEML|kde-docbook}} Records all SVN commits with the <tt>GUI</tt> magic word. | ||
| getInvolved= | | getInvolved= | ||
Line 200: | Line 197: | ||
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. | 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使用不便而且让新手感到畏惧。 | |||
Revision as of 03:49, 27 September 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 |
KDE系统管理队伍: | |
Get Involved | Alternative Tools |
Subversion 1.4是目前用于KDE的源代码管理系统,服务器位于法兰克福。另一个只读镜像位于anonsvn.kde.org。
移植到一个分布式的源代码管理系统已经提上议事日程,考虑GIT。关于这件事的讨论详见 kde-scm-interest邮件列表。 GIT可能会和其他工具,诸如REPO一起使用。
Current State | People |
Get Involved | Alternative Tools |
n/a |
CMake是目前KDE使用的构建工具。他是由kitware inc开发的自由软件,可用于多个KDE平台。
该工具被用于KDE4系列的联编,目前还没有替换的计划。CMake 2.6.2版本就是用来联编KDE 4.2的。
Current State | People |
KDE系统管理团队: | |
Get Involved | Alternative Tools |
n/a |
n/a |
LXR为KDE中的类和方法作出索引。他可以用来方便的找出适合使用一个类,并且找到他在整个程序里是如何被使用的。通常在重构是很有用。
审阅
Current State | People |
|
|
Get Involved | Alternative Tools |
|
通常KDE并不对单个补丁提供正规审阅策略。有些补丁在检入SVN之前就有邮件组审阅过了。这通常是针对一个大补丁或有新手开发的补丁。
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,
- 新加内容都有文档记录 [x]
- 私有类和d-指针正确合理使用 [x]
- 通过测试 [ ]
- 没有明显安全顾虑 [ ]
- 设计良好、易维护 [ ]
- 等等
这些议题在这里有所讨论,但目前还没有一个定稿。所以没有提现在这里。
Current State | People |
|
Unknown |
Get Involved | Alternative Tools |
|
检入过滤用于将相关键入内容发送给相关邮件列表。
Current State | People |
在此审阅设计方案
|
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.
文档
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使用不便而且让新手感到畏惧。
Current State | People |
|
|
Get Involved | Alternative Tools |
|
n/a |
欢迎添加更多Krazy检查。详见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:
- 微软视窗
- 苹果OS
- FreeBSD 6 (gcc)
- FreeBSD 7 (gcc)
- Solaris (S10, S11);SPARC和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 |
可以有一些统计数字,诸如千行错误率,缺陷修正率等。
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 |
|
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 |
主题和翻译
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 |
不祥 |
Current State | People |
|
Unknown |
Get Involved | Alternative Tools |
n/a |
无 |
Current State | People |
|
Unknown |
Get Involved | Alternative Tools |
n/a |
无 |