# Some thoughts on Tezos governance **URL:** https://forum.tezosagora.org/t/some-thoughts-on-tezos-governance/4362 **Category:** Philosophy and Economics **Created:** [March 6, 2022, 1:30pm UTC](https://forum.tezosagora.org/t/some-thoughts-on-tezos-governance/4362 "2022-03-06T13:30:49Z") **Posts on this page:** 1 **Showing post:** 4
### Author: ![noodlestomatojuice](https://forum.tezosagora.org/user_avatar/forum.tezosagora.org/noodlestomatojuice/32/1358_2.png) [@noodlestomatojuice](https://forum.tezosagora.org/u/noodlestomatojuice) #### Post date: [April 8, 2022, 5:29pm UTC](https://forum.tezosagora.org/t/some-thoughts-on-tezos-governance/4362/4 "2022-04-08T17:29:11Z")
@Ali and I brainstormed the idea of allowing patches during the governance process in our thread: > [@How can we incorporate the patching of issues found during protocol upgrade testing into the on-chain governance process?](https://forum.tezosagora.org/t/how-can-we-incorporate-the-patching-of-issues-found-during-protocol-upgrade-testing-into-the-on-chain-governance-process/3895/6): > > So an “optimistic” algorithm that applies the way you voted (yay, nay, pass) for the first iteration of the non-patched proposal to any subsequent patches of that same proposal, unless you explicitly vote no. With a potential limitation that allows only the proposer of the original amendment to propose the patch. I like the suggestion and I think it’s definitely worth discussing. I do wonder if limiting who can propose a patch is a benefit to security, maybe we can discuss further. --- _[View the full topic](https://forum.tezosagora.org/t/some-thoughts-on-tezos-governance/4362)._