Prysm Eth2 Client Feedback
As part of improving the production readiness of our eth2 client, we are seeking candid feedback from anyone in the community regarding painpoints in using Prysm, developing for Prysm, or integrating Prysm's tools/code into other projects. We are especially looking for specific examples of problems in our codebase or running Prysm itself that prove to be significant hurdles to anyone using the client.

We want to hear your feedback so we can keep improving our work and code health. Please fill this quick survey and let us know your thoughts (your answers will be anonymous).
How satisfied are you with the following aspects of the Prysm project? *
1 = Very dissatisfied   5 = Very satisfied
1
2
3
4
5
N/A
Documentation
Contributing
Team Feedback / Support
Prysm's Codebase
Running a Beacon Node / Validator
Prysm's ETH2 API
What specifically can be improved about our documentation? Please elaborate on painpoints or parts that could be more clear or accessible
Regarding contributions to the codebase: what is the biggest painpoint? What do you think about our aid and response to outside contributors? How can it be improved?
Regarding our tooling / runtime: what could be be made easier for you to use Prysm or develop on Prysm? What specific problems do you encounter when attempting to interact with our client? Please be objective and offer rationale behind the problems you see.
Regarding our codebase: what are specific problems you see that make it hard to reason about? In what ways can it be improved in general? Please be as objective as possible and mention why the rationale behind the problems you enumerate. Mention the packages or files which are problematic.
Regarding structure/naming of our code: in what ways could it be improved? what patterns are problematic and why? how can we make your life easier? Please be objective and offer references to the problems you see
Regarding interactions with the Prysm team: has your overall experience been positive/negative? Do you recall any incidents in which our team could have done a better job assisting you or helping on a task?
Regarding usability of the Prysm client to participate in eth2: what were the major painpoints of running a node and/or a validator?
What operating system and machine do you use to run/develop Prysm?
Submit
Clear form
Never submit passwords through Google Forms.
This form was created inside of Prysmatic Labs. Report Abuse
Google Forms