This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: devguide: add "core mentors" area to Experts Index
Type: enhancement Stage: resolved
Components: Devguide Versions:
process
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: Nosy List: brett.cannon, chris.jerdonek, eric.araujo, ezio.melotti, ncoghlan, r.david.murray
Priority: normal Keywords: patch

Created on 2012-08-09 21:14 by chris.jerdonek, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
issue-15611-1.patch chris.jerdonek, 2012-08-11 23:19
Messages (6)
msg167836 - (view) Author: Chris Jerdonek (chris.jerdonek) * (Python committer) Date: 2012-08-09 21:14
On the core-mentorship list, Nick Coghlan suggested adding an "area" to the Experts Index for core developers who are on the core-mentorship list (or at least those who wish to be listed).

This issue is to do that.  This can be done by adding a row to the Miscellaneous section with Interest Area "core mentors" or "core mentorship".

http://docs.python.org/devguide/experts.html#miscellaneous
msg167837 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2012-08-09 21:35
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.
msg167840 - (view) Author: Chris Jerdonek (chris.jerdonek) * (Python committer) Date: 2012-08-09 21:50
> I think you should better define the goal of this new section.

I see your point and may not have fully understood the intent.  I'll defer to Nick on this since the initial suggestion was his.  I'm not personally wedded to any particular resolution of the issue. :)
msg168011 - (view) Author: Chris Jerdonek (chris.jerdonek) * (Python committer) Date: 2012-08-11 23:19
Here is an initial patch based on the core developers who responded on core-mentorship.

In response to Ezio's comment (after thinking further), I think the goal would be to provide a list of people that new contributors should feel welcome to add to the nosy list in interest areas that are not otherwise covered (or perhaps on any issue they would like advice on?).

Reasons for limiting this to new contributors and core mentors are (1) to prevent the core developers listed from being added to the nosy list for *every* issue that falls into an area not covered, and (2) in recognition that new contributors benefit from the mentorship and welcome that core mentors are especially interested in providing.

I see that the "core mentorship" label does not fully capture this, but I'm open to other suggestions (e.g. choosing a different label, adding a footnote, or adding another section).  Having this be part of the Experts Index simplifies things like populating the tracker pull-down.
msg185284 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2013-03-26 17:58
Is this still desired? I think it would be better to simply have a message in experts.html to say that if you need help finding someone then email core-mentorship instead of having a list that must be maintained.
msg185461 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2013-03-28 19:01
The devguide already mentions core-mentorship [0][1], and people already ping issues there when necessary, so I agree that this can be closed.

[0]: http://docs.python.org/devguide/help.html#core-mentorship
[1]: http://docs.python.org/devguide/setup.html#build-dependencies
History
Date User Action Args
2022-04-11 14:57:34adminsetgithub: 59816
2013-03-28 19:01:10ezio.melottisetstatus: pending -> closed
resolution: rejected
messages: + msg185461

stage: needs patch -> resolved
2013-03-26 17:58:42brett.cannonsetstatus: open -> pending

messages: + msg185284
2012-08-11 23:19:37chris.jerdoneksetfiles: + issue-15611-1.patch

nosy: + brett.cannon, r.david.murray
messages: + msg168011

keywords: + patch
2012-08-09 21:50:19chris.jerdoneksetmessages: + msg167840
2012-08-09 21:35:34ezio.melottisetmessages: + msg167837
2012-08-09 21:14:55chris.jerdonekcreate