While the proposed timeline demonstrates an admirable desire to move the on-chain program forward, there are several compelling reasons why this 7-day discussion period is insufficient for such a foundational decision:
Timing Concerns:
The mid-July timeframe poses significant challenges as it coincides with peak summer period when many community members are on vacation or have reduced availability. More critically, scheduling this discussion right before Web3Summit creates a direct conflict of priorities. Many ambassadors and key stakeholders will be focused on preparation for this major industry event, potentially limiting their ability to engage meaningfully in discussions that will shape the future of the on-chain program.
Importance of Deliberation:
The on-chain fellowship represents a fundamental shift in how the program operates. These are not incremental changes but foundational structural decisions that will impact the ecosystem for years to come. Seven days simply doesn’t provide adequate time for:
- Thorough review of pallet changes and their implications
- Meaningful community feedback and iteration
- Proper consideration of onboarding plans and their long-term effects
- Resolution of potential concerns or conflicts that may arise
Risk of Rushed Implementation:
History shows that hastily implemented foundational changes often require significant time and resources to rectify later. The principle of “measure twice, cut once” applies particularly well here. Taking additional time now to ensure proper community alignment and technical soundness will save considerable effort down the road. The cost of delays pales in comparison to the potential cost of having to restructure or fix rushed decisions post-implementation.
Governance Process Integrity:
The mention that this requires a vote on OpenGov to be included in the RTU (Runtime Upgrade) underscores the significance of these decisions. Such consequential changes deserve the full democratic process that OpenGov provides, which inherently requires adequate time for proposal review, community discussion, and informed voting.
Recommendation:
Consider extending the discussion period to at least 14-21 days, scheduled after Web3Summit when the community can dedicate proper attention to these crucial decisions. This would demonstrate respect for the importance of the on-chain program while ensuring robust community participation and thorough deliberation.