[librsvg: 12/21] Some more things for the outline.

[Marge Bot <marge-bot src gnome org>]

commit 9bb2a2234fcd0e4cbeef1d9e1c8fe6e2a31f090c
Author: Federico Mena Quintero <federico gnome org>
Date:   Wed Aug 17 17:30:34 2022 -0500

    Some more things for the outline.
    
    Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/729>

 devel-docs/index.rst | 24 ++++++++++++++++--------
 1 file changed, 16 insertions(+), 8 deletions(-)
---
diff --git a/devel-docs/index.rst b/devel-docs/index.rst
index e35a13bab..5319320de 100644
--- a/devel-docs/index.rst
+++ b/devel-docs/index.rst
@@ -12,11 +12,6 @@ Welcome to the developer's guide for librsvg.  This is for people who
 want to work on the development of librsvg itself, not for users of
 the library or the `rsvg-convert` program.
 
-Before embarking on big changes to librsvg, please write a little
-design document modeled on the following ones, and submit a merge
-request.  We can then discuss it before coding.  This way we will have
-a sort of big-picture development history apart from commit messages.
-
 Introduction
 ------------
 
@@ -25,9 +20,9 @@ use the then-new Scalable Vector Graphics format (SVG) for GNOME's
 icons and other graphical assets on the desktop.  Since then, it has
 evolved into a few different tools.
 
-You may want to familiarize yourself with :doc:`product` to see what a
-full build produces: the library itself, the ``rsvg-convert``
-executable, etc.
+You may want to familiarize yourself with :doc:`product` to read about
+these tools, and the things that a full build produces: the library
+itself, the ``rsvg-convert`` executable, etc.
 
 Getting started
 ===============
@@ -47,9 +42,20 @@ Tour of the code - load a file, render it.
 
 Test suite - move tests/readme here?
 
+Link to the internals documentation.
+
 Design documents
 ================
 
+Before embarking on big changes to librsvg, please write a little
+design document modeled on the following ones, and submit a merge
+request.  We can then discuss it before coding.  This way we will have
+a sort of big-picture development history apart from commit messages.
+
+See https://rustc-dev-guide.rust-lang.org/walkthrough.html, section
+Overview, to formalize the RFC process for features vs. drive-by
+contributions.
+
 FIXME: link the md here.
 
 Information for maintainers
@@ -59,6 +65,8 @@ FIXME: Move RELEASING.md here
 
 Overview of the maintainer's workflow.
 
+Marge-bot.
+
 Documentation on the CI.
 
 References