This SIP proposes minor amendments to the Core Contributor Committee (CCC) SIP-161 to help clarify CCCs responsibilities and only mentions modifications made to SIP-161.
\nThis SIP clarifies the following Core Contributor Committee responsibilities, while keeping the original responsibilities in place:
\nIn addition to the original motivation for establishing the CCC, there is a need for leadership and management body for CCs to ensure all required work is being implemented in a timely and effective manner. The CCC is the overseeing body of the overall progress and the direct representative between the CCs and the community and other governing bodies.
\nThe Core Contributor Committee will consist of three Core Contributors, one from engineering and two from other specialisations.
\nAmendments on the decisions to be made by CCCs:
\nNo change here.
\nCCCs are no longer to be elected every 3 months, they are now elected every 6 months, matching every second election epochs.\nCCs compensations and packages are now to be reviewed at least every 6 months or earlier, instead of every 3 months.
\nNo change.
\nSIPs
\nAll the original SIP-related responsibilities in SIP-161 are to be conducted directly or indirectly by the CCCs, meaning that CCCs may choose to delegate such responsibilities to an existing CC or determine that there is a lack of suitable CCs for particular roles and take necessary actions to fill the gaps. The goal of CCCs is to make sure that these responsibilities are implemented in a timely and effective manner one way or another.
\nNon-Technical Work
\nAll the original non-technical work responsibilities in SIP-161 are to be conducted directly or indirectly by the CCCs, meaning that CCCs may choose to delegate such responsibilities to an existing CC or determine that there is a lack of suitable CCs for particular roles and take necessary actions to fill the gaps. The goal of CCCs is to make sure that these responsibilities are implemented in a timely and effective manner.
\nProtocol Maintenance Work
\nAll the original protocol maintenance work responsibilities in SIP-161 are to be conducted directly or indirectly by the CCCs, meaning that CCCs may choose to delegate such responsibilities to an existing CC or determine that there is a lack of suitable CCs for particular roles and take necessary actions to fill the gaps. The goal of CCCs is to make sure that these responsibilities are implemented in a timely and effective manner.
\nCCCs will no longer be responsible for protocol road-map and vision.
\nCCCs are no longer to perform their duties with no compensation, they will now be paid a monthly stipend per member under Treasury Councils discretion.
\nThe original rationale for establishing the CCC was to have a governance body that was responsible for the CC's and could advocate on their behalf within the wider Synthetix governance framework. The intent was not for the individual members of the CCC to perform all of the takes and roles assigned to the CCC buyt in stead to provide oversight and monitoring of these takes and ensure that there were sufficient CC resources to enable these functions to be performed efficiently and effectively. The CCC was also intended to be an information conduit between the CC's and the other governance bodies within Synthetix to ensure that if a specific function assigned to the CC's was failing to be executed that the other governing bodies would have a place to discuss and resolve this issue. The intent is for the CCC to ensure that all CC tasks are properly resourced and manage and monitor the performance of each CC in their role.
\nThe Core Contributor Committee elections will no longer happen every epoch (3 months) aligned with the other governance bodies epoch length (currently set to 3 months), CCCs elections will happen every 6 months due to the nature of CCCs responsibilities and the requirement to be consistent with the budgets and other matters.
\nAdditionally, the election process will be set in a way to elect at least 1 person from engineering in order to represent engineering CCs. An ideal split would be to have 1 engineering, 1 product & 1 marketing and/or other CC elected to cover a variety of responsibilities within the protocol.
\n\nSCCP can configure the below values of this SIP:
\nCopyright and related rights waived via CC0.
"}},"pageContext":{"id":"c4c51d56-bbc7-5f1d-b4a1-eb43f8c7b7a9","frontmatter__sip":232,"__params":{"frontmatter__sip":"232"}}},"staticQueryHashes":[]}