Well, my understanding is that it's actually not about reading the Policies section separately, but that any changes to Policies can be done at any time and do not have to be drafted into the Governance and do not have to be formally approved by a round table of the Community, Advisory, or Project Manager, correct? But Non-Policy sections (I.E. Our Governance) can only be changed through formal discussion, voting, and approvals by the Community, Core Dev, with final Advisory feedback.
Agree/Disagree?
Hmm, did we say well of how Policy changes are made? Maybe we should actually say that also.
- Governance section = How this section can be changed, i.e. our Governance Process. For our Governance section, it looks like we did a good job of explaining the change process for Governance section.
- Policies section = But how this section can be changed, i.e. the Advisory and Core Dev approval process for Policy changes? My understanding is that just someone speaking up in a meeting and getting CS&S, a few devs, and maybe the Project manager is enough to make a small policy change and it doesn't even necessarily have to be drafted into the Governance to actually take effect? <-- This is why I always wanted policies written in a different document by the way. No strong opinions, just bringing up the additional gap in documentation for the process for "who changes Policies and how and when they take effect"
