Add Josh from Protocol Support

[taxmeifyoucan]

Name: Josh Davis (@joshdavislight)
Team: Protocol Support
Start time: 2022-11
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, organizing EF internship that helped internal protocol teams and also Protocol Studies program under EPF. The major part of his work is dedicated to Ethereum Protocol Fellowship.

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 became members of client teams, 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. This is meant to propose that organizing the fellowship is an eligible workstream that creates sustainable pipeline for protocol development, not that EPF fellows become eligible themselves. Fellows who made it to the guild follow the regular process of working with client team and are not meant to be eligible for their EPF work.
(edited)

Some of his contributions:

ACD calls
Forkcast contributions and features
EIP updates
EPF

[eserilev]

Josh would be a great addition to the protocol guild IMO

[Inspector-Butters]

I wouldn't be here if it weren't for Josh. I'm pretty sure this holds true for a decent number of other EPF fellows as well. He belongs in PG.

[raxhvl]

+1 to @Inspector-Butters! Josh does amazing work attracting talent through the EPF and internship programs.

[tvanepps]

I am also in support of including EPF as a PG-eligible workstream. a few requirements before I'd want to have this PR merged:

• remove the mention of "Protocol Studies" as this is not being proposed as eligible
• an explicit note that this eligibility is intended just for the coordinators of the EPF program, and not the participating fellows. extending membership to them (as has been suggested in the past by mkalinin here and here) would require a more thoughtful consideration and oversight
• backdate his start date to the start of the EPF-related work, instead of June 2025. if the Summer of Protocols/protocol studies program was a meaningful % of time the last few years, then we can figure out what the balance is in the onboarding form

[taxmeifyoucan]

Thank you @tvanepps! I will edit the PR description to make the eligibility clear. I would keep Protocol Studies just as a mention and clarify as it's basically one part of our EPF work, not a completely separate effort