Hi @brettcannon - Should we at-least do a call for a org admin and mentor before assuming they wont be available? I can do a call-far, in the python-dev or python-list? And let’s see if that dies due to lack of interest.
Sure! I’m just commenting based on how we typically can’t find anyone for GSoC and so I personally don’t want to push for a call due to lack of time on my part to push it forward.
No. AFAIK, we don’t have it. We only have general bug reports on documentation at bugs.python.org
There could be other projects which might have a focused need.
For celery, we are working on its version 5 architectural plan stage. that might be an interesting idea. which mainly deal with distributed python tasks on the cloud.
If you think this is something we can do, I will be happy to write up a small summary of the discussion on that thread.
I may not be the best person to mentor on this but I can volunteer to help where I can.
There are many resources we can borrow a leaf including that post from Real Python by Anthony and many suggested resources on this link: https://github.com/pyladies/pyladies-maintainers/issues/6 but we can bring all those ideas and create concrete documentation of the Cpython source code.
Something that we can consider moving to python org as a consolidated guide.
Thank you. That’s a worthy project idea. Let’s keep it as a potential one. I think we can find willing developers to review if this project gets worked upon. A dedicated mentor is still required.
I am not sure if the project was restricted to pyladies repo, or can considered a CPython documentation project. But the intention was to work on it as part of pyladies project.