2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
3 "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
5 <refentry id="gtk-resources">
7 <refentrytitle>Mailing lists and bug reports</refentrytitle>
8 <manvolnum>3</manvolnum>
9 <refmiscinfo>Mailing lists and bug reports</refmiscinfo>
13 <refname>Mailing lists and bug reports</refname>
15 Getting help with GTK+
20 <title>Filing a bug report or feature request</title>
23 If you encounter a bug, misfeature, or missing feature in GTK+, please
25 <ulink url="http://bugzilla.gnome.org">http://bugzilla.gnome.org</ulink>.
26 We'd also appreciate reports of incomplete or misleading information in
27 the GTK+ documentation; file those against the "docs" component of the "gtk+"
32 Don't hesitate to file a bug report, even if you think we may know
33 about it already, or aren't sure of the details. Just give us as much
34 information as you have, and if it's already fixed or has already been
35 discussed, we'll add a note to that effect in the report.
39 The bug tracker should definitely be used for feature requests, it's
40 not only for bugs. We track all GTK+ development in Bugzilla, so it's
41 the way to be sure the GTK+ developers won't forget about an issue.
47 <title>Submitting Patches</title>
50 If you develop a bugfix or enhancement for GTK+, please file that in
51 Bugzilla as well. Bugzilla allows you to attach files; please attach a
52 patch generated by the <command>diff</command> utility, using the
53 <option>-u</option> option to make the patch more readable. All patches
54 must be offered under the terms of the GNU LGPL license, so be sure you
55 are authorized to give us the patch under those terms.
59 If you want to discuss your patch before or after developing it, mail
60 <ulink url="mailto:gtk-devel-list@gnome.org">gtk-devel-list@gnome.org</ulink>.
61 But be sure to file the Bugzilla report as well; if the patch is only on the
62 list and not in Bugzilla, it's likely to slip through the cracks.
68 <title>Mailing lists</title>
71 There are several mailing lists dedicated to GTK+ and related
72 libraries. Discussion of GLib, Pango, and ATK in addition to GTK+
73 proper is welcome on these lists. You can subscribe or view the
74 archives of these lists on
75 <ulink url="http://mail.gnome.org">http://mail.gnome.org</ulink>.
76 If you aren't subscribed to the list, any message you post to
77 the list will be held for manual moderation, which might take
85 <term><ulink url="mailto:gtk-list@gnome.org">gtk-list@gnome.org</ulink></term>
87 gtk-list covers general GTK+ topics; questions about using GTK+ in programs,
88 GTK+ from a user standpoint, announcements of GTK+-related projects
89 such as themes or GTK+ modules would all be on-topic. The bulk of the
90 traffic consists of GTK+ programming questions.
95 <term><ulink url="mailto:gtk-app-devel-list@gnome.org">gtk-app-devel-list@gnome.org</ulink></term>
97 gtk-app-devel-list covers writing applications in GTK+. It's narrower
98 in scope than gtk-list, but the two lists overlap quite a
99 bit. gtk-app-devel-list is a good place to ask questions about GTK+
100 programming. </para></listitem>
104 <term><ulink url="mailto:gtk-devel-list@gnome.org">gtk-devel-list@gnome.org</ulink></term>
106 gtk-devel-list is for discussion of work on GTK+ itself, it is
107 <emphasis>not</emphasis> for
108 asking questions about how to use GTK+ in applications. gtk-devel-list
109 is appropriate for discussion of patches, bugs, proposed features,
115 <term><ulink url="mailto:gtk-i18n-list@gnome.org">gtk-i18n-list@gnome.org</ulink></term>
117 gtk-i18n-list is for discussion of internationalization in GTK+;
118 Pango is the main focus of the list. Questions about the details of
119 using Pango, and discussion of proposed Pango patches or features, are
125 <term><ulink url="mailto:gtk-doc-list@gnome.org">gtk-doc-list@gnome.org</ulink></term>
127 gtk-doc-list is for discussion of the <application>gtk-doc</application>
128 documentation system (used to document GTK+), and for work on the GTK+