Skip to content
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.

Eth2 Call 55 #198

Closed
djrtwo opened this issue Jan 13, 2021 · 3 comments
Closed

Eth2 Call 55 #198

djrtwo opened this issue Jan 13, 2021 · 3 comments

Comments

@djrtwo
Copy link
Collaborator

djrtwo commented Jan 13, 2021

Eth2 Call 55 Agenda

call 54

Meeting Date/Time: Thursday 2021/01/14 at 14:00 GMT

Meeting Duration 1.5 hours

Livestream Link

  1. Client Updates
  2. Upgrade 1
  3. Q1 R&D
  4. Research Updates
  5. Networking
  6. Spec discussion
  7. Open Discussion/Closing Remarks
@benjaminion
Copy link
Contributor

  1. hard fork 1

Request: can we try moving away from the "Hard fork" terminology? It's a protocol ugrade. If it results in a contentious fork then we can retrospectively refer to it as a fork. But for non-contentious stuff, I'd much prefer to normalise the use of "upgrade" rather than the very loaded and much misunderstood "hard fork".

Yeah, I know that we have "Fork" terminology in the spec, but this is more about public messaging.

(No doubt I'm whistling in the wind here, but this seems to be an opportunity to try setting some new norms.)

@hwwhww
Copy link
Contributor

hwwhww commented Jan 14, 2021

can we try moving away from the "Hard fork" terminology?

We probably don't have enough time on this call, but I wish we can brainstorm a great versioning theme and a cool release name for the next mainnet consensus upgrade soon. :)

@benjaminion
Copy link
Contributor

My call notes: https://hackmd.io/@benjaminion/BJ2TO360v

@djrtwo djrtwo mentioned this issue Jan 26, 2021
@djrtwo djrtwo closed this as completed Jan 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants