-
Notifications
You must be signed in to change notification settings - Fork 335
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
Remove Gov V1 collectives #2643
Conversation
this change was agreed with the MBF
Is it intended that we only remove |
it is intended to remove the Council and Tech Committee collectives, not the whole |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apart from the pipeline failures, the changes look good to me.
Is there a reason for not removing the tests instead of just disabling them?
I am asking because every test (even if skipped/disabled) slows down the test run.
@@ -69,13 +68,8 @@ parameter_types! { | |||
} | |||
|
|||
/// We allow root and Chain council to execute privileged asset operations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/// We allow root and Chain council to execute privileged asset operations. | |
/// We allow Root and General Admin to execute privileged asset operations. |
Co-authored-by: Federico Rodríguez <federico@moonsonglabs.com>
Co-authored-by: Federico Rodríguez <federico@moonsonglabs.com>
Co-authored-by: Federico Rodríguez <federico@moonsonglabs.com>
What does it do?
Adds a migration to remove Council and TechCommitte collective
What important points reviewers should know?
It contains a storage migration. The members of the collective are currently 5 Moonbeam/Moonriver/Moonbase