[librsvg/hospitality] README.md: Note how to contact me by irc

[Federico Mena Quintero <federico src gnome org>]

commit f652d0559410ef0342513af087b283c4d1ee8f53
Author: Federico Mena Quintero <federico gnome org>
Date:   Thu Jan 18 20:29:43 2018 -0600

    README.md: Note how to contact me by irc
    
    Also, link to this "Maintainer" section from the other READMEs instead
    of just putting my email in them.

 COMPILING.md    |  4 ++--
 CONTRIBUTING.md |  6 +++---
 README.md       | 14 ++++++++++++--
 tests/README.md |  4 ++--
 4 files changed, 19 insertions(+), 9 deletions(-)
---
diff --git a/COMPILING.md b/COMPILING.md
index 516f23d..eb37bc0 100644
--- a/COMPILING.md
+++ b/COMPILING.md
@@ -7,7 +7,7 @@ of how librsvg integrates Cargo and Rust into its autotools setup are
 described in [this blog post][blog], although hopefully you will not
 need to refer to it.
 
-It is perfectly fine to [ask the maintainer][mail] if you have
+It is perfectly fine to [ask the maintainer][maintainer] if you have
 questions about the Autotools setup; it's a tricky bit of machinery,
 and we are glad to help.
 
@@ -121,7 +121,7 @@ unpacked tarball.  Your build system can patch this file as needed.
 
 [autotools]: https://autotools.io/index.html
 [blog]: https://people.gnome.org/~federico/blog/librsvg-build-infrastructure.html
-[mail]: mailto:federico gnome org
+[maintainer]: README.md#maintainers
 [install]: INSTALL
 [rust-target-dir]: https://github.com/rust-lang/rust/tree/master/src/librustc_back/target
 [cargo-vendor]: https://crates.io/crates/cargo-vendor
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 3673f70..c39ceb8 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -77,7 +77,7 @@ requests (or pull requests) if your fork is in
 
 For technical reasons, the maintainers of librsvg do not get
 automatically notified if you submit a pull request through the GNOME
-mirror in Github.  [Please mail the maintainer][mail] directly if you
+mirror in Github.  [Please contact the maintainer][maintainer] directly if you
 have a pull request there or a branch that you would like to
 contribute.
 
@@ -103,14 +103,14 @@ toplevel [`Makefile.am`][toplevel-makefile].  *Note that this is for
 both C and Rust sources*, since `make(1)` needs to know when a Rust
 file changed so it can call `cargo` as appropriate.
 
-It is perfectly fine to [ask the maintainer][mail] if you have
+It is perfectly fine to [ask the maintainer][maintainer] if you have
 questions about the Autotools setup; it's a tricky bit of machinery,
 and we are glad to help.
 
 [coc]: code_of_conduct.md
 [gitlab]: https://gitlab.gnome.org/GNOME/librsvg
 [bugs-browse]: https://gitlab.gnome.org/GNOME/librsvg/issues
-[mail]: mailto:federico gnome org
+[maintainer]: README.md#maintainers
 [tests-readme]: tests/README.md
 [blog]: https://people.gnome.org/~federico/blog/librsvg-build-infrastructure.html
 [toplevel-makefile]: Makefile.am
diff --git a/README.md b/README.md
index 60d487c..e367989 100644
--- a/README.md
+++ b/README.md
@@ -131,8 +131,18 @@ from C.
 Maintainers
 -----------
 
-The maintainer of librsvg is [Federico Mena Quintero][federico].  You
-can [mail me][mail] for any other questions you have about librsvg.
+The maintainer of librsvg is [Federico Mena Quintero][federico].  Feel
+free to contact me for any questions you may have about librsvg, both
+its usage and its development.  You can contact me in the following
+ways:
+
+* [Mail me][mail] at federico gnome org.
+
+* IRC: I am `federico` on `irc.gnome.org` in the `#rust` or
+  `#gnome-hackers` channels.  I'm there most weekdays (Mon-Fri)
+  starting at about UTC 14:00 (that's 08:00 my time; I am in the UTC-6
+  timezone).  If this is not a convenient time for you, feel free to
+  [mail me][mail] and we can arrange a time.
 
 [svg]: https://en.wikipedia.org/wiki/Scalable_Vector_Graphics
 [gnome]: https://www.gnome.org/
diff --git a/tests/README.md b/tests/README.md
index 92243db..622f52b 100644
--- a/tests/README.md
+++ b/tests/README.md
@@ -144,7 +144,7 @@ It is up to you to decide what to do next:
   until someone fixes it, or try to [fix the bug yourself][pull-requests]!
 
 * Any other situation of course deserves attention.  Feel free to [ask
-  the maintainers][mail] about it; even if you figure out the problem
+  the maintainers][maintainer] about it; even if you figure out the problem
   yourself, a failed test almost always indicates a problem that is
   not just on your end.
 
@@ -269,4 +269,4 @@ corresponding object IDs and values to be tested for are in the
 [gtest]: https://developer.gnome.org/glib/stable/glib-Testing.html
 [bug]: ../CONTRIBUTING.md#reporting-bugs
 [pull-requests]: ../CONTRIBUTING.md#pull-requests
-[mail]: mailto:federico gnome org
+[maintainer]: README.md#maintainers