I saw a post on the AllCoreDevs gitter channel from Mudit Gupta which illustrates a problem in the community. This person was hoping to get up to speed enough to help with go-ethereum contributions, perhaps unrealistically, but earnestly. There is a need for advanced on-boarding, but the core devs don’t have time to do it and expect new contributors to do the work themselves.
Some architecture diagrams of go ethereum or perhaps a video of someone going over the architecture will greatly help Imo. Otherwise, it will just take hours and hours for a new programmer to start contributing (which, as everyone can see, not many are willing to do).
Docs about implementation internals have a tendency to rot fast. Docs about structures like patricia trees are great, but for a lot of things, the code will always be the best reference. It will take hours and hours to grasp it all, but we try to flag 'good-first-ticket’s to help on-board new devs. And the geth discord server is better suited for general geth-discussion
I am not requesting detailed docs about the implementation. Just a 30 min video walkthrough maybe that says what is where.
And later on this person writes something about contributor motivations:
I don’t want to just pick issues and solve them, I want to get the feel of the code first. I want to learn new things while doing that. I need to enjoy something if I am going to do it for free. I am just not ready enough to do chores that I don’t enjoy doing without any gains.
Are there any ideas about what can be done here?