CA Baseline - MustSupport Removal Proposal v2.0.0 - Feb 14 vote

I am unable to make the call on the 14th, but do agree with the proposal to remove the mustSupport from the profiles for v2.0

We've been discussing the risks/benefits of MustSupport in the Baseline over the last two years (see today's call for a summary of the discussions). We have landed on a proposal to remove the minimal set of remaining mustSupports from the profiles for v2.0.0 to bring us more in line with the convention of other national bases and to make it more useful in the context of other guides (e.g., CA Core+).

We are seeking feedback on the forums to the following proposal by 2/13 and will be pursuing a vote on the motion at the next Governance Call (2/14).

Proposal: Remove mustSupport from the profiles for v2.0.0, with the intent to only re-introduce if we have an affirmative position on why mustSupports should be re-introduced to provide unique value in the Baseline – supporting with design principles & goals we set for the Baseline.

• Note any of the current mustSupports in a spreadsheet (indicate the date & maturity level for the profile so that it still has value as an artefact to support other conversations) – host spreadsheet somewhere and share the spreadsheet w/ pCHDCF & Core+ teams
• Update MustSupport section in the guide to indicate reasoning behind change and providing guidance