Archive:Contribute (zh TW)

Revision as of 05:41, 19 September 2009 by Alisha (Talk | contribs)

Jump to: navigation, search


Contents

Contribute


這個頁面試圖提供KDE開發的不同方面,尤其是與程式設計有關的部分有一個總體的認識。KDE項目歡迎任何願意提供幫助的人

noframe
 
Note
有許多參與KDE開發的途徑,例如:
文件撰寫、翻譯、開發、可用性、無障礙、美工、產品推廣
Not a coder? See KDE's pages on how to get involved to see other ways you can help. Also see: Bugsquad!

新聞和郵件資源

KDE項目的總體發展方向是由實際參與工作的人決定的——並沒有一個單獨的最高層的計劃指導KDE將來會變成什麼樣子。

如果你想獲知現在正發生著什麼,那麼你可能會關心這些消息來源:

郵件列表
可能這是最好的獲知 KDE 正在開發著什麼的途徑。相關的文件可以在這裡獲得。
過濾後的討論
在你所感興趣的區域內收取 SVN 討論的通知。
KDE Commit-Digest
每週的 SVN 討論概述。
The Dot
KDE新聞網站。

開始程式設計

開始為 KDE coding是取決於找到需要修補的東西,並且修補它。你可能想查閱相關模塊的概述來幫助找到你在尋找的東西;一旦你修復了某些東西,你需要提交一個補丁。 如果你多次地這麼做,你可能需要申請一個SVN賬戶,那麼你將可以直接地修補相關的東西。

At the moment, there are two choices for development within KDE - you can work on KDE3, or KDE4. KDE3 is a good choice for bug fixing, however the main development work effort (and all new features) is on KDE4. This document mainly focuses on work in support of KDE4.

C++

KDE大部分是用C++寫成的。如果你不熟悉C++,你至少需要對它進行一些學習。有一些很好的關於C++的書,其中一本非常出色的教學叫做Bruce Eckel's "Thinking in C++",你可以自由而免費地下載它,同樣你也能將其打印成書面文件。在參與KDE之前,你不需要對它的所有東西都有個透徹的理解,但你至少需要懂得基本的語法和操作。

Qt

要想精通KDE程式設計,你應當了解Qt。如果你不熟悉Qt,你工作時應當參考包括Qt Reference Documentation在內的Qt相關指南。

If you are more into multimedia and videos for a start you might want to spend two amazing minutes on watching Building a Simple Help Documentation Browser with Qt4 Designer. If that got your attention you might also want to watch the video introduction Hello Qt by Mark Summerfield which is part of the Trolltech Developer Days 2006 presentations.

If you need a gentler introduction to Qt, or would just like an alternative view, then you may wish to look at the The Independent Qt Tutorial (Currently offline due to book contract).

If you prefer to learn Qt by reading a traditional book, take a look at Trolltechs book page. More suggestions on becoming familiar with Qt4 are available here as well.

KDE

一系列關於KDE技術的資訊可以在指南中查閱。

你同樣可以在FAQs中找到關於KDE程式設計的有用資訊。 這些資訊對KDE4來說可能同樣是有點過時了,然而其中的許多內容仍在被廣泛地應用著,甚至是在KDE之外。

你同樣可以閱讀KDE程式設計書籍

最後,但絕不是次要的,KDE與大量的類別(Application Programmer Interface,API)文件一起發布。 這些,同樣包括許多關於如何編寫與更新類別文件(the class documentation)的有用鏈接都在KDE API參考手冊中呈現。你同樣能在自己擁有的機器上生成這些,或者使用一個經常更新的在線版本—— The English Breakfast Network

關於以上步驟的更詳細的描述請參看我們的程式設計指導

參與除錯和品質保障

KDE中包含有許多應用程式,但並非每個程式都有一個維護者致力於管理漏洞和從總體上幫忙將相互關聯且可用的代碼轉換為精緻的程式。

如果你有興趣幫助KDE解決問題,但又不知從何處著手,成為一個KDE品質保障小組(the KDE Quality Team)的一員可能正是你所期望的——更多信息請查看品質保障小組的網站。注意,你不需要任何程式設計技能就可以參與進來。In particular develpers regurarly publish so-called Junior Jobs to encourage new contributions.

當然,你能在不成為KDE品質保障小組成員的情況下參與除錯——只需要在KDE漏洞跟踪系統上創建一個你自己的賬戶,並且開始搜索和整理這些漏洞。 再次強調,你並不必須擁有編程技能——那隻是幫助程式設計師用一貫的手法在程式中複製漏洞而已。

Bugsquad嘗試跟踪KDE軟體中的漏洞,並且確保被確認的漏洞被開發者們注意到。在Bugsquad中你不需要任何的編程知識;事實上,如果你不會編程,這是一種回饋某些東西給KDE社群的良好方法。

Getting Answers to Your Questions

If your question concerns KDE development, your options are pretty much the same general user ones, with some modifications:

  • Read the Developer FAQ. Many common developer questions have been answered in the KDE Developer FAQ
  • Search/browse KDE websites. A lot of questions can also be answered from the KDE websites, and the documentation included on it. You can search all the KDE websites on the homepage. In addition, you can browse the KDE developer website.
  • Search mailing lists. A lot of questions have already been answered on the KDE mailing lists, particular the lists kde-devel, kde2-porting, kde-core-devel, kde-games-devel, kfm-devel and koffice-devel. You can search these lists either at lists.kde.org. You should always search for your answer before asking questions on the mailing lists. When you ask a question on a mailing list you are emailing thousands of people -- please do this only if the answer is not available through a simple search.
  • Search engines. Do not forget about your favorite search engine. One of the best search engines is Google. With Google you can also search the great bulk of Usenet news sites, which is also particularly helpful, especially for general programming and gcc-related questions.
  • Ask on KDE mailing lists. If you still do not have an answer, try asking your question on one of the KDE mailing lists listed above.

A full list of KDE mailing lists is available here and here.


Historical Sources

KDE Traffic
Summary of the development mailing lists. KDE Traffic ran for 76 issues, from 10 March 2001 until 16 April 2004. The KDE Commit-Digest (described above) is its logical successor.



KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal