docs/architecture/optionality.md

3 OpenBMC does its best to be widely applicable to all BMC deployments in the
10 Required for the deployment of _any_ OpenBMC build. Examples of this include the
19 image, or might be done to reduce the security attack surface. These kids of
27 one of these categories. For non-trivial feature additions, the commit message
36 include, Http keep alive, Security features like timeouts and payload size
38 user-facing impact to function, although might do things like improve
41 Requires: Standards conformance, applicability to all flash-size systems, as
44 ### User opt-in features
46 User opt-in features are features for which an external user must explicitly
52 Requires: Explicit, non-default user opt-in to execute the various features.
54 ### Developer opt-in features
57 _only_ for a subset of the OpenBMC audience, and might add OEM parameters to
58 non-standard interfaces, new command sets, or new APIs that might be applicable.
67 CI will generally enable all developer opt-in features to ensure the most
73 2. Entity-manager configuration