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 12:40, 18 October 2026
, 13 days ago→Elligible features and Duplicate rules
Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 55: | Line 55: | ||
== Elligible features and Duplicate rules == | == Elligible features and Duplicate rules == | ||
* Features of a community module must NOT: | * Features of a community module must NOT: | ||
[] provide a feature too similar to 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. In 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 is interesting for a lot of users of a given country and bring a real added-value related to one of this point: | * 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 at least one of this point: | ||
** Sustainability | ** Sustainability | ||
** Sovereignty | ** Sovereignty | ||
| Line 64: | Line 64: | ||
** Interface with an external system too complex to maintain in the core. | ** Interface with an external system too complex to maintain in the core. | ||
* If a | * If a can provide 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. | ||
= Responsability of the Dolibarr foundation = | = Responsability of the Dolibarr foundation = | ||