Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lowering Democracy Pallet's Settings #45

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

Nolan730
Copy link

@Nolan730 Nolan730 commented May 6, 2022

We are having some problems due to high launch/execute times. We need to lower those settings to solve this problem. I didnt include numbers since we should talk about suitable numbers

@Nolan730
Copy link
Author

Nolan730 commented May 6, 2022

image
image
image
Also @takemiyamakoto mentioned about these problems at telegram. Lowering these settings can solve them

open_rfps/Lowering Democracy Pallet's Settings Outdated Show resolved Hide resolved
open_rfps/Lowering Democracy Pallet's Settings Outdated Show resolved Hide resolved
open_rfps/Lowering Democracy Pallet's Settings Outdated Show resolved Hide resolved
open_rfps/Lowering Democracy Pallet's Settings Outdated Show resolved Hide resolved
open_rfps/Lowering Democracy Pallet's Settings Outdated Show resolved Hide resolved
Nolan730 and others added 6 commits May 6, 2022 14:24
Co-authored-by: William Richter <88400283+WRRicht3r@users.noreply.github.com>
Co-authored-by: William Richter <88400283+WRRicht3r@users.noreply.github.com>
Co-authored-by: William Richter <88400283+WRRicht3r@users.noreply.github.com>
Co-authored-by: William Richter <88400283+WRRicht3r@users.noreply.github.com>
Co-authored-by: William Richter <88400283+WRRicht3r@users.noreply.github.com>
@takemiyamakoto
Copy link
Contributor

The long times are a feature, not a bug. We need ample time for review in case unknown people submit proposals.

@Nolan730
Copy link
Author

Nolan730 commented May 7, 2022

The long times are a feature, not a bug. We need ample time for review in case unknown people submit proposals.

I totally agree. I dont suggest to make it 1-2 days. I think 7 days of launch period, 7 days voting and 1 days of executing time is plenty. If we have an option to stop community members from proposing some functions like minting/runtime update, there wont be a spam.

@Danby7
Copy link

Danby7 commented May 7, 2022

Shorter timeframes (although not so short as to be open to manipulation) would be great, if feasible, as it would most likely result in higher engagement/participation from the community. People probably lose awareness about proposals that sit for weeks on end without being acted on. Not sure how practical making such changes would be though, with regard to resources.

@Nolan730 Nolan730 requested a review from WRRicht3r May 8, 2022 18:00
@Nolan730
Copy link
Author

Nolan730 commented May 27, 2022

I would like to offer these settings: (if i miss a setting, let me know)
Launch time period: 3 days
Voting period: 6 days
Execution time: 1 days

We will be able to process 1 proposal per 3 day, have enough time(6 days) for voting and enough time(1 days) for emergency cancellation by techcomitte. Also we will get rid of the less important proposals and lower the queue at council/techcomitte votings. Currently we have 5 voting at queue(one was in council since 3-4 days) and processing very slowly. I suggest we make these changes immediately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants