Difference between revisions of "Contribute/ja"

Jump to: navigation, search
(Created page with "KDE へ貢献する方法として最も簡単なのが、[https://bugs.kde.org/ KDE バグ追跡システム] ('''Bugzilla''') から KDE の[http://userbase.kde.org/Asking_Ques...")
(Created page with "使っているアプリケーションがクラッシュした際、'''Dr Konqi''' が表示され、クラッシュについてレポートする手順を示します。詳細...")
Line 29: Line 29:
KDE へ貢献する方法として最も簡単なのが、[https://bugs.kde.org/ KDE バグ追跡システム] ('''Bugzilla''') から KDE の[http://userbase.kde.org/Asking_Questions#Reporting_KDE_Bugs バグを報告]することです。
KDE へ貢献する方法として最も簡単なのが、[https://bugs.kde.org/ KDE バグ追跡システム] ('''Bugzilla''') から KDE の[http://userbase.kde.org/Asking_Questions#Reporting_KDE_Bugs バグを報告]することです。
If the application you are using crashes then the '''Dr Konqi''' utility will appear and guide you through the process of reporting the crash.  Learn more by reading  [[Development/Tutorials/Debugging/How_to_create_useful_crash_reports|how to create useful crash reports]].
使っているアプリケーションがクラッシュした際、'''Dr Konqi''' が表示され、クラッシュについてレポートする手順を示します。詳細は[[Development/Tutorials/Debugging/How_to_create_useful_crash_reports|より良いクラッシュレポートを作成するには]]の記事を参照して下さい。
== Getting Started with Coding ==
== Getting Started with Coding ==

Revision as of 03:39, 8 September 2011

Other languages:
Ελληνικά • ‎English • ‎español • ‎suomi • ‎français • ‎galego • ‎日本語 • ‎한국어 • ‎Nederlands • ‎polski • ‎português do Brasil • ‎slovenčina • ‎中文(中国大陆)‎


このページは、KDE の様々な面を、プログラミング関係に絞って外観を伝えることを目的としています。KDE プロジェクトは、手伝ってくれる方は誰でも歓迎します。

KDE の開発に参加する方法としては様々なものがありますが、幾つかのカテゴリに分類できます:
プログラム開発者でなければ、参加するには のページで他に貢献できることを確認して下さい。Bugsquadもご確認下さい。


KDE プロジェクトの一般的な方向性は、活動をしている人々によって決定されます。将来的に KDE をどうするかについて、高次元での統一した計画は存在しません。


恐らく KDE の開発状況について知るための最も良い方法でしょう。こちらにアーカイブがあります。
KDE のソースコードリポジトリのうち、関心のあるプロジェクトへのコミット通知を受け取ることができます。
KDE Commit-Digest
毎週の KDE ソースコードリポジトリへのコミット状況の要約です。
The Dot
KDE ニュースサイトです。


KDE へ貢献する方法として最も簡単なのが、KDE バグ追跡システム (Bugzilla) から KDE のバグを報告することです。

使っているアプリケーションがクラッシュした際、Dr Konqi が表示され、クラッシュについてレポートする手順を示します。詳細はより良いクラッシュレポートを作成するにはの記事を参照して下さい。

Getting Started with Coding

Getting started at coding for KDE is a matter of finding something to fix, and fixing it. You may want to consult the module overview to help find what you are looking for; once you have fixed something, you will want to send in a patch. If you do that a few times, you may want to apply for a KDE Contributor account so you can improve things directly.


KDE is mostly written in C++. If you are not familiar with C++, you should do at least some work on it. There are a number of good books on C++ - an excellent source is Bruce Eckel's "Thinking in C++", which is available both as a free download and as a printed document. It isn't essential to understand everything before you start in KDE, but you do need to understand basic syntax and operations.


To become proficient with KDE coding, you should understand the Qt toolkit. If you are not familiar with Qt, you should work through the tutorials included with Qt Reference Documentation.

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 the Books about Qt page. More suggestions on becoming familiar with Qt4 are available How to Learn Qt page.


A range of information on KDE techniques is available in the tutorial section. Note that some of these tutorials still target KDE3, though they should be at least partly applicable.

You will also find useful information on KDE coding in the FAQs section. This information may also be somewhat dated for KDE4, however much of it is broadly applicable, even outside KDE.

You can also read KDE coding books.

Last, but by no means least, KDE comes with extensive class (Application Programmer Interface) documentation. This is available in the KDE API Reference Manuals section, which also contains a number of useful links on how to write or update the class documentation. You can also generate these on your own machine, or refer to a more up-to-date online version at API Reference.

A more detailed description of the steps above is available in our Programming Guide.

Getting Involved in Bug Hunting and Application Quality

There is a large number of applications within KDE, and not all of them have a maintainer dedicated to managing bugs and generally helping out with all the issues associated with turning some working code into a polished application.

If you are interested in helping out with KDE, but don't know where to start, becoming a member of the KDE Quality Team might appeal to you - see the Quality Team website for more information. Note that you do not need any programming skills to become involved. In particular developers regularly publish so-called Junior Jobs to encourage new contributions.

Of course, you can become involved in bug hunting without being part of the KDE Quality Team - just create yourself an account on the KDE bug tracking system, and start searching / sorting through the bugs. Again, you don't have to have programming skills - it helps the programmers enormously just to have a procedure that allows a bug to be consistently reproduced.

The Bugsquad tries to keep track of bugs in KDE software and make sure that valid bugs are noticed by developers. You do not need any programming knowledge to be in the Bugsquad; in fact it is a great way to return something to the KDE community if you cannot program.

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 TechBase website. And if possible, help edit it for clarity, and use the talk page if something is unclear.
  • 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.

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