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

Agenda: Governance, Jul 14 2020 #313

Closed
2 tasks done
lehnberg opened this issue Jul 4, 2020 · 1 comment · Fixed by #319
Closed
2 tasks done

Agenda: Governance, Jul 14 2020 #313

lehnberg opened this issue Jul 4, 2020 · 1 comment · Fixed by #319
Labels
governance Anything related to governance meetings Anything related to meetings

Comments

@lehnberg
Copy link
Collaborator

lehnberg commented Jul 4, 2020

Solicit suggestions for agenda items for the Governance meeting to be held on Tuesday Jul 14 @ 15:00 UTC in Keybase main lobby. Please comment to provide topics or suggestions.

Proposed agenda

  1. Agenda review
  2. Action point follow ups from previous meeting
    • Funding requests processed?
    • Spending logs updated?
  3. Documentation progress
  4. Code of conduct progress
  5. RFC & sub-teams update
  6. Other questions
@lehnberg lehnberg added meetings Anything related to meetings governance Anything related to governance labels Jul 4, 2020
@johndavies24
Copy link

It may be worth revisiting announcing future HFs. If we have reason to believe that future hardforks are inevitable because of already known reasons (e.g. some known things are missing and a lot of new tech is emerging) and time is necessary to implement these things, then we should communicate that and set people's expectations. Maybe future dates are set for a time-frame more like 1-3 years? I am not sure how to do this in a way that allows for flexibility and also reduces fork risks, maybe trigger fork X blocks after some UTXO held by core was spent? Just an idea, but if we already know reasons that future HF will be necessary I think it would be best to set that expectation now.

If there are no known reasons to expect future hardforks then it is alright to keep everything as is and let new reasons arise organically.

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

Successfully merging a pull request may close this issue.

2 participants