Forum Discussion:
https://tribe.fei.money/t/fip-57-guidelines-for-dao-governance-procedures/3751
Motivation: In light of the recent controversies due to confusions over the governance process, I’d like to propose some governance guideline practices to ensure that future governance votes would proceed in an orderly manner that is satisfactory to everyone.
https://docs.fei.money/governance/fei-improvement-proposals-fips is the currently standing rules of FEI governance, This proposal is meant to supplement the above proposal and incorporate some of the best long standing practices observed by the community. This proposal is meant to aggregate and codify the best of such practices and it is meant to serve as a reference for the future combined TRIBE DAO as well. Since TRIBE DAO is still in its early stages, these draft measures, if approved, are meant to serve as “official governance guidelines” rather than immutable “written laws” for the future operation of the DAO.
Proposal:
A notable exception would be technical rollouts, or routine contract upgrades such as FIP-48, which can be forwarded straight to On-Chain voting/OA timelock if there are no dissensions. Other measures which are already approved in principle by a DAO vote such as individual LaaS funding, can be allowed to move forward directly to OA/snapshot.
An exception can be carved out for proposals that see no dissensions or edits from the original document. In which case the last call is simply a 48 hour countdown announcement.
Only the author(s) of the original forum discussion post should make the snapshot for that particular motion, or allow somebody else to do so with explicit written permission in that original thread.
Upon the passing of a snapshot vote, the poster should announce in their original discourse post, or on discord governance, the specific time they intend to forward the proposal for on-chain voting/Optimistic Approval. If a particular snapshot is a “temperature check” and not meant to be executed directly, it should be clearly indicated by its authors.
Routine protocol upgrades can be exempt from these requirements.
If a proposal outright fails, the author should indicate whether they intend to repost the FIP after editing its contents with community input. A failed FIP should go through the entire process of a new FIP, including another last call, etc.
If a proposal passes, but the authors feel that an edit to its contents are merited before proceeding with onchain voting/OA; the authors should clearly indicate so as soon as possible. The authors should clearly outline every edit from the proposal that has passed the snapshot. This is particularly relevant for the Fei-Rari merge snapshot, and I encourage the community to comment on needed changes for the Fei-Rari merges.
The DAO guardian should be able to veto existing votes if they satisfy the following criteria:
If successfully passed on snapshot, these guidelines would be pinned on the discourse forum and written into the snapshot website for Fei. They would serve as official guidelines for the governance process.
Proposals that blatantly disregards these guidelines should be rapidly informed as such by community members. If the authors do not respond to valid inquiries of procedure, and outright circumvents governance practices, the proposal could be subject to sanctions such as non execution by OA approval, or veto by guardian/DAO.