-
Notifications
You must be signed in to change notification settings - Fork 699
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
[Deprecation] Deprecate Gov1 pallets #168
Comments
@kianenigma @ggwpez what's the full list of Gov1 pallets? |
This is related to #485 |
|
noting here a possible deprecating strategy for these suggested by Gav:
|
This suggestion by Gav is already covered in the deprecation process, except for the date note that I will add. |
Isn't things like collective and membership are still being used? Best is to check the Kusama runtime and see what pallets are still in there as a part of the governance process. |
Yup I checked. All instances of |
But they might be still used in system parachains such as All in all, I would argue that between the 5, Moreover, paritytech/substrate#12588 will make Contrary, while we have the gov v2 pallets, something like All in all, i think |
I see what you mean now, thanks for clarifying 👍 |
Can we have some process for such ecosystem wide impact breaking changes? I can’t be just an informal decision from a few devs. It can be a formal decision from a few devs if there is a formal process used with documents of the process. Yeah I know there will be a depreciation process and I am sure someone will notify you if you deprecated that something shouldn’t be depreciated, but still, how do you decide what should be depreciated? Besides, there are many other less used pallets in FRAME. Have you considered remove those first? e.g. atomic-swap, insecure-randomness-collective-flip, lottery, nicks. |
As mentioned in the issue description there is indeed a deprecation process for this #182. We are indeed working on improving processes and documenting them, but of course there is still a lot of work to be done. All constructive suggestions are welcome. There might be other deprecations in the future, this issues is about Gov1. |
I am asking for the process to determine what pallet to remove from this repo and apply this process to less used pallets first before gov1 pallets. This process happens before the deprecation process. Or in other words, the deprecation process is only a step in this pallet removal process. |
@muharem could you please check the list of pallets to deprecate? |
@juangirini I can only add that |
Gov1 pallets that have a Gov2 alternative will be deprecated and eventually archived. Any team external to Parity will be free to clone that repo and maintain it. |
Motivated by the conversation started in paritytech/substrate#14241 (comment) Gov1 pallets should be deprecated
Pallets to deprecate
They should follow the Deprecation Process.
The text was updated successfully, but these errors were encountered: