Hi @Dacha, yes, fully aligned on making the feedback public!
Our goal for HoS Proposal Transparency
- make any proposal trackable end-to-end: from the initial forum post, to Screening Committee review, to feedback, and finally to the voting outcome.
- implement this workflow on GitHub in the short term, as it gives us the tools we need to prototype and iterate quickly while DAO Ops is being established.
- long-term, a proposal’s entire lifecycle should be trackable on-chain.
Why the CoC Screening Committee feedback isn’t yet on GitHub
For the CoC proposal, we tested the GitHub-based process for the first time and ran into several issues. That’s completely expected, we needed to understand how the workflow functions for all parties involved: the proposal author, the Screening Committee, and the HSP Editor.
Why We Decided Not to Put the CoC Proposal to a Sensing Vote Yet
A key point raised in the Screening Committee’s feedback relates to the following section in the CoC proposal:
Moderation and appeals — Independent body of at least 3 members with rotation and recusal rules. To be developed post-ratification.
The Committee was correct to flag this as insufficiently defined. Without clarity on who is responsible for moderation and appeals, and how the process should operate, delegates cannot meaningfully assess the associated costs, both financially and in terms of attention cost, see my comments here.
E.g., if a dedicated tool is required for moderation and appeals, that alone could easily result in a five-digit budget. Delegates must have clarity to evaluate a proposal.
So we, myself included, have some homework to complete before this moves to a vote.
CoC WIP
- Define the appeals body and include it directly in the proposal.
- Review dependencies with other constitutional documents and run the proposal process (including GitHub tracking) through another full pass.
Once these points are clarified, moving toward ratification will make much more sense.
Hope this provides additional context.
Appreciate your comments @Dacha, let’s build strong standards for clarity and transparency at HoS!