Create Executive vote - October 04, 2024.md

[blimpa]

@boet1 , @VoteWizard

[blimpa]

Executive Creation

Creation

• [x] Sync Community Git

• [x] Ensure you are working from the latest master branch

• [x] Read Associated Executive Contents sheet

• [x] Copy the executive template

• [x] Update filename

• [x] Update dates - exact time is not required and should be left at midnight.

• [x] Ensure the title refers to the most impactful/important actions included in the proposal.

• [x] Ensure that the summary refers to all actions included in the proposal.

• [x] Ensure that the publisher (entity publishing the executive on the voting portal) of the executive is listed in the preamble (at the entity level).

• [x] Ensure that the writers of the executive code are listed in the preamble (at the entity level).

• [x] Ensure that the reviewers of the executive code are listed in the preamble (at the entity level).

• [x] Ensure that the office-hours modifier is mentioned as part of the executive copy, if present in the executive spell code.

• [x] Ensure that it is clearly stated which items are affected by the GSM Delay.

• [x] Ensure that the GSM Delay period is clearly communicated.

• [x] Ensure that the proposal expiry is explicitly noted, including the length of time for which the proposal is valid.

Items

• [x] Add each item to the proposal details section

• [x] Order the items by judged impact/importance. If different from the executive contents, reorder the executive contents sheet so that they match.

• [x] For each item

  • [x] Ensure the executive summary contains a high-level overview of every action contained in the proposal.
  • [x] Ensure that each item or set of items in the executive proposal has a corresponding entry in the proposal details section.
  • [x] Ensure that each item in the copy contains a link to the reasoning for its inclusion.
  • [x] Ensure that each item in the copy contains a link to the authorization for its inclusion.
  • [x] Ensure that each item in the copy contains any links required for voters to determine the context surrounding its inclusion.
  • [x] Ensure that the framing and tense used for each item is future-conditional. Ie: "IF this executive proposal passes, THEN this action will take place."
  • [x] Ensure that hyperlinks to documentation and/or context are added to key parameters, terms, and contracts where reasonable and possible.
  • [x] Ensure that Ethereum and IPFS addresses are hyperlinked such that it is easy to view their details.
  • [x] Ensure that parties implicated in the proposal outcome related to this item are aware of the wording used.

Self-Review

• [x] Do any '$' parameter signifiers remain? (spell address is unknown at this point)
• [x] Do the executive title, summary, and executive summary accurately reflect executive copy content?
• [x] Read the executive copy in full, with the above checklists and general readability in mind. Make any required changes.
• [x] Run the copy through a spelling and grammar checker - do not blindly accept suggested changes.
• [x] Inform the reviewer that the executive copy is ready to review
• [x] Commit changes, and create a PR to the Community GitHub repository.

Submission

• [ ] Merge approved executive copy PR.
• [ ] Inform technical teams that the copy is ready and provide the link.
• [ ] Once technical teams have provided a spell address, add it to the executive copy.
• [ ] Update the proposals.json to set the active proposal on the portal.
• [ ] Refresh portal cache (DUX/Jetstream can provide password)
• [ ] Inform the community of the new executive proposal.

[CivicSage3]

Spell Sheet Creation

Pre-Meeting Tasks (Completed by EOD Monday before Spell Meeting)

• [x] Reach out to Ecosystem Actors about possible Spell Contents.
• [x] Inform relevant parties about deadlines (see Spell Coordination Schedule).
• [x] Review recent polls for to-do items.
• [x] Review the latest forum posts for requested items.

GovOps Meeting Tasks (Tuesdays, one week before Spell release)

• [x] Obtain roles for this week:
  • [x] Spell Crafter
  • [x] Reviewer (Dewiz)
  • [x] Reviewer (Sidestream)
• [x] Review Requested Contents from Ecosystem Actors.
• [x] Obtain consensus on Spell Items.
• [x] Confirm Repeating Checklist Items:
  • [x] Office Hours: Yes
  • [x] Global Line Modifier: Yes
  • [x] Order of Operations Issues: Yes

Sheet Creation (Tuesdays, one week before Spell release)

• [x] Duplicate "Executive Contents (Template)" in Spell Sheet.
• [x] Add a new column with the spell date in the "Spell Progress Tracking" sheet and ensure the progress is kept up to date.
• [x] Rename duplicate tab for expected spell date (in yyyy-mm-dd format).
• [x] Add role and recurring items info from GovOps Meeting.
• [x] Add Spell Items as formatted in the sheet.
• [x] Complete and confirm checksums for DAI and MKR transfers.
• [x] SubDAO Spell Crafter delivered the SubDAO spell address and spell PR in Discord with no differences in the code.

Obtain Confirmations for listed items (Wednesday, confirmations due EOD Friday)

• [x] Reach out to relevant Ecosystem Actors for item-specific confirmations.
• [x] Correct any discrepancies.
• [x] Confirm items for the Governance Confirm column.

[VoteWizard]

We confirm the hash:

cast keccak -- "$(wget 'https://raw.githubusercontent.com/makerdao/community/7018db4f449dc84fd250302b87734bd7aa66620c/governance/votes/Executive%20vote%20-%20October%2004%2C%202024.md' -q -O - 2>/dev/null)"

0xcc25bed2b24d0e3735fc7fadced432daf59890454cde7a4e65373b9fa5c55f26