Modules - Rules for community modules: Difference between revisions

Modules - Rules for community modules (view source)

50 bytes added , 3 months ago

m

31,003

edits

@@ Line 28: / Line 28: @@
 The user that publish initialy the module in the Community repository agrees to check and approve, on a regular basis, all Pull Requests submited related to its module.
-If the module in the community repository is just a link to an external repository, the external link must be a forge based on '''Git''' (for example Gitlab, Gitea, Framagit, ...).
+The reference of the sources and issues of the module must be the community repo. Any hosting onto another repository must be as a mirroring only. This guarantee that the following needs for a community modules will always be met:
 * Getting sources with a simple "git clone" with no need to create any account must be possible, for exemple using the "git clone" command with the http url of the repository (the source of the Git external repository is defined into the index.yaml file in the root directory of the module).