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 15:03, 7 April 2026
, 6 months ago→Features and Duplicate rules
Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 45: | Line 45: | ||
== Features and Duplicate rules == | == Features and Duplicate rules == | ||
* 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 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 existing feature. | |||
** be a feature for a niche market. If such a case, providing an external module, hosted on your own forge, and published on DoliStore.com is a better choice. | |||
* A community module must offer a feature that | * A community module must offer a feature that is interesting for a lot of users of a given country and bring a real added-value related to one of this point: | ||
** Sustainability | |||
** Sovereignty | |||
** Legal requirement | |||
** Interface with an external system too complex to maintain in the core. | |||
* 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. | * 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. | ||