Archive:Development/Software Engineering Framework (zh CN): Difference between revisions

From KDE TechBase
No edit summary
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Template:I18n/Language Navigation Bar|Development/Software_Engineering_Framework}}
 


此网页的目的是总结KDE项目在软件工程方面所使用的工具和程序；覆盖所有编码工作。这包括错误修正，审查，测试，文档，需求等等。
此网页的目的是总结KDE项目在软件工程方面所使用的工具和程序；覆盖所有编码工作。这包括错误修正，审查，测试，文档，需求等等。
Line 7: Line 7:


== 开发工具 ==
== 开发工具 ==
{{SEFBox
{{SEFBox_(zh_CN)
| name=代码控制
| name=代码控制
| currentState=
| currentState=
Line 30: Line 30:




{{SEFBox
{{SEFBox_(zh_CN)
| name=联编系统
| name=联编系统
| currentState=
| currentState=
Line 46: Line 46:




{{SEFBox
{{SEFBox_(zh_CN)
| name=搜寻
| name=搜寻
| currentState=
| currentState=
Line 59: Line 59:


== 审阅 ==
== 审阅 ==
{{SEFBox
{{SEFBox_(zh_CN)
| name=审阅补丁(递交前)
| name=审阅补丁(递交前)
| currentState=
| currentState=
Line 67: Line 67:
* David Solbach和KDE系统管理组维护Plasma审阅公告栏的安装。
* David Solbach和KDE系统管理组维护Plasma审阅公告栏的安装。
| getInvolved=
| getInvolved=
* {{KDEML|kde-core-devel}}: 讨论KDE不定审阅和工具。
* {{KDEML|kde-core-devel}}: 讨论KDE补丁审阅和工具。
| altTools=
| altTools=
* Launchpad.net offers merge review/approval pre-merge [https://code.launchpad.net/~thumper/pqm/test-bzr-home/+merge/296/] [http://news.launchpad.net/cool-new-stuff/review-branch-merge-proposals-in-launchpad] [http://news.launchpad.net/cool-new-stuff/email-interface-to-code-review]
* Launchpad.net offers merge review/approval pre-merge [https://code.launchpad.net/~thumper/pqm/test-bzr-home/+merge/296/] [http://news.launchpad.net/cool-new-stuff/review-branch-merge-proposals-in-launchpad] [http://news.launchpad.net/cool-new-stuff/email-interface-to-code-review]
Line 89: Line 89:
这些议题在[http://thread.gmane.org/gmane.comp.kde.devel.core/54213 这里]有所讨论，但目前还没有一个定稿。所以没有提现在这里。
这些议题在[http://thread.gmane.org/gmane.comp.kde.devel.core/54213 这里]有所讨论，但目前还没有一个定稿。所以没有提现在这里。


{{SEFBox
{{SEFBox_(zh_CN)
| name=递交审阅(递交后)
| name=递交审阅(递交后)
| currentState=
| currentState=
Line 106: Line 106:




{{SEFBox
{{SEFBox_(zh_CN)
| name=设计审阅
| name=设计审阅
| currentState=
| currentState=
在此审阅设计方案
在此审阅设计方案
* mailing lists
* 邮件列表
* project wikis
* 项目维基
* face-to-face/BOF 会话和精神
* face-to-face/BOF 会话和精神
* kdereview
* kde审阅
| getInvolved=
| getInvolved=
* {{KDEML|kde-core-devel}}用于宣布KDE审阅的新条件。
* {{KDEML|kde-core-devel}}用于宣布KDE审阅的新条件。
}}
}}


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.
KDE没有正式的官方设计审阅流程。一些设计审阅就是KDE审阅的一部分。将来也许要把它正规化并要求有一些设计文档。


== 文档 ==
== 文档 ==


{{SEFBox
{{SEFBox_(zh_CN)
| name=技术文档
| name=技术文档
| currentState=
| currentState=
Line 135: Line 135:
}}
}}


techbase.kde.org is a [http://www.mediawiki.org 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.
techbase.kde.org是个[http://www.mediawiki.org 维基（MediaWiki）网站]，用于收集技术任务如教程，日程安排和项目信息。wiki.kde.org是个tiki-wiki网站，有类似功能，两个都再用，将来也许会合二为一。




{{SEFBox
{{SEFBox_(zh_CN)
| name=API文档
| name=API文档
| currentState=
| currentState=
Line 150: Line 150:
}}
}}


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.
KDE API文档是每日构建并放在http://api.kde.org。它也可以在本地通过IDE来创建。


It is possible to create [http://www.kdedevelopers.org/node/3010 man pages] and [http://thread.gmane.org/gmane.comp.kde.devel.core/55578 qthelp documentation] from kde sources.
可以从KDE源代码创建[http://www.kdedevelopers.org/node/3010 man pages]和[http://thread.gmane.org/gmane.comp.kde.devel.core/55578 QT帮助文档]。




{{SEFBox
{{SEFBox_(zh_CN)
| name=用户手册
| name=用户手册
| currentState=
| currentState=
Line 167: Line 167:
}}
}}


User documentation is generated from module doc/ folders and hosted on http://docs.kde.org.
用户文档是从模块文档目录（doc/）创建的，在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.
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 175: Line 175:
== 测试和质检 ==
== 测试和质检 ==


{{SEFBox
{{SEFBox_(zh_CN)
| name=缺陷跟踪
| name=缺陷跟踪
| currentState=
| currentState=
Line 181: Line 181:
* KBugBuster
* KBugBuster
| people=
| people=
* [http://mattr.info:8080/blog/?s=bugzilla Matt Rogers] and the KDE sysadmin team maintain the KDE bugzilla installation.
* [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 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的缺陷追踪系统现在合并到Bugzilla 3.0。Work was recently merged on a transition to Bugzilla 3.0 from Bugzilla 2.16.  现在人有些清理工作但大部分已经完成了。


Bugzilla使用不便而且让新手感到畏惧。
Bugzilla使用不便而且让新手感到畏惧。




{{SEFBox
{{SEFBox_(zh_CN)
| name=静态代码检查
| name=静态代码检查
| currentState=
| currentState=
* [http://www.englishbreakfastnetwork.org/krazy/ Krazy] hosted at EnglishBreakfastNetwork (EBN).
* [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 builds].
* [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 214: Line 214:
欢迎添加更多Krazy检查。详见http://websvn.kde.org/trunk/quality/.
欢迎添加更多Krazy检查。详见http://websvn.kde.org/trunk/quality/.


{{SEFBox
{{SEFBox_(zh_CN)
| name=联编测试
| name=联编测试
| currentState=
| currentState=
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.


Builds are planned for the following platforms:
构建计划在下列平台上：


* 微软视窗
* 微软视窗
Line 238: Line 238:




{{SEFBox
{{SEFBox_(zh_CN)
| name=单元测试
| name=单元测试
| currentState=
| currentState=
[[Development/Tutorials/Unittests|Unit tests]] may be written with the QTest framework. Tests can be run with the command '<tt>make test</tt>'.
[[Development/Tutorials/Unittests|单元测试]]可以通过QTest框架创建。可以通过运行'<tt>make test</tt>'命令来运行测试。
| getInvolved=
| getInvolved=
* [[Development/Tutorials/Unittests|Techbase单元测试教程]]
* [[Development/Tutorials/Unittests|Techbase单元测试教程]]
Line 249: Line 249:




{{SEFBox
{{SEFBox_(zh_CN)
| name=质量测试
| name=质量测试
| currentState=
| currentState=
* The early adopter/user community
* 在其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 263: Line 263:




{{SEFBox
{{SEFBox_(zh_CN)
| name=性能和优化
| name=性能和优化
| currentState=
| currentState=
* {{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 macros for optimization of common algorithms.
* KDE宏用于优化通用算法。
| getInvolved=
| getInvolved=
* {{KDEML|kde-optimize}}
* {{KDEML|kde-optimize}}
Line 277: Line 277:




{{SEFBox
{{SEFBox_(zh_CN)
| name=Accessibility和可用性
| name=Accessibility和可用性
| currentState=
| currentState=
Line 292: Line 292:




{{SEFBox
{{SEFBox_(zh_CN)
| name=研究
| name=研究
| currentState=
| currentState=
Line 307: Line 307:
== 市场和开拓期望 ==
== 市场和开拓期望 ==


{{SEFBox
{{SEFBox_(zh_CN)
| name=需求收集
| name=需求收集
| currentState=
| currentState=
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 Fill new wishlist items.
* http://bugs.kde.org 添加新需求。
* {{KDEML|kde-core-devel}} 商讨获取需求的新方法。
* {{KDEML|kde-core-devel}} 商讨获取需求的新方法。
}}
}}




{{SEFBox
{{SEFBox_(zh_CN)
| name=Promotion
| name=Promotion
| currentState=
| currentState=
Line 337: Line 337:




{{SEFBox
{{SEFBox_(zh_CN)
| name=社区管理
| name=社区管理
| currentState=
| currentState=
Line 354: Line 354:




{{SEFBox
{{SEFBox_(zh_CN)
| name=沟通管理
| name=沟通管理
| currentState=
| currentState=
Line 362: Line 362:
* [http://planetkde.org 博客]
* [http://planetkde.org 博客]
* Conferences
* Conferences
Developers communicate with users though
开发员和用户间的沟通：
* [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]
Users communicate with each other and developers through
用户间和用户开发员间沟通：
* [http://forum.kde.org 论坛]
* [http://forum.kde.org 论坛]
* {{KDEML|kde}} mailing list
* {{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, including development, testing, advocacy, translation, documentation etc.
* Add your blog to planet kde if you contribute to KDE in some way, 包括开发，测试，推广，翻译和文档等等。
}}
}}


== 发布==
== 发布==


{{SEFBox
{{SEFBox_(zh_CN)
| name=发布计划
| name=发布计划
| currentState=
| currentState=
* Maintained at [[Schedules]].
* 在[[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|release-team}}
* {{KDEML|发布团队}}
}}
}}




{{SEFBox
{{SEFBox_(zh_CN)
| name=功能计划
| name=功能计划
| currentState=
| currentState=
* [[Schedules/KDE4/4.1_Feature_Plan]]
* [[Schedules/KDE4/4.4_Feature_Plan|KDE 4.4 计划]]
* [[Schedules/KDE4/4.2_Feature_Plan]]
| people=
| people=
[https://mail.kde.org/mailman/listinfo/release-team KDE发行团队]
[https://mail.kde.org/mailman/listinfo/release-team KDE发行团队]
Line 407: Line 406:
现在techbase用于讨论未来计划，但也许还有更好的办法。
现在techbase用于讨论未来计划，但也许还有更好的办法。


{{SEFBox
{{SEFBox_(zh_CN)
| name=Downstream packagers and contributions
| name=Downstream包装者和贡献
| currentState=
| currentState=
* KDE3 & KDE4都由许多发行包。
* KDE3 & KDE4都由许多发行包。
Line 418: Line 417:
== 主题和翻译==
== 主题和翻译==


{{SEFBox
{{SEFBox_(zh_CN)
| name=美工
| name=美工
| currentState=
| currentState=
Line 433: Line 432:
There may be a need to create tutorials on how to create artwork for kde.
There may be a need to create tutorials on how to create artwork for kde.


{{SEFBox
{{SEFBox_(zh_CN)
| name=翻译
| name=翻译
| currentState=
| currentState=
Line 448: Line 447:


== 法律与支持 ==
== 法律与支持 ==
{{SEFBox
{{SEFBox_(zh_CN)
| name=KDE e.v. - 法律实体的代表
| name=KDE e.v. - 法律实体的代表
| currentState=
| currentState=
Line 457: Line 456:
}}
}}


{{SEFBox
{{SEFBox_(zh_CN)
| name=许可证
| name=许可证
| currentState=
| currentState=
Line 466: Line 465:
}}
}}


{{SEFBox
{{SEFBox_(zh_CN)
| name=赞助与合作
| name=赞助与合作
| currentState=
| currentState=

Latest revision as of 12:53, 23 June 2013


此网页的目的是总结KDE项目在软件工程方面所使用的工具和程序；覆盖所有编码工作。这包括错误修正，审查，测试，文档，需求等等。

目前所使用的KDE的工具集列出了其使用范围，已知的替代品，和优点/缺点。


开发工具

Template:SEFBox (zh CN)

Subversion 1.4是目前用于KDE的源代码管理系统，服务器位于法兰克福。另一个只读镜像位于anonsvn.kde.org。

移植到一个分布式的源代码管理系统已经提上议事日程，考虑GIT。关于这件事的讨论详见 kde-scm-interest邮件列表。 GIT可能会和其他工具，诸如REPO一起使用。


Template:SEFBox (zh CN)

CMake是目前KDE使用的构建工具。他是由kitware inc开发的自由软件，可用于多个KDE平台。

该工具被用于KDE4系列的联编，目前还没有替换的计划。CMake 2.6.2版本就是用来联编KDE 4.2的。


Template:SEFBox (zh CN)

LXR为KDE中的类和方法作出索引。他可以用来方便的找出适合使用一个类，并且找到他在整个程序里是如何被使用的。通常在重构是很有用。

审阅

Template:SEFBox (zh CN)

通常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]
  • 通过测试 [ ]
  • 没有明显安全顾虑 [ ]
  • 设计良好、易维护 [ ]
  • 等等

这些议题在这里有所讨论，但目前还没有一个定稿。所以没有提现在这里。

Template:SEFBox (zh CN)

检入过滤用于将相关键入内容发送给相关邮件列表。


Template:SEFBox (zh CN)

KDE没有正式的官方设计审阅流程。一些设计审阅就是KDE审阅的一部分。将来也许要把它正规化并要求有一些设计文档。

文档

Template:SEFBox (zh CN)

techbase.kde.org是个维基（MediaWiki）网站，用于收集技术任务如教程，日程安排和项目信息。wiki.kde.org是个tiki-wiki网站，有类似功能，两个都再用，将来也许会合二为一。


Template:SEFBox (zh CN)

KDE API文档是每日构建并放在http://api.kde.org。它也可以在本地通过IDE来创建。

可以从KDE源代码创建man pages和QT帮助文档。


Template:SEFBox (zh CN)

用户文档是从模块文档目录（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.

测试和质检

Template:SEFBox (zh CN)

Bug tracking in KDE的缺陷追踪系统现在合并到Bugzilla 3.0。Work was recently merged on a transition to Bugzilla 3.0 from Bugzilla 2.16. 现在人有些清理工作但大部分已经完成了。

Bugzilla使用不便而且让新手感到畏惧。


Template:SEFBox (zh CN)

欢迎添加更多Krazy检查。详见http://websvn.kde.org/trunk/quality/.

Template:SEFBox (zh CN)

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上


Template:SEFBox (zh CN)

It may be possible run run these tests automatically possibly on EBN or on Dirks dashboard.


Template:SEFBox (zh CN)

可以有一些统计数字，诸如千行错误率，缺陷修正率等。


Template:SEFBox (zh CN)

以后会向开发员提供一些教程，让他们能够优化代码。


Template:SEFBox (zh CN)


Template:SEFBox (zh CN)

市场和开拓期望

Template:SEFBox (zh CN)


Template:SEFBox (zh CN)


Template:SEFBox (zh CN)


Template:SEFBox (zh CN)

发布

Template:SEFBox (zh CN)


Template:SEFBox (zh CN)

现在techbase用于讨论未来计划，但也许还有更好的办法。

Template:SEFBox (zh CN)


主题和翻译

Template:SEFBox (zh CN)

其他美工事宜见 http://kde-look.org.

There may be a need to create tutorials on how to create artwork for kde.

Template:SEFBox (zh CN)

法律与支持

Template:SEFBox (zh CN)

Template:SEFBox (zh CN)

Template:SEFBox (zh CN)

Retrieved from "https://techbase.kde.org/index.php?title=Archive:Development/Software_Engineering_Framework_(zh_CN)&oldid=79986"