Gm Optimism Collective
We are delighted to be part of this season 6 Code of Conduct Council, and to contribute with our work to making the collective a better place to thrive.
Over the past two months we have had several meetings where we have discussed how to work and also shared our experience. In the first two months of our term, we spent part of the time building internal agreements, updating documents and learning how to work as a team. In addition, thanks to our open office hour, we have had the opportunity to meet more people with optimistic vibes and a desire to continue innovating the way we operate as a council.
The Optimism Code of Conduct Council Internal Operating Procedures for season 6, was updated and published in the Optimism Collective Forum. Here, a summary of changes from the previous one:
-
In the first lines we shared the process of election and the importance of the continuos decentralization of IOP for the long term benefit of the collective.
-
Endorsement and clarification of the process that involves the resolution and evaluation of the report, in this escenario we divided the conflicts in small, medium or large according to their severity and the needs for each conflict. A third party was introduced as a mediator (Resolv3), chosen through the Mission Foundation, to deal with conflict escalations that go beyond the capabilities of the council.
-
The timing for reviewing the conflicts was amplified by two days to a total of five days, and added the information about the notification for the parties, if the notified one didn’t respond in the next five days the CoCC it’s going to decide unilaterally.
-
We know that the information and some of the reports take longer to be evaluated, that’s why we are taking five working days to gather information and due diligence to understand what happened. And if mediation and voting takes place, we can extend this time up to ten days. However, if the conflict implies a severe violation one of the parties will be suspended until the resolution phase.
-
Definition of warnings and communication how information around cases is going to be privately managed and close to the chest reviewed.
Our approach was to renovate with a more inclusive, understandable and shareable language the Reporting Form. By today we have reviewed three different cases:
Report 1
The first report was anonymously filled by a Optimism Collective Member. It involved the project Rubyscore. The timing and review of all the documents and data were made on time and the members of the council made the due diligence of communicating with relevant parties. After discussing with the foundation, this report was out of the boundaries and the scope of the CoCC. We contacted the reporter via email and gave the information about the follow up on this case.
No further action was needed
Report 2
We had a public comment from Bubli.eth that has a complaint about the on chain voting and final decision made for the CoCC elections. In this case, Oxytocin started the conversation within his personal account, this happened in the transition period. After reviewing this publication and with the election of Oxytocin, all the members of the CoCC decided to write the response to Bubli.eth in consensus within the account of Oxytocin that posted in behalf of all of us.
No further action it’s intended to happen.
Report 3
We received an anonymous concern about possible centralization of power inside of the Grants Council. The CoCC reviewed this situation in an extraordinary meeting, and to de escalate and channel the public communication around this topic, we contacted the reporting party and requested support from Resolv3 to support transforming claims into proactive action steps that can contribute to seasonal continued improvements. Relevant information was shared with the grants council.
Report 4
We received a report from Hashigo that involved the Oekaki community and Base.
Although Base is part of the Superchain, we emphasize that things that happen outside of the Optimism Collective’s hosted platforms cannot be resolved or mitigated by the CoCC.
Each chain’s hosted platforms and internal communication channels are autonomous; therefore we cannot enforce any decision or be accountable for conflict happening on other OP Chains.
After reviewing the evidence of the report and the evolution of the situation, We contacted relevant parties to share recommendations and improvement ideas.
We believe that this concern is highly valid and will seek to suggest that not only Base, but other OP Chains replicate our CoC practices and even create their own CoC Council in the future to deal with this type of situations.
Call to action!
We are having great weeks and great experiences, in the first Office Hours we shared about our personal journey and the experience that drived us to be part of the CoCC, shared the new documents and the IOP. Now we are heading to our next office hours that will happen in Discord, on Sept 26th at 2:00 PM UTC (event soon to be added to the public calendar), please come by and say hi!