Bug reporting and feature requests which we plan to move to Github issues in order to get a better integration with Github in general and with the pull requests.
d) erlang-patches (mailing list)
Not used since the start of bugs.erlang.org, we plan to remove it completely. I don't think there is any traffic here.
e) eeps (mailing list)
Intended for discussion about EEPs, originally a limited number of members but now open to anyone to join. We plan to move the discussion to Github issues and pull requests here https://github.com/erlang/eep in the repository where the EEPs are stored.
Re: Workflow-relation of github : erlang.org : mailing lists?
Taking a recent discussion into account, and if you haven't already, might I suggest the Erlang/OTP team also take GitHub Discussions into consideration, at the moment (or even after) GitHub Issues is adopted?
I guess adopting these will potentially change the way the community interacts with this mailing list, too, but it might be worth it to experiment.
Personally, all these new threads about pinning (and the discussion around it) is what made me think that a system more organized than e-mail threads would benefit the community as a whole.