| <refentry id="glib-resources" revision="17 Jan 2002"> |
| <refmeta> |
| <refentrytitle>Mailing lists and bug reports</refentrytitle> |
| <manvolnum>3</manvolnum> |
| <refmiscinfo>Mailing lists and bug reports</refmiscinfo> |
| </refmeta> |
| |
| <refnamediv> |
| <refname>Mailing lists and bug reports</refname> |
| <refpurpose> |
| Getting help with GLib |
| </refpurpose> |
| </refnamediv> |
| |
| <refsect1> |
| <title>Filing a bug report or feature request</title> |
| |
| <para> |
| If you encounter a bug, misfeature, or missing feature in GLib, please |
| file a bug report on |
| <ulink url="http://bugzilla.gnome.org">http://bugzilla.gnome.org</ulink>. |
| We'd also appreciate reports of incomplete or misleading information in |
| the GLib documentation; file those against the "docs" component of the "glib" |
| product in Bugzilla. |
| </para> |
| |
| <para> |
| Don't hesitate to file a bug report, even if you think we may know |
| about it already, or aren't sure of the details. Just give us as much |
| information as you have, and if it's already fixed or has already been |
| discussed, we'll add a note to that effect in the report. |
| </para> |
| |
| <para> |
| The bug tracker should definitely be used for feature requests, it's |
| not only for bugs. We track all GLib development in Bugzilla, so it's |
| the way to be sure the GLib developers won't forget about an issue. |
| </para> |
| |
| </refsect1> |
| |
| <refsect1> |
| <title>Submitting Patches</title> |
| |
| <para> |
| If you develop a bugfix or enhancement for GLib, please file that in |
| Bugzilla as well. Bugzilla allows you to attach files; please attach a |
| patch generated by the <command>diff</command> utility, using the |
| <option>-u</option> option to make the patch more readable. All patches |
| must be offered under the terms of the GNU LGPL license, so be sure you |
| are authorized to give us the patch under those terms. |
| </para> |
| |
| <para> |
| If you want to discuss your patch before or after developing it, mail |
| <ulink url="mailto:gtk-devel-list@gnome.org">gtk-devel-list@gnome.org</ulink>. |
| But be sure to file the Bugzilla report as well; if the patch is only on the |
| list and not in Bugzilla, it's likely to slip through the cracks. |
| </para> |
| |
| </refsect1> |
| |
| <refsect1> |
| <title>Mailing lists</title> |
| |
| <para> |
| There are several mailing lists dedicated to GTK+ and related |
| libraries. Discussion of GLib generally takes place on these lists. |
| You can subscribe or view the archives of these lists on |
| <ulink url="http://mail.gnome.org">http://mail.gnome.org</ulink>. |
| </para> |
| |
| <para> |
| <variablelist> |
| |
| <varlistentry> |
| <term><ulink url="mailto:gtk-list@gnome.org">gtk-list@gnome.org</ulink></term> |
| <listitem><para> |
| gtk-list covers general GTK+ (and GLib) topics; questions about using GLib |
| in programs, GLib from a user standpoint, announcements of GLib-related projects |
| would all be on-topic. The bulk of the traffic consists of GTK+ programming |
| questions. |
| </para></listitem> |
| </varlistentry> |
| |
| <varlistentry> |
| <term><ulink url="mailto:gtk-devel-list@gnome.org">gtk-devel-list@gnome.org</ulink></term> |
| <listitem><para> |
| gtk-devel-list is for discussion of work on GTK+ (and GLib) itself, it is |
| <emphasis>not</emphasis> for asking questions about how to use GTK+ (or GLib) |
| in applications. gtk-devel-list is appropriate for discussion of patches, |
| bugs, proposed features, and so on. |
| </para></listitem> |
| </varlistentry> |
| |
| <varlistentry> |
| <term><ulink url="mailto:gtk-doc-list@gnome.org">gtk-doc-list@gnome.org</ulink></term> |
| <listitem><para> |
| gtk-doc-list is for discussion of the <application>gtk-doc</application> |
| documentation system (used to document GTK+ and Glib), and for work on the GTK+ |
| (and GLib) documentation. |
| </para></listitem> |
| </varlistentry> |
| |
| </variablelist> |
| </para> |
| |
| </refsect1> |
| |
| |
| </refentry> |