Update with commonwealth window #10
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I added the suggestion for 2 week minimum time window for commonwealth discussions before getting something up on chain as mentioned here: https://forum.regen.network/discussion/4328-proposal-for-discussion-formalize-the-use-of-commonwealth I also added a mention that emergency upgrades may not have any formal onchain governance and may just be informal consensus among validators coordinated by the core dev team to execute a patch.
ryanchristo
reviewed
Apr 19, 2022
| @@ -18,9 +18,9 @@ The following guidelines should be taken into consideration before submitting an | |||
|
|
|||
| - Once a forum discussion has started, a link to the discussion should be shared publicly in the #governance channel of the Regen Network [Discord Server](https://discord.gg/regen-network) and on Telegram and Twitter (tagging [@regen_network](https://twitter.com/regen_network)). | |||
|
|
|||
| - The time between socializing the proposal and submitting the proposal will vary depending on the proposal and community engagement but generally a proposal should be brought to discussion *at least* one week before submitting the proposal on chain. | |||
| - The time between socializing the proposal and submitting the proposal will vary depending on the proposal and community engagement but generally a proposal should be brought to discussion on commonwealth *at least* two weeks before submitting the proposal on chain. | |||
There was a problem hiding this comment.
We may want to have an official proposal for this change. The idea with proposal 10 was to update the voting period but to also introduce guidelines that are updated through a governance process:
With that being said, any significant changes to the guidelines should go through the governance process in the form of a text proposal.
I think this change along with any others would be the result of Formalize the Use of Commonwealth.
There was a problem hiding this comment.
Suggested change
| - The time between socializing the proposal and submitting the proposal will vary depending on the proposal and community engagement but generally a proposal should be brought to discussion on commonwealth *at least* two weeks before submitting the proposal on chain. | |
| - The time between socializing the proposal and submitting the proposal will vary depending on the proposal and community engagement but generally a proposal should be brought to discussion on [Commonwealth](https://forum.regen.network/) *at least* two weeks before submitting the proposal on chain. |
ryanchristo
reviewed
Apr 19, 2022
|
|
||
| - In certain circumstances, an emergency proposal may need to be submitted. An emergency proposal fixes a security vulnerability or a critical bug in the software and in which case these guidelines may not apply. | ||
| - In certain circumstances, an emergency proposal may need to be submitted. An emergency proposal fixes a security vulnerability or a critical bug in the software and in which case these guidelines may not apply. Emergency upgrades will likley happen outside of the formal onchain governance process due to security concerns. |
There was a problem hiding this comment.
Suggested change
| - In certain circumstances, an emergency proposal may need to be submitted. An emergency proposal fixes a security vulnerability or a critical bug in the software and in which case these guidelines may not apply. Emergency upgrades will likley happen outside of the formal onchain governance process due to security concerns. | |
| - In certain circumstances, an emergency proposal may need to be submitted. An emergency proposal fixes a security vulnerability or a critical bug in the software and in which case these guidelines may not apply. Emergency upgrades will likely happen outside of the formal on-chain governance process due to security concerns. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added the suggestion for 2 week minimum time window for commonwealth discussions before getting something up on chain as mentioned here:
https://forum.regen.network/discussion/4328-proposal-for-discussion-formalize-the-use-of-commonwealth
I also added a mention that emergency upgrades may not have any formal onchain governance and may just be informal consensus among validators coordinated by the core dev team to execute a patch.