1 <refentry id="gmime-resources" revision="1 Feb 2003">
3 <refentrytitle>Mailing lists and bug reports</refentrytitle>
4 <manvolnum>3</manvolnum>
5 <refmiscinfo>Mailing lists and bug reports</refmiscinfo>
8 <refname>Mailing lists and bug reports</refname>
10 Getting help with GMime
14 <title>Filing a bug report or feature request</title>
16 If you encounter a bug, misfeature, or missing feature in GMime, please
18 <ulink url="http://bugzilla.gnome.org">http://bugzilla.gnome.org</ulink>.
19 We'd also appreciate reports of incomplete or misleading information in
20 the GMime documentation; file those against the "docs" component of the
21 "gmime" product in Bugzilla.
24 The bug tracker should definitely be used for feature requests, it's
25 not only for bugs. We track all GMime development in Bugzilla, so it's
26 the way to be sure the GMime developers won't forget about an issue.
30 <title>Submitting Patches</title>
32 If you develop a bugfix or enhancement for GMime, please file that in
33 Bugzilla as well. Bugzilla allows you to attach files; please attach a
34 patch generated by the <command>diff</command> utility, using the
35 <option>-u</option> option to make the patch more readable. All
36 patches must be offered under the terms of
37 the <ulink url="http://www.gnu.org/licenses/lgpl-2.1.txt">LGPLv2.1</ulink>
38 license, so be sure you are authorized to give us the patch under
42 If you want to discuss your patch before or after developing it, mail
43 <ulink url="mailto:gmime-devel-list@gnome.org">gmime-devel-list@gnome.org</ulink>,
45 the <ulink url="http://bugzilla.gnome.org">Bugzilla</ulink> report as
46 well, this way it's less likely to slip through the cracks.
50 <title>Mailing lists</title>
51 <para>There is currently only one mailing-list devoted to GMime
52 itself which is for both the development of and development with
53 GMime. You can subscribe to this list
54 at <ulink url="http://mail.gnome.org/mailman/listinfo/gmime-devel-list">http://mail.gnome.org/mailman/listinfo/gmime-devel-list</ulink>.