Add Josh from Protocol Support #468
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Name: Josh Davis (@joshdavislight)
Team: Protocol Support
Start time: 2025-06
Weight: 1
Eligibility:
Josh has been part of EF for more than 3 years now, and with the restructure last year, he became fully dedicated to work on the protocol. As a part of Protocol Support team, he has been helping to conduct ACD calls and took technical responsibility over almost all core developer calls. With this role he also helped to develop ACDbot and he is also contributing to Forkcast, making the all integrations with dev process smoother. His other work was on publications like Pectra Book and organizing EF internship that helped internal protocol teams. The major part of his work is dedicated to Ethereum Protocol Fellowship and Protocol Studies.
I want to mainly highlight his work on EPF. We worked on 4 cohorts of the fellowship together, helped to bring dozens of new developers to the core protocol. Many of them are now part of Protocol Guild and can vouch for benefits of this work. I understand there was discussion whether EPF organization work is indeed eligible and with this PR I'd like to argue for this. Maintaining the developer talent and knowledge base should be crucial for sustainability of the protocol. If the Guild decides it's not the case, I would propose Josh with 0.5 weight and lower my multiplier also to 0.5 because almost half of our time during year is dedicated to this, at least in the past.
Some of his contributions:
ACD calls
Forkcast contributions and features
EIP updates
Fellowship and study group