-
Notifications
You must be signed in to change notification settings - Fork 62
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
ETC Core Devs Call 17: Magneto Upgrade #424
Comments
Are all client teams invited to this call or is it only a Core-Geth decision option? |
All teams. Everyone. |
Will be in attendance. |
I am afraid that I am likely unable to attend the call tomorrow, but just wanted to register my support and ETC Coop's support for the Magneto HF, given the recent disclosure. |
Proposing two schedules for the meeting: Schedule A
Schedule B (accelerated)
|
Meeting concluded with rough consensus on activating schedule B:
And moving to ECIP 1103 to "last call" with review period end on June 4th, 2021. Attendants:
|
Hey going forward I think we need more transparency around these meetings. It’s not like these are just “afternoon tea” calls. I understand that you @q9f organized this well in advance, but I think it’s important we give all contributors the opportunity to be present. Ethereum ACD meetings are good examples of how such calls are handled. I am more than willing to facilitate and record the meetings as well as take down and publish any notes, and recordings, and set up possibly live streams. Anybody not in the ETC GitHub were likely unaware about today’s meeting and did not attend. If at all a possible please ping me or let me know @q9f. ✌🏼 |
I have a meeting recording and can share if it you wish to publish it |
Yes, please. |
You should be able to download it here if you want to mirror it.
|
ETC Core Devs Call 17
Agenda
Schedule A
Schedule B (accelerated)
All fork times est. at 12pm UTC
The text was updated successfully, but these errors were encountered: