Modules - Rules for community modules: Difference between revisions

Modules - Rules for community modules (view source)

84 bytes added , 7 months ago

m

31,003

edits

@@ Line 21: / Line 21: @@
 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 is a link to an external reference, the external link must be a forge based on Git.
+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, ...).
 * 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).
 * Contributing to sources must be as easy as doing a Pull or Merge Request. If the creation of an account is required for this, the creation of the user account should be possible from the forge in few seconds. No personal information should be requested (except a login or an email) for this registration step. Rgistration process should also be fully automatic (so contributor can register any day at any hour and push its Pull Request few seconds after).