Lines Matching full:that

5 "Why" section, to ensure that the intent is being met, and that if exceptions to
10 ## Meta layers should not patch projects that exist within the openBMC tree
15 the possibility that patches exist that repo maintainers aren't aware of makes
16 it much more likely that a single machine breaks, or we have behavior
19 Also, in general, the maintainer is there to ensure that the greater community,
33 PACKAGECONFIG entry that can be set to enable it.
39 Yocto itself is an open source project that accepts contributions. The more
40 changes that OpenBMC stacks against Yocto recipes, the more unmaintainable it
59 There are some OpenBMC projects that are utilized outside of OpenBMC. As such,
60 there are configuration items that are not intended to be used in OpenBMC, or
61 configuration items that would pose a security risk. Also, as options change and
67 configurations makes that change far more difficult to do.
72 use that to enable said feature in your meta layer.
74 ## Meta layers should not have recipes that point to proprietary licensed code
79 appropriate distribution licenses such that it can be reused. Pointing to
80 commercially licensed repositories actively opposes that goal.
84 Find an equivalent open source project that meets the needs, or request that the
91 Without this guideline, a loophole is present that allows OpenBMC developers to
92 bypass code review by pointing the upstream recipe to a public repository that
113 Generally an OpenBMC specific repository is something that does any of the
125 Keeping all long-term-supported code in the OpenBMC github ensures that the
128 refactoring that might be necessary to keep up with the latest best practices,
144 increases the likelihood that builds break, and makes builds far less
167 authority. Placing code into these meta-layers allows practices that do not
169 implementations and approaches that do not encourage collaboration.