docs: Remove mentions of decommissioned services

We don't use Bugzilla or mailing list any more.

1 files changed, 18 insertions, 87 deletions

diff --git a/docs/reference/gtk/resources.sgml b/docs/reference/gtk/resources.sgml
index 05e18084d7..530712786b 100644
--- a/docs/reference/gtk/resources.sgml
+++ b/docs/reference/gtk/resources.sgml
@@ -20,12 +20,8 @@ Getting help with GTK+
 <title>Filing a bug report or feature request</title>
 
 <para>
-If you encounter a bug, misfeature, or missing feature in GTK+, please
-file a bug report on 
-<ulink url="https://bugzilla.gnome.org">https://bugzilla.gnome.org</ulink>.
-We'd also appreciate reports of incomplete or misleading information in 
-the GTK+ documentation; file those against the "docs" component of the "gtk+"
-product in Bugzilla.
+If you encounter a bug, misfeature, or missing feature in GTK, please
+file a bug report on <ulink url="https://gitlab.gnome.org/GNOME/gtk/issues">GitLab</ulink>.
 </para>
 
 <para>
@@ -37,103 +33,38 @@ discussed, we'll add a note to that effect in the report.
 
 <para>
 The bug tracker should definitely be used for feature requests, it's
-not only for bugs. We track all GTK+ development in Bugzilla, so it's
-the way to be sure the GTK+ developers won't forget about an issue.
+not only for bugs. We track all GTK development in GitLab, so it's
+the way to be sure the GTK developers won't forget about an issue.
 </para>
 
-</refsect1>
-
-<refsect1>
-<title>Submitting Patches</title>
-
 <para>
-If you develop a bugfix or enhancement for GTK+, 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.
+Just make sure that any issue filed is actionable, and contains clear
+instructions on how to reproduce an issue, and the conditions to close
+the bug report or feature request. Non-actionable, or user support
+questions will be directed to Discourse.
 </para>
 
 </refsect1>
 
 <refsect1>
-<title>Mailing lists</title>
+<title>Contributing</title>
 
 <para>
-There are several mailing lists dedicated to GTK+ and related
-libraries. Discussion of GLib, Pango, and ATK in addition to GTK+
-proper is welcome on these lists. You can subscribe or view the
-archives of these lists on 
-<ulink url="https://mail.gnome.org">http://mail.gnome.org</ulink>.
-If you aren't subscribed to the list, any message you post to
-the list will be held for manual moderation, which might take
-some days to happen.      
+Please, follow the instructions outlined in the
+<ulink url="https://gitlab.gnome.org/GNOME/gtk/-/blob/master/CONTRIBUTING.md">Contribution Guide</ulink> available in the GTK
+source code repository.
 </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+ topics; questions about using GTK+ in programs,
-GTK+ from a user standpoint, announcements of GTK+-related projects
-such as themes or GTK+ modules would all be on-topic. The bulk of the
-traffic consists of GTK+ programming questions.
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term><ulink url="mailto:gtk-app-devel-list@gnome.org">gtk-app-devel-list@gnome.org</ulink></term> 
-<listitem><para>
-gtk-app-devel-list covers writing applications in GTK+. It's narrower
-in scope than gtk-list, but the two lists overlap quite a
-bit. gtk-app-devel-list is a good place to ask questions about GTK+
-programming.  </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+ itself, it is 
-<emphasis>not</emphasis> for
-asking questions about how to use GTK+ 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-i18n-list@gnome.org">gtk-i18n-list@gnome.org</ulink></term>
-<listitem><para>
-gtk-i18n-list is for discussion of internationalization in GTK+; 
-Pango is the main focus of the list. Questions about the details of 
-using Pango, and discussion of proposed Pango patches or features, are
-all on topic.
-</para></listitem>
-</varlistentry>
+</refsect1>
 
-<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 for work on the GTK+ 
-documentation.
-</para></listitem>
-</varlistentry>
+<refsect1>
+<title>User support</title>
 
-</variablelist>
+<para>
+If you have questions about building, using, or contributing to GTK, please
+open a topic on <ulink url="https://discourse.gnome.org/tag/gtk">Discourse<ulink>.
 </para>
 
 </refsect1>
 
-
 </refentry>