31,003
edits
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 at least 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: | ||
| 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 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. | * Finally, we must answer the question: What is impact if suddenly the module become not available ? Is it a big trouble for end users or not ? If not (can be replaced easily), module is not elligible. | ||
Note: 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 = | ||