Archive:Development/Software Engineering Framework (zh CN): Difference between revisions
No edit summary |
No edit summary |
||
Line 110: | Line 110: | ||
| currentState= | | currentState= | ||
在此审阅设计方案 | 在此审阅设计方案 | ||
* | * 邮件列表 | ||
* | * 项目维基 | ||
* face-to-face/BOF 会话和精神 | * face-to-face/BOF 会话和精神 | ||
* | * kde审阅 | ||
| getInvolved= | | getInvolved= | ||
* {{KDEML|kde-core-devel}}用于宣布KDE审阅的新条件。 | * {{KDEML|kde-core-devel}}用于宣布KDE审阅的新条件。 | ||
}} | }} | ||
KDE没有正式的官方设计审阅流程。一些设计审阅就是KDE审阅的一部分。将来也许要把它正规化并要求有一些设计文档。 | |||
== 文档 == | == 文档 == | ||
Line 135: | Line 135: | ||
}} | }} | ||
techbase.kde. | techbase.kde.org是个[http://www.mediawiki.org 维基(MediaWiki)网站],用于收集技术任务如教程,日程安排和项目信息。wiki.kde.org是个tiki-wiki网站,有类似功能,两个都再用,将来也许会合二为一。 | ||
Line 150: | Line 150: | ||
}} | }} | ||
KDE | KDE API文档是每日构建并放在http://api.kde.org。它也可以在本地通过IDE来创建。 | ||
可以从KDE源代码创建[http://www.kdedevelopers.org/node/3010 man pages]和[http://thread.gmane.org/gmane.comp.kde.devel.core/55578 QT帮助文档]。 | |||
Line 167: | Line 167: | ||
}} | }} | ||
用户文档是从模块文档目录(doc/)创建的,在http://docs.kde.org 可以找到。 | |||
meinproc | meinproc 是个KDE工具(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. | 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. | ||
Line 181: | Line 181: | ||
* KBugBuster | * KBugBuster | ||
| people= | | people= | ||
* [http://mattr.info:8080/blog/?s=bugzilla Matt Rogers] | * [http://mattr.info:8080/blog/?s=bugzilla Matt Rogers] 和KDE系统管理元团队维护KDE Bugzilla系统。 | ||
| getInvolved= | | getInvolved= | ||
* {{KDEML|kde-core-devel}} Discuss alternative bug trackers for KDE. | * {{KDEML|kde-core-devel}} Discuss alternative bug trackers for KDE. | ||
Line 195: | Line 195: | ||
}} | }} | ||
Bug tracking in | Bug tracking in KDE的缺陷追踪系统现在合并到Bugzilla 3.0。Work was recently merged on a transition to Bugzilla 3.0 from Bugzilla 2.16. 现在人有些清理工作但大部分已经完成了。 | ||
Bugzilla使用不便而且让新手感到畏惧。 | Bugzilla使用不便而且让新手感到畏惧。 | ||
Line 203: | Line 203: | ||
| name=静态代码检查 | | name=静态代码检查 | ||
| currentState= | | currentState= | ||
* [http://www.englishbreakfastnetwork.org/krazy/ Krazy] | * [http://www.englishbreakfastnetwork.org/krazy/ Krazy] 在EnglishBreakfastNetwork (EBN). | ||
* [http://www.coverity.com/ Coverity] is used to find possible sources of defects and suggested optimizations. Results are displayed per module as part of [http://ktown.kde.org/~dirk/dashboard/ Dirks Dashboard | * [http://www.coverity.com/ Coverity] is used to find possible sources of defects and suggested optimizations. Results are displayed per module as part of [http://ktown.kde.org/~dirk/dashboard/ Dirks Dashboard 构建]. | ||
| people= | | people= | ||
* [http://people.fruitsalad.org/adridg/bobulate/ Adriaan de Groot] | * [http://people.fruitsalad.org/adridg/bobulate/ Adriaan de Groot] | ||
Line 229: | Line 229: | ||
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. | 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. | ||
构建计划在下列平台上: | |||
* 微软视窗 | * 微软视窗 | ||
Line 241: | Line 241: | ||
| name=单元测试 | | name=单元测试 | ||
| currentState= | | currentState= | ||
[[Development/Tutorials/Unittests| | [[Development/Tutorials/Unittests|单元测试]]可以通过QTest框架创建。可以通过运行'<tt>make test</tt>'命令来运行测试。 | ||
| getInvolved= | | getInvolved= | ||
* [[Development/Tutorials/Unittests|Techbase单元测试教程]] | * [[Development/Tutorials/Unittests|Techbase单元测试教程]] | ||
Line 252: | Line 252: | ||
| name=质量测试 | | name=质量测试 | ||
| currentState= | | currentState= | ||
* | * 在其adopter/user社区 | ||
* [http://www.sqo-oss.eu/news/coverage/sqo-oss-project-launched-with-kde SQO-OSS] | * [http://www.sqo-oss.eu/news/coverage/sqo-oss-project-launched-with-kde SQO-OSS] | ||
| people= | | people= | ||
Line 268: | Line 268: | ||
* {{KDEML|kde-optimize}} mailing list coordinates optimizations in KDE. | * {{KDEML|kde-optimize}} mailing list coordinates optimizations in KDE. | ||
* Krazy and Coverity tools also include some optimization checks. | * Krazy and Coverity tools also include some optimization checks. | ||
* | * KDE宏用于优化通用算法。 | ||
| getInvolved= | | getInvolved= | ||
* {{KDEML|kde-optimize}} | * {{KDEML|kde-optimize}} | ||
Line 313: | Line 313: | ||
* Developers may do some research into requirements for applications based on User Research Profiles. | * Developers may do some research into requirements for applications based on User Research Profiles. | ||
| getInvolved= | | getInvolved= | ||
* http://bugs.kde.org | * http://bugs.kde.org 添加新需求。 | ||
* {{KDEML|kde-core-devel}} 商讨获取需求的新方法。 | * {{KDEML|kde-core-devel}} 商讨获取需求的新方法。 | ||
}} | }} | ||
Line 362: | Line 362: | ||
* [http://planetkde.org 博客] | * [http://planetkde.org 博客] | ||
* Conferences | * Conferences | ||
开发员和用户间的沟通: | |||
* [http://planetkde.org Blogs] to some extent (mainly early adopting users). | * [http://planetkde.org Blogs] to some extent (mainly early adopting users). | ||
* [http://forum.kde.org Forums] to some extent where the developer chooses to. | * [http://forum.kde.org Forums] to some extent where the developer chooses to. | ||
* [http://dot.kde.org News announcements] | * [http://dot.kde.org News announcements] | ||
用户间和用户开发员间沟通: | |||
* [http://forum.kde.org 论坛] | * [http://forum.kde.org 论坛] | ||
* {{KDEML|kde}} | * {{KDEML|kde}} 邮件列表 | ||
* #kde irc 通道. | * #kde irc 通道. | ||
| people= | | people= | ||
* [http://c133.org/blog/ Chris Lee] 管理planetkde.org | * [http://c133.org/blog/ Chris Lee] 管理planetkde.org | ||
| getInvolved= | | getInvolved= | ||
* Add your blog to planet kde if you contribute to KDE in some way, | * Add your blog to planet kde if you contribute to KDE in some way, 包括开发,测试,推广,翻译和文档等等。 | ||
}} | }} | ||
Line 381: | Line 381: | ||
| name=发布计划 | | name=发布计划 | ||
| currentState= | | currentState= | ||
* | * 在[[Schedules|计划栏目]]维护。 | ||
| people= | | people= | ||
* | * | ||
Line 387: | Line 387: | ||
* [http://www.kdedevelopers.org/blog/1451 Allen Winter] - KDEPIM发行协调官。 | * [http://www.kdedevelopers.org/blog/1451 Allen Winter] - KDEPIM发行协调官。 | ||
| getInvolved= | | getInvolved= | ||
* {{KDEML| | * {{KDEML|发布团队}} | ||
}} | }} | ||
Line 394: | Line 394: | ||
| name=功能计划 | | name=功能计划 | ||
| currentState= | | currentState= | ||
* [[Schedules/KDE4/4.1_Feature_Plan]] | * [[Schedules/KDE4/4.1_Feature_Plan|KDE 4.1 计划]] | ||
* [[Schedules/KDE4/4.2_Feature_Plan]] | * [[Schedules/KDE4/4.2_Feature_Plan|KDE 4.2 计划]] | ||
| people= | | people= | ||
[https://mail.kde.org/mailman/listinfo/release-team KDE发行团队] | [https://mail.kde.org/mailman/listinfo/release-team KDE发行团队] | ||
Line 408: | Line 408: | ||
{{SEFBox | {{SEFBox | ||
| name= | | name=Downstream包装者和贡献 | ||
| currentState= | | currentState= | ||
* KDE3 & KDE4都由许多发行包。 | * KDE3 & KDE4都由许多发行包。 |
Revision as of 05:27, 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没有正式的官方设计审阅流程。一些设计审阅就是KDE审阅的一部分。将来也许要把它正规化并要求有一些设计文档。
文档
techbase.kde.org是个维基(MediaWiki)网站,用于收集技术任务如教程,日程安排和项目信息。wiki.kde.org是个tiki-wiki网站,有类似功能,两个都再用,将来也许会合二为一。
Current State | People |
|
|
Get Involved | Alternative Tools |
|
|
KDE API文档是每日构建并放在http://api.kde.org。它也可以在本地通过IDE来创建。
Current State | People |
|
Unknown |
Get Involved | Alternative Tools |
|
n/a |
用户文档是从模块文档目录(doc/)创建的,在http://docs.kde.org 可以找到。
meinproc 是个KDE工具(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的缺陷追踪系统现在合并到Bugzilla 3.0。Work was recently merged on a transition to Bugzilla 3.0 from Bugzilla 2.16. 现在人有些清理工作但大部分已经完成了。
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.
构建计划在下列平台上:
- 微软视窗
- 苹果OS
- FreeBSD 6 (gcc)
- FreeBSD 7 (gcc)
- Solaris (S10, S11);SPARC和AMD64上
Current State | People |
单元测试可以通过QTest框架创建。可以通过运行'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 |
|
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 |
开发人员可以通过下列方式沟通: 开发员和用户间的沟通:
用户间和用户开发员间沟通: |
|
Get Involved | Alternative Tools |
|
n/a |
发布
Current State | People |
|
|
Get Involved | Alternative Tools |
n/a |
Current State | People |
Get Involved | Alternative Tools |
|
|
现在techbase用于讨论未来计划,但也许还有更好的办法。
Current State | People |
|
Unknown |
Get Involved | Alternative Tools |
|
n/a |
主题和翻译
Current State | People |
|
|
Get Involved | Alternative Tools |
n/a |
其他美工事宜见 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 |
无 |