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

Implement governance improvements based on FIP36 experience #48

Open
dmc314 opened this issue Nov 30, 2022 · 1 comment
Open

Implement governance improvements based on FIP36 experience #48

dmc314 opened this issue Nov 30, 2022 · 1 comment
Assignees
Labels

Comments

@dmc314
Copy link
Contributor

dmc314 commented Nov 30, 2022

eta: 2023-02-28

Work with FF to implement relevant CEL governance recommendations from FIP36 retrospective.

  • Define a clearer process for governance of network upgrades, be they one or a mixture of: 1) a regularly scheduled update every X months, 2) an emergency FIP or update, and 3) the status quo of project-driven, opportunistic timelines.
  • Work with DMOB and FF to ensure Fil Poll code is updated based on lessons learned in FIP 36, to eliminate double counting, deal with msig wallets, include all necessary data for locked token calcs, and process for relevant constituents
  • Define clearer policy for accept/reject criteria and voting constituents
  • Better define token holder voting to account for obstacles with tokens held by exchanges, msigs, lenders, etc
  • Clarify definition and responsibilities of Core Devs
  • Add a section to FIP draft template for “Anticipated Risks” and “Teams Potentially Affected”. This pre-assessment could provide an early indication of contentious FIPs if many teams or stakeholders stand to be effected
@dmc314
Copy link
Contributor Author

dmc314 commented Jan 9, 2023

CEL actively participating in Governance revision discussions: filecoin-project/FIPs#585

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

No branches or pull requests

2 participants