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

Eth2.0 Implementers Call 20 Agenda #51

Closed
djrtwo opened this issue Jun 20, 2019 · 3 comments
Closed

Eth2.0 Implementers Call 20 Agenda #51

djrtwo opened this issue Jun 20, 2019 · 3 comments

Comments

@djrtwo
Copy link
Collaborator

djrtwo commented Jun 20, 2019

Eth2.0 Implementers Call 20 Agenda

Meeting Date/Time: Thursday 2019/6/27 at 14:00 GMT

Meeting Duration 1.5 hours

YouTube Live Stream Link

Agenda

  1. Testing Updates
  2. Client Updates
  3. Research Updates
  4. Network
  5. Move to discord
  6. Graffiti in testing
  7. Spec discussion
  8. Open Discussion/Closing Remarks
@GregTheGreek
Copy link

Proposal to move communications to Discord

Rational: Unify communications into a service that can handle:

  1. Notifications correctly
  2. Support groups/channels
  3. Have user roles
  4. A place in which "jumping on a quick call" can be facilitated with ease (We could have an ETH2 "watercooler")

Naturally, Gitter does not meet any of these criteria efficiently. Recently the ETH1/ETH2 Javascript communications migrated to a Discord server where things can be neatly organized into respective sections;

  1. Clients - All client teams can have their own respective channel
  2. Spec - A place to discuss changes to the ongoing spec, perhaps even by version.
  3. Research - Can be broken into the different phases
  4. Tooling - Can be broken into szz, bls, libp2p, etc...

This would allow us to organize ourselves in a much better fashion, keep dialogue on track and ultimately be able to track things we want to track, with notifications.

@protolambda
Copy link

Graffiti use-case in testing

Can we standardize the graffiti field (32 bytes in block body, any data) contents for testing? I.e. put the client vendor ID (to be assigned), node start timestamp, validator version, beacon node version, etc. in there, so we can easily track things on testnets? Maybe even networking details like node IPs, for more analysis? And then on mainnet we let it be real graffiti again, not revealing such data for privacy.

@tvanepps
Copy link

tvanepps commented Jun 27, 2019

consider rotating call times like the Core Dev call has recently proposed?

https://twitter.com/hudsonjameson/status/1142092727531855872

@djrtwo djrtwo mentioned this issue Jun 27, 2019
@djrtwo djrtwo closed this as completed Jul 10, 2019
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

4 participants