| <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
| <html> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> |
| <title>Mailing lists and bug reports: GLib Reference Manual</title> |
| <meta name="generator" content="DocBook XSL Stylesheets V1.79.1"> |
| <link rel="home" href="index.html" title="GLib Reference Manual"> |
| <link rel="up" href="glib.html" title="GLib Overview"> |
| <link rel="prev" href="glib-changes.html" title="Changes to GLib"> |
| <link rel="next" href="glib-fundamentals.html" title="GLib Fundamentals"> |
| <meta name="generator" content="GTK-Doc V1.25.1 (XML mode)"> |
| <link rel="stylesheet" href="style.css" type="text/css"> |
| </head> |
| <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> |
| <table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="5"><tr valign="middle"> |
| <td width="100%" align="left" class="shortcuts"></td> |
| <td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td> |
| <td><a accesskey="u" href="glib.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td> |
| <td><a accesskey="p" href="glib-changes.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td> |
| <td><a accesskey="n" href="glib-fundamentals.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td> |
| </tr></table> |
| <div class="refentry"> |
| <a name="glib-resources"></a><div class="titlepage"></div> |
| <div class="refnamediv"><table width="100%"><tr> |
| <td valign="top"> |
| <h2><span class="refentrytitle">Mailing lists and bug reports</span></h2> |
| <p>Mailing lists and bug reports — |
| Getting help with GLib |
| </p> |
| </td> |
| <td class="gallery_image" valign="top" align="right"></td> |
| </tr></table></div> |
| <div class="refsect1"> |
| <a name="id-1.2.9.3"></a><h2>Filing a bug report or feature request</h2> |
| <p> |
| If you encounter a bug, misfeature, or missing feature in GLib, please |
| file a bug report on |
| <a class="ulink" href="http://bugzilla.gnome.org" target="_top">http://bugzilla.gnome.org</a>. |
| 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. |
| </p> |
| <p> |
| 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. |
| </p> |
| <p> |
| 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. |
| </p> |
| </div> |
| <div class="refsect1"> |
| <a name="id-1.2.9.4"></a><h2>Submitting Patches</h2> |
| <p> |
| 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 <span class="command"><strong>diff</strong></span> utility, using the |
| <code class="option">-u</code> 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. |
| </p> |
| <p> |
| If you want to discuss your patch before or after developing it, mail |
| <a class="ulink" href="mailto:gtk-devel-list@gnome.org" target="_top">gtk-devel-list@gnome.org</a>. |
| 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. |
| </p> |
| </div> |
| <div class="refsect1"> |
| <a name="id-1.2.9.5"></a><h2>Mailing lists</h2> |
| <p> |
| 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 |
| <a class="ulink" href="http://mail.gnome.org" target="_top">http://mail.gnome.org</a>. |
| </p> |
| <p> |
| </p> |
| <div class="variablelist"><table border="0" class="variablelist"> |
| <colgroup> |
| <col align="left" valign="top"> |
| <col> |
| </colgroup> |
| <tbody> |
| <tr> |
| <td><p><span class="term"><a class="ulink" href="mailto:gtk-list@gnome.org" target="_top">gtk-list@gnome.org</a></span></p></td> |
| <td><p> |
| 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. |
| </p></td> |
| </tr> |
| <tr> |
| <td><p><span class="term"><a class="ulink" href="mailto:gtk-devel-list@gnome.org" target="_top">gtk-devel-list@gnome.org</a></span></p></td> |
| <td><p> |
| gtk-devel-list is for discussion of work on GTK+ (and GLib) itself, it is |
| <span class="emphasis"><em>not</em></span> 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. |
| </p></td> |
| </tr> |
| <tr> |
| <td><p><span class="term"><a class="ulink" href="mailto:gtk-doc-list@gnome.org" target="_top">gtk-doc-list@gnome.org</a></span></p></td> |
| <td><p> |
| gtk-doc-list is for discussion of the <span class="application">gtk-doc</span> |
| documentation system (used to document GTK+ and Glib), and for work on the GTK+ |
| (and GLib) documentation. |
| </p></td> |
| </tr> |
| </tbody> |
| </table></div> |
| <p> |
| </p> |
| </div> |
| </div> |
| <div class="footer"> |
| <hr>Generated by GTK-Doc V1.25.1</div> |
| </body> |
| </html> |
