31,003
edits
Modules - Rules for community modules: Difference between revisions
Jump to navigation
Jump to search
m
Modules - Rules for community modules (view source)
Revision as of 14:56, 7 April 2026
, 6 months ago→Duplicate
m (→Duplicate) Tag: 2017 source edit |
m (→Duplicate) Tag: 2017 source edit |
||
| Line 44: | Line 44: | ||
Source files of module can (should) contains name, email (and company name) of each author, however, the module should not contain any mention to the company at any other places, except into source files header or some text files (like README, COPYRIGHT, ...), so the "About page" of the module must refer to the authors as the "Dolibarr community". Name, email and company name of authors can be mentionned inside source files but we should not find a link to the web site of an external company inside the screens of a Community module, except links to the Git forge or any Dolibarr resource (like the https://partners.dolibarr.org page) or to documentation sites that are allowed. | Source files of module can (should) contains name, email (and company name) of each author, however, the module should not contain any mention to the company at any other places, except into source files header or some text files (like README, COPYRIGHT, ...), so the "About page" of the module must refer to the authors as the "Dolibarr community". Name, email and company name of authors can be mentionned inside source files but we should not find a link to the web site of an external company inside the screens of a Community module, except links to the Git forge or any Dolibarr resource (like the https://partners.dolibarr.org page) or to documentation sites that are allowed. | ||
== Duplicate == | == Features and Duplicate rules == | ||
If a module provides the same features than another Community module, the Dolibarr foundation board will decide which one to keep and which one to remove on a case per case basis, so only one module will remain for the same feature. | * A community module must not provide a feature too similare than a Dolibarr existing feature. If the module just complete a Dolibarr official existing feature, it is better to try to submit a PR to enhance the official feature. | ||
* A community module must offer a feature that may be interesting for a lot of users of a given country and must not be a niche market. In such a case, doing an external module for Dolistore.com is a better solution. | |||
* If a module provides the same features than another Community module, the Dolibarr foundation board will decide which one to keep and which one to remove on a case per case basis, so only one module will remain for the same feature. | |||
= Version and validation of these rules = | = Version and validation of these rules = | ||