Closed simahawk closed 2 months ago
This could be a dumb question, by here it goes 🤓 Why is the split between "core" and "contrib" modules. Is this for easier focused maintainers? As a contributor, how do I now if a feature is "core" or a "contrib"?
This could be a dumb question, by here it goes 🤓 Why is the split between "core" and "contrib" modules. Is this for easier focused maintainers? As a contributor, how do I now if a feature is "core" or a "contrib"?
@dreispt good question. In general:
This could be a dumb question, by here it goes 🤓 Why is the split between "core" and "contrib" modules. Is this for easier focused maintainers? As a contributor, how do I now if a feature is "core" or a "contrib"?
@dreispt good question. In general:
* core = generic, reusable in any context, not bound to very specific apps unless required * contrib = everything else that is not generic, built on top of the core/framework part * motivation: not ending up w/ huge repos, making clear what's "core and generic" and what's not (look at OCA/edi in v14 for instance)
NOTE to myself: mention this in the description of the repos :)
I'll set the description manually because ATM I don't think is supported by the tool
We use the name in fact https://github.com/OCA/repo-maintainer/blob/master/oca_repo_maintainer/tools/manager.py#L194
Originated from this discussion https://github.com/OCA/product-attribute/pull/1645#discussion_r1654672188. Similarly to
mis-builder-contrib
this repo should host modules that extendweb-api
features but they are not generic and not part of core set of modules.