Comments (9)
Chain pruning proposal https://gist.github.com/karalabe/60be7bef184c8ec286fc7ee2b35b0b5b
from pm.
Confirmed with @Souptacular that we intend to publish unattributed notes.
from pm.
@HershyatHatch You're asking important questions and I appreciate that. I'm all for shining light :)
@Souptacular said multiple times on the call last week that the meeting would be open only to core devs and researchers ("open" here means open to the usual attendees of the all core devs meetings, i.e., "core devs" somewhat loosely and subjectively defined), that it would not be livestreamed/recorded, and that notes will be taken and may or may not be shared.
I intend to respect his wishes, but I will bring this topic up at the start of the call for brief discussion to ensure we have consensus on this point.
from pm.
@lrettig I asked on twitter, but I will do the old 'double-up' -
What is the thinking behind not recording this call?
from pm.
What is the thinking behind not recording this call?
That is my recollection of the consensus in the room when we decided to have this call, that it will be open to core devs only, that it will not be recorded or livestreamed, and that unattributed notes will be taken and (revision: may be) shared. This was at the request of several core devs who wanted to feel that they could speak openly.
To be clear, this is not my decision and I have no power to unilaterally change this.
@Souptacular if you (or others) have a different understanding please let me know.
from pm.
This was discussed among @AlexeyAkhunov, @Souptacular, @karalabe, @gcolvin, @5chdn and others on the core devs call last week. Notes here. Look for "Hudson: How do we handle the call on the 30th?":
Hudson:
For my purposes definition of core devs is working on low-level projects
There is a grey area including teams such as Infura working on low-level RPC
For now, meeting on 30th is not closed but may be closed to anyone but core devs
Notes may or may not be released
from pm.
So that conversation starts off with Hudson saying.
Hudson: I'm having reservations on how open the meeting on the 30th should be, we said we wanted it to be private, but I think maybe it should be more open. Here are some options..." notes taken, published, livestreamed, etc.
After some further discussion, with no plausible reasons given for keeping it closed
(other than Alexy's concern about his research being used in bad faith, which he more recently said that he no longer has concerns about https://ethereum-magicians.org/t/ethereum-state-rent-for-eth-1-x-pre-eip-document/2018/6?u=hershy)
Greg and Alexy said this:
Greg: Once there are meetings across groups, it shouldn't be secret
Press will report whatever they can find, it won't be complete or accurate
Alexey: If no one else is arguing for it to be closed, let's make it open
After a little more discussion, Hudson sums up thusly:
Hudson: For now, meeting on 30th is not closed but may be closed to anyone but core devs
Notes may or may not be released
So, the consensus in the room, absolutely was not that the call should be closed. The conversation ends with a "for now it is open" (with the both-sides-of-the-fence caveat/disclaimer that it "may be closed".). And now we find out that it has in fact been changed to closed.
That reversal of the "for now it is open" must have come after the call last Friday. So, again I ask:
Being that the consensus on that all devs call was that the call should be 'open' (or at least recorded), what lead to the decision being reversed?
from pm.
And @lrettig I appreciate that this wasn't your decision, nor is it your call to unilaterally change it. I'm really just inquiring as to the process of all this and hoping to get some light shine on that, if possible.
from pm.
Notes are up at https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Eth1x%20Sync%201.md. Closing.
from pm.
Related Issues (20)
- Dencun Interop Testing Call #35 HOT 2
- Comparte el enlace al escritorio
- Execution Layer Meeting 176 HOT 1
- Dencun Interop Testing Call #36 HOT 2
- Execution Layer P2P Breakout #6 HOT 1
- Consensus-layer Call 123 HOT 2
- Verkle Implementers Call #9 HOT 2
- Execution Layer Meeting 177 HOT 5
- Consensus-layer Call 124 HOT 2
- EIP-3074 Breakout Room HOT 1
- EOF Implementers Call #29
- RollCall #2 HOT 2
- EOF Implementers Call #30
- Verkle Implementers Call #10 HOT 1
- Execution Layer Meeting 178 HOT 6
- My problems
- Claim KZG POAP with Github HOT 1
- Dencun Interop Testing Call #37 HOT 2
- Consensus-layer Call 125 HOT 5
- Consensus-layer Call 126 HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pm.