[jhbuild] Drop requirement on github.com repo

[Emmanuele Bassi <ebassi src gnome org>]

commit 97f65005981140f13088daedd5a9e425e8e9f839
Author: Emmanuele Bassi <ebassi gnome org>
Date:   Thu Oct 25 11:10:59 2018 +0100

    Drop requirement on github.com repo
    
    We don't use jhbuild modules for releasing GNOME, so the requirements on
    the github.com repo should be relaxed.

 modulesets/gnome-suites-core-deps-latest.modules | 13 ++++++-------
 1 file changed, 6 insertions(+), 7 deletions(-)
---
diff --git a/modulesets/gnome-suites-core-deps-latest.modules 
b/modulesets/gnome-suites-core-deps-latest.modules
index 3f2173e9..4e364fb8 100644
--- a/modulesets/gnome-suites-core-deps-latest.modules
+++ b/modulesets/gnome-suites-core-deps-latest.modules
@@ -17,14 +17,13 @@
 <repository type="git" name="salsa.debian.org"
     href="https://salsa.debian.org/"/>
 
-<!-- WARNING: github.com is only allowed here under one of two conditions:
+<!--
+  WARNING: You should use github-tar and build from a release tarball;
+  building from Git should only happen if:
 
-  (a) The module has tarball releases elsewhere (e.g. GNOME infrastructure)
-  (b) The module is always built from tarball, never from git
-
-If (a) does not apply then you must build from tarball (github-tar) if adding
-a GitHub module here. Otherwise our release infrastructure will fail to handle
-the module and we will just change it to use a tarball anyway.
+    - the module is maintained by a GNOME developer (it hosts release
+      tarballs on GNOME infrastructure)
+    - the module is built from a stable branch or a tag
 -->
 <repository type="git" name="github.com"
     href="https://github.com/"/>