This is an entirely different request to what was said in OP, and honestly, I don’t think this is a good.
In fact, this is a terrible idea:
- Purely from a legal perspective the official docs have a clear license transfer happening - this is far less certain for mailing lists and github issues. I know it’s fashionable in AI business to ignore these kind of concerns, but the PSF shouldn’t contribute to it. (just because it’s publicly available, doesn’t mean you can do with it whatever you want. In fact, even your plan to scrape it might literally be illegal - I haven’t read the TOC)
- Especially emails have a good chance to contain personal information that people might not want to be easily searchable. There is a mountain of difference between having it archived somewhere and having it feed into an AI system.
- These discussions are riddle with new ideas, half-implemented things and historic, no-longer-relevant discussions. Training an AI on this would probably be worthless unless your goal is to dig through the history instead of learning about python as it is right now. (note: AIs are not good enough to cleanly distinguish this kind of stuff because of their finite context window - and it’s unlikely they will be good enough anytime soon.)
The actual docs are easily part of a single github repo and can easily be feed into an AI bot.
(Also, just in case: I explicitly do not want my contributions to this site be part of any AI chatbot that doesn’t 100% clearly, provably follow CC-BY-NC, as it is legally required to. Good luck finding an AI chatbot that guarantees this…)