nexmon – Blame information for rev 1

Subversion Repositories:
Rev:
Rev Author Line No. Line
1 office 1 <?xml version="1.0"?>
2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 ]>
5 <refentry id="glib-resources" revision="17 Jan 2002">
6 <refmeta>
7 <refentrytitle>Mailing lists and bug reports</refentrytitle>
8 <manvolnum>3</manvolnum>
9 <refmiscinfo>Mailing lists and bug reports</refmiscinfo>
10 </refmeta>
11  
12 <refnamediv>
13 <refname>Mailing lists and bug reports</refname>
14 <refpurpose>
15 Getting help with GLib
16 </refpurpose>
17 </refnamediv>
18  
19 <refsect1>
20 <title>Filing a bug report or feature request</title>
21  
22 <para>
23 If you encounter a bug, misfeature, or missing feature in GLib, please
24 file a bug report on
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 GLib documentation; file those against the "docs" component of the "glib"
28 product in Bugzilla.
29 </para>
30  
31 <para>
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.
36 </para>
37  
38 <para>
39 The bug tracker should definitely be used for feature requests, it's
40 not only for bugs. We track all GLib development in Bugzilla, so it's
41 the way to be sure the GLib developers won't forget about an issue.
42 </para>
43  
44 </refsect1>
45  
46 <refsect1>
47 <title>Submitting Patches</title>
48  
49 <para>
50 If you develop a bugfix or enhancement for GLib, 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.
56 </para>
57  
58 <para>
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.
63 </para>
64  
65 </refsect1>
66  
67 <refsect1>
68 <title>Mailing lists</title>
69  
70 <para>
71 There are several mailing lists dedicated to GTK+ and related
72 libraries. Discussion of GLib generally takes place on these lists.
73 You can subscribe or view the archives of these lists on
74 <ulink url="http://mail.gnome.org">http://mail.gnome.org</ulink>.
75 </para>
76  
77 <para>
78 <variablelist>
79  
80 <varlistentry>
81 <term><ulink url="mailto:gtk-list@gnome.org">gtk-list@gnome.org</ulink></term>
82 <listitem><para>
83 gtk-list covers general GTK+ (and GLib) topics; questions about using GLib
84 in programs, GLib from a user standpoint, announcements of GLib-related projects
85 would all be on-topic. The bulk of the traffic consists of GTK+ programming
86 questions.
87 </para></listitem>
88 </varlistentry>
89  
90 <varlistentry>
91 <term><ulink url="mailto:gtk-devel-list@gnome.org">gtk-devel-list@gnome.org</ulink></term>
92 <listitem><para>
93 gtk-devel-list is for discussion of work on GTK+ (and GLib) itself, it is
94 <emphasis>not</emphasis> for asking questions about how to use GTK+ (or GLib)
95 in applications. gtk-devel-list is appropriate for discussion of patches,
96 bugs, proposed features, and so on.
97 </para></listitem>
98 </varlistentry>
99  
100 <varlistentry>
101 <term><ulink url="mailto:gtk-doc-list@gnome.org">gtk-doc-list@gnome.org</ulink></term>
102 <listitem><para>
103 gtk-doc-list is for discussion of the <application>gtk-doc</application>
104 documentation system (used to document GTK+ and Glib), and for work on the GTK+
105 (and GLib) documentation.
106 </para></listitem>
107 </varlistentry>
108  
109 </variablelist>
110 </para>
111  
112 </refsect1>
113  
114  
115 </refentry>