Ezio Melotti added the comment: I think you should better define the goal of this new section. How would people use this information? * If it's just to know what developers are on the core-mentorship list, I think it's a bit pointless, especially because not all of them might want to be listed or they might be listed and not following it actively; * If it's to know if someone you see on core-mentorship is a core developer, the full list of developers is a better way to check, since it contains all the names; * If (as Nick's message seems to suggest) the goal is to find people willing to be added to the nosy list of issues about orphaned modules, then the "core mentors" header is a bit misleading because people might be on core-mentorship but they might not want to be added to issues (or vice versa);
The last goal makes some amount of sense, but it's somewhat orthogonal with the core-mentorship ML. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15611> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
