blob: 02fc73b31118ce1aa8f6a0ca093a7105e4efd8ba (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
<!--
<?xml version="1.0" ?>
<!DOCTYPE chapter PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
"dtd/kdex.dtd">
-->
<chapter id="about">
<title
>About this <acronym
>FAQ</acronym
></title>
<qandaset>
<qandaentry>
<question>
<para
>What can I do to help out with this <acronym
>FAQ</acronym
>?</para>
</question>
<answer>
<para
>First, send us any errors that you may find. Also, any suggestions that you might have, are appreciated. Better yet, send us everything that you think is unclear, and if possible, send us what you think would be a clearer solution. Our email address is <email
>kde-doc-english@kde.org</email
>. </para>
<para
>Second, send us your solutions of those frequently-asked questions which are still not in this <acronym
>FAQ</acronym
>. We will put them in as soon as possible.</para>
<para
>Last but not least, please make full use of this <acronym
>FAQ</acronym
>. Read this <acronym
>FAQ</acronym
> (and other relevant documentation) well before asking questions on the various &kde; mailing lists or newsgroups.</para>
<note
><para
>You might also want to consider becoming a <acronym
>FAQ</acronym
> maintainer. Please refer to <xref linkend="FAQ-maintainer-HOWTO"/> for more details. </para
></note>
</answer>
</qandaentry>
<qandaentry>
<question id="FAQ-maintainer-HOWTO">
<para
>How do I become a <acronym
>FAQ</acronym
> maintainer?</para>
</question>
<answer>
<para
>Actually, it is very easy to become an <acronym
>FAQ</acronym
> maintainer, and we are always in need of fresh blood. :-) Just send us an email at <email
>kde-doc-english@kde.org</email
>. </para>
</answer>
</qandaentry>
</qandaset>
</chapter>
|
