3 <!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
8 <chapter id="contribute">
9 <title>Contributing</title>
14 <para>How can I contribute to &kde;?</para>
17 <para>&kde; is a free software project that lives from voluntary
18 contributions. Everybody is encouraged to contribute to &kde;. Not
19 only programmers are welcome. There are many ways in which you can
20 help to improve &kde;:</para>
22 <listitem><para>Test the software.</para></listitem>
23 <listitem><para>Send in bug reports. For more information on this,
24 see <link linkend="bug-report">How do I submit a bug
25 report?</link>.</para></listitem>
26 <listitem><para>Write documentation or help files. You can get some
27 information by visiting the <ulink
28 url="http://l10n.kde.org/docs/">&kde; Editorial Team
29 Home Page</ulink>.</para></listitem>
30 <listitem><para>Translate programs, documentation, and help files.
31 For more information on this, you should visit <ulink
32 url="http://l10n.kde.org">The &kde; Translators' and Documenters' Web
33 Site</ulink>.</para></listitem>
34 <listitem><para>Draw nice icons or compose sound effects. You can
35 visit the <ulink url="http://kde-artists.org/">&kde;
36 artists page</ulink> to find out more.</para></listitem>
37 <listitem><para>Write articles and books about &kde;. If you want to
38 help spread the word about &kde;, simply send an email to
39 <email>kde-promo@kde.org</email>. This will get you in touch
40 with the &kde; public relations volunteers.</para></listitem>
41 <listitem><para>Program new &kde; applications. Please refer to <xref
42 linkend="programming"/> for more information.</para></listitem>
43 <listitem><para> Of course, sponsors are also
44 welcome. :-)</para></listitem>
46 <para>There are several places to look for more information if you
47 want to get involved in the development. The first step is to
48 subscribe to some of the <ulink url="http://www.kde.org/mailinglists/">mailing
49 lists</ulink>. You will soon see something
50 that can be improved or added.</para>
55 <question id="bug-report">
56 <para>How do I submit a bug report?</para>
59 <para>There is a bug tracking system available at <ulink
60 url="http://bugs.kde.org">http://bugs.kde.org</ulink>. The
61 system features a wizard to submit new bug reports and a
62 list of all known bugs.</para>
63 <para>The easiest way to submit a bug is to select
64 <menuchoice><guimenu>Help</guimenu><guimenuitem>Report
65 Bug...</guimenuitem></menuchoice> from the menu bar of the application
66 with the bug. This will open a small dialog box with a link
67 to the bug tracking system. Please make sure to follow the
68 instructions of the bug reporting wizard.</para>
73 <question id="programming">
74 <para>I want to program for &kde;. What should I do first?</para>
77 <para>Everybody is encouraged to develop software for &kde;. What you
78 should do first depends strongly on your experience, ⪚ whether you have
79 already learned C++ or have experience with the &Qt; toolkit and so
81 <para>To get into &kde; programming, you will need some basic tools:
82 <application>cmake</application>, and
83 <application>gcc</application>. You should look to <ulink
84 url="http://techbase.kde.org/">http://techbase.kde.org/</ulink>
87 <para>Another excellent resource for learning &kde;
88 programming is the &Qt;
89 online tutorials. These are installed along with &Qt;. To view them,
90 open <filename>$<envar>QTDIR</envar>/doc/html/index.html</filename> in
91 &konqueror; and bookmark it. The tutorials
92 can be found under "Using
93 Qt". The source code for each lesson can be found in the <filename
94 class="directory">$<envar>QTDIR</envar>/tutorial</filename>
96 <para>There is, however, one thing that everybody interested in
97 programming for &kde; should do: <emphasis>subscribe to the developers
98 mailing list</emphasis>. To subscribe, you have to send an email to
100 url="mailto:kde-devel-request@kde.org">kde-devel-request@kde.org</ulink>
101 with the subject <userinput>subscribe
102 <replaceable>your_email_address</replaceable></userinput>.
103 <important><para>Please read <link linkend="subscribe">How to
104 subscribe/unsubscribe to these lists</link> carefully. Everything
105 said there applies to the development list as
106 well.</para></important></para>
112 <para>How do I get access to &kde; <acronym>SVN</acronym>?</para>
115 <para>The &kde; project uses <acronym>SVN</acronym> to develop the
116 core parts of the software. Usually, when you have changed one of the
117 parts (⪚ fixed a bug), and you want to commit this change, the best
118 way is to create a patch against a current snapshot and send this
119 patch to the developer/maintainer of the respective program.</para>
120 <para>If you are doing this more or less regularly, there are instructions here on how to get write access to the <acronym>SVN</acronym> repository: <ulink url="http://techbase.kde.org/Contribute/Get_a_SVN_Account">
121 http://techbase.kde.org/Contribute/Get_a_SVN_Account</ulink>. But be aware that more users will slow
122 down <acronym>SVN</acronym> access for all developers, so we want to
123 keep the number of people with direct <acronym>SVN</acronym> access
124 reasonably small. But feel free to ask!</para>
130 <para>Can I have read-only access to the <acronym>SVN</acronym> repository?</para>
133 <para>Yes. Instructions on how to get anonymous, read-only <acronym>SVN</acronym> access are here: <ulink url="http://techbase.kde.org/Getting_Started/Sources/Anonymous_SVN">
134 http://techbase.kde.org/Getting_Started/Sources/Anonymous_SVN</ulink>
141 <para>Are there any <acronym>SVN</acronym> mirror sites for &kde;?</para>
144 <para>No, there are currently no anonymous <acronym>SVN</acronym> mirror sites for &kde;. If you're interested in setting one up, please contact <email>sysadmin@kde.org</email>
151 <para>How do I go about translating &kde; programs into my native
155 <para>Look at the <ulink url="http://l10n.kde.org">The &kde;
156 Translators' and Documenters' Web Site</ulink> to see whether your
157 program is already translated (most are). Otherwise you will find
158 information there on how to do it yourself.</para>