Greetings,

One crucial missing piece in the Python world is the focus

on internals of projects. You have many talks on usage and

scaling but not enough on internals. Even less workshops.

For OpenSource to thrive, you need people who master the codebase.

It's a long process. You get there by having core contributors over 

time. How does a contributor becomes a core one? By getting the feet wet

into the codebase and tackling more difficult as time passes. That's why 

instead of waiting for people to find issues, work on it, wait for validation,

we can improve the training process without damage to the codebase.

People get the educational version of the repo, solve the issues at their

own pace up to the level where they'll feel confident to try a meaningful

PR. Seeing it with the eye of a knowledgeable person makes will make them

PR not just for the sake of PR but because of a real need. One practical

way is also to point the intermediate steps to resources on the internet, like

this and that C articles to get started with C, this article to understand this C 

behaviour, this talk at this conf to understand this part of the C API, i built a

tool specifically to document those intermediate steps by gathering resources 

on the internet, will start using it soon: https://linkolearn.com/. I  am part of the 

Flask Community Workgroup (It's due to be announced soon, but here is the link:

https://flaskcwg.github.io/). One of the aims of it is education, a good deal about

internals. We aim to roll out some initiatives by next year. What caused me to

write the first post is that there seems to be a bottleneck somewhere when you

see contributors overwhelmed by OpenSource tasks. If it were some obscure project

I understand but not one of the most popular OpenSource product of today.