docs: refer to the already existing mailing list

If contributors choose to send patches to the mailing list, we'll
take them.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

docs/source/ContributionGuide.rst

@@ -23,11 +23,9 @@ take place in the Pull Request as well.
 For people who don't like the github development model, there is the option
 of sending the patches to the Mailing List, following a workflow more
 traditional in Open Source development communities. The patches will be
-reviewed in the Mailing List, should you opt for that.
-
-As soon as we have a mailing list functional, just send
-patches to the list, and we'll have a sub-maintainer that will collect the
-patches, integrate them on a branch, and then those patches will be submitted
-as a github Pull Request. This process tries to ensure that every contributed
-patch goes through the CI jobs before it is considered good for inclusion.
+reviewed in the Mailing List, should you opt for that. Then a maintainer will
+collect the patches, integrate them on a branch, and then those patches will
+be submitted as a github Pull Request. This process tries to ensure that every
+contributed patch goes through the CI jobs before it is considered good for
+inclusion.