Recap: Community Call #6 (October 11th)

Thank you to for joining this week’s delegate community call! For those of you that couldn’t make it, a full recording of the meeting can be found here.
Brief recap below!

Previous action items:

  • On the topic of guidance on funding development through a proposal and a governance fund charter: Stay tuned, this is being worked on by the Foundation!

Topics of discussion

A few proposals have been changed after receiving delegate approval. Some delegates have later removed their approval after changes were made, but it’s hard to constantly monitor whether or not proposals are changing. Suggested ways to address this were:

  • Foundation could add language to the operating manual that specifies what constitutes a material change or what type of changes require a proposal to be re-submitted. However, it may be challenging to fully define what constitutes a material change.

  • Proposers could specify that a proposal is in its final form and only then seek delegate approval. The thread could be locked once they receive approvals.

  • There is a setting on Discourse that allows changes to be highlighted (redlining). We could turn that setting on and then a committee could alert approving delegates if there have been notable changes made since approval.

  • It’s important to consider who would be responsible for monitoring whether changes have been made. The proposer? The approving delegate? The committees?

  • The Foundation will consider all of the options above and request feedback on a suggested solution

Who has decision making authority when something is not clearly specified by the Foundation or in the Operating Manual?

  • When the Foundation is not the decision maker, it has been unclear who is.
    It was suggested that the Foundation sets guidelines and then committees have decision making authority when something pertaining to their operations is ambiguous.

  • This would imbue committees with more decision making power than is explicitly outlined at the moment.

  • Committee responsibilities are currently outlined in the Introducing Committees post. Any updates to clarify decision making authority will be highlighted on the Forum and in Discord.

  • When something is defined in the operating manual, but needs to be updated or changed, delegates can submit a pull request to suggest a change on Github: (OPerating-manual/ at main · ethereum-optimism/OPerating-manual · GitHub)

The Foundation is aware that a delegate code of conduct is needed and is something to be considered during the next Reflection Period.

Feedback on Cycle 7

  • It’s been an improvement over Cycle 6

  • There are still some proposals falling through the cracks because proposers are unsure of the process. There may be more room for committees and delegates to be more involved in bringing proposers up to speed and pointing them towards the Gov Docs

  • From a proposer’s perspective, one thing that would help would be if all committees can post the list of proposals they are going to review so proposers know if their proposal has been included or not.

Action items

  • Join the convo here to create community mottos for navigating tough governance discussions

  • Make sure to provide your input on the Uniswap RFC regarding liquidity mining incentives for their OP grant. This is a great way to engage as an Optimism delegate outside our own community

  • For those of you at Devcon, stay on top of this thread and hopefully you can all meet up and talk gov stuff: Devcon Community Governance Meetup!

  • If your committee is not already posting a list of proposals that will be reviewed in your Discord channel at the start of Week 2, please do so!

We’re back to delegate hosted calls next week, thank you in advance to Duncan! Sign up to host future calls here and in the meantime, stay Optimistic :star2: :sparkling_heart:


This is concise and in-depth :+1:


Thank you so much for the notes!!!

Thanks! Appreciate this comprehensive summary.

Thank you @lavande!!! :slightly_smiling_face: