Authors: irishpride1in and Alex.eth
3 days (72h) is not enough time for everyone to read and carefully consider a proposal, nor cast their vote
7 days (168h) will allow enough time for those with busy schedules to carefully consider each proposal and cast their vote
Everyone’s lifestyles, working conditions, and family/community obligations are different and afford users varying degrees of leisure time to devote to reading and considering the implications each proposal might have. This is especially true if the proposal is technical in nature ,or is a topic the user may not be familiar with. Therefore, the current 3 day (72h) voting period may not be enough time for users to form an educated opinion or even participate in voting. This poses a real risk that some individuals or groups may try to push detrimental agendas on short notice to deprive the community the time necessary to absorb the details or consider the impact the proposal might have on the product. For instance, proposing a highly technical proposal veiled in jargon that the average person cannot grasp the true meaning of and pushing it through in 72h seems inappropriate to the ethos of decentralized governance.
In this light, I propose that the community agree to a 7 day minimum voting period to proposals sent to snapshot. This should allow enough time for users to form an educated decision, look at the discussion/comments on discord and the governance forum, and find some time to vote.
As some things will need to move more quickly than 7 days in the event of an emergency, I would also propose that the team or community members via the team have the ability to propose issues with the current 3 day window if needed.
Thank you for your consideration!