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:51, 18 October 2026
, 13 days ago→Elligible features and Duplicate rules
Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 59: | Line 59: | ||
* 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: | ||
** Sovereignty or emancipation from the GAFAM | ** Sovereignty or emancipation from the GAFAM | ||
** Legal requirement | ** Legal requirement | ||
** Interface with an external system too complex to maintain in the core. | ** Interface with an external system too complex to maintain in the core. | ||
** Cyber security (safety related to accidents or IT disaster are not part, risk management is not involved either). | |||
* 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. | * 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. | ||