-
Notifications
You must be signed in to change notification settings - Fork 335
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
Ethereum Core Devs Meeting 101 Agenda #224
Comments
Sorry if I stole anyone's thunder posting this, just wanted to write down that I want to talk about EIP-2681 before I forgot. |
Oh nice! Just opened #225 without even checking. Closing, let's use this. @lightclient was leaving EIP-2938 on intentional? On the last call I thought we tabled it until post-Berlin. |
@timbeiko I left it on in case @holiman or @RatanRSur read any deeper into the EIP. However, given the amount to discuss with Berlin it may make sense to table at least for 101. |
Sounds good. I'll remove it for how and if either Martin or Rai wants to bring it up, they can comment here and we'll put it on the agenda :-) |
Breakout-room meeting summary - #223 (comment) |
If possible, I would like 10 to 15 minutes allocated to me going over these prior to the YOLOv3 discussion. I think it will help ensure everyone is on the same page when we start that YOLOv3 discussion and facilitate that going smoothly. If 15 minutes is thought to be too long, then I can limit scope to just the first one (The Path to 2929) and probably narrow it down to 5 uninterrupted minutes. The Path to 2929: https://notes.ethereum.org/kvDtI9BsS6qFdsLDY_YwpQ |
Next meeting's agenda: #228 |
Ethereum Core Devs Meeting 101 Agenda
Agenda
The text was updated successfully, but these errors were encountered: