I think questions about triaging can be asked in the regular core-mentorship as those are useful for all contributors and core devs.

On Dec 9, 2017 10:23 AM, "Carol Willing" willingc@gmail.com wrote:

On Dec 9, 2017, at 11:58 AM, Brett Cannon brett@python.org wrote:

I have a subscription request to python-committers from Cheryl. Im planing rejecting it since we have kept this list only to committees, but I didn't want it to come off as rude when it happens.

I also don't know if we want a triage-only list.

Perhaps it would be a good idea to have a "core mentorship - triage" list which core devs interested in mentoring and triage can help answer questions from Cheryl and Sanyam and others down the road. Nice things about a list like this is it could be low traffic and supportive while helping to build maintainer skills over time. I would be happy to moderate and encourage folks on a list like that.

On Sat, Dec 9, 2017, 05:13 Victor Stinner, victor.stinner@gmail.com wrote:

...

Hi,

For your information, I just sent emails to Julien, Cheryl and Sanyam to notify them that I will their mentor during one month.

I asked them to ask me to double check before merging a pull request (Julien) or closing a bug (Cheryl and Sanyam).

Since I'm trying for formalize the whole process to become a core dev, I kept a copy of my emails to serve as template for future mentors:

https://github.com/vstinner/misc/blob/master/cpython/ mentor_core_dev_email.rst https://github.com/vstinner/misc/blob/master/cpython/ mentor_bug_triage_email.rst

By the way, I'm now working on the "Process to become a core developer" document (maybe becoming a PEP later?) at: https://github.com/vstinner/misc/blob/master/cpython/pep- core_dev_process.rst (I almost didn't change since I sent it to python-committers)

Victor

---

python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

---

python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

---

python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

On Dec 9, 2017, at 3:01 PM, Victor Stinner victor.stinner@gmail.com wrote:

I agree with Mariatta, I don't think that yet another mailing list is needed ;-)

:-)

Brett: it's ok reject Cherl's subscription, maybe it's just a misunderstanding. I added Cheryl in CC to my email to python-commiters when I announced that she got the bug triage permission. Maybe such email should be sent to the core-mentorship mailing instead to be more consistent?

That's a good idea to announce on core-mentorship going forward.

Victor

Le 9 déc. 2017 19:37, "Mariatta Wijaya" mailto:mariatta.wijaya@gmail.com> a écrit : I think questions about triaging can be asked in the regular core-mentorship as those are useful for all contributors and core devs.

On Dec 9, 2017 10:23 AM, "Carol Willing" mailto:willingc@gmail.com> wrote:

...

On Dec 9, 2017, at 11:58 AM, Brett Cannon mailto:brett@python.org> wrote:

I have a subscription request to python-committers from Cheryl. Im planing rejecting it since we have kept this list only to committees, but I didn't want it to come off as rude when it happens.

I also don't know if we want a triage-only list.

Perhaps it would be a good idea to have a "core mentorship - triage" list which core devs interested in mentoring and triage can help answer questions from Cheryl and Sanyam and others down the road. Nice things about a list like this is it could be low traffic and supportive while helping to build maintainer skills over time. I would be happy to moderate and encourage folks on a list like that.

...

On Sat, Dec 9, 2017, 05:13 Victor Stinner, mailto:victor.stinner@gmail.com> wrote: Hi,

For your information, I just sent emails to Julien, Cheryl and Sanyam to notify them that I will their mentor during one month.

I asked them to ask me to double check before merging a pull request (Julien) or closing a bug (Cheryl and Sanyam).

Since I'm trying for formalize the whole process to become a core dev, I kept a copy of my emails to serve as template for future mentors:

https://github.com/vstinner/misc/blob/master/cpython/mentor_core_dev_email.r... https://github.com/vstinner/misc/blob/master/cpython/mentor_core_dev_email.r... https://github.com/vstinner/misc/blob/master/cpython/mentor_bug_triage_email... https://github.com/vstinner/misc/blob/master/cpython/mentor_bug_triage_email...

By the way, I'm now working on the "Process to become a core developer" document (maybe becoming a PEP later?) at: https://github.com/vstinner/misc/blob/master/cpython/pep-core_dev_process.rs... https://github.com/vstinner/misc/blob/master/cpython/pep-core_dev_process.rs... (I almost didn't change since I sent it to python-committers)

Victor

---

python-committers mailing list python-committers@python.org mailto:python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/ https://www.python.org/psf/codeofconduct/

---

python-committers mailing list python-committers@python.org mailto:python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/ https://www.python.org/psf/codeofconduct/

---

python-committers mailing list python-committers@python.org mailto:python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/ https://www.python.org/psf/codeofconduct/

---

python-committers mailing list python-committers@python.org mailto:python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/ https://www.python.org/psf/codeofconduct/

On 10 December 2017 at 09:46, R. David Murray rdmurray@bitdance.com wrote:

The point is, in Martin's judgement (and I have had no reason to doubt it in the years that have followed) is that it is a far more common problem for newly promoted people to be afraid to screw up than it is for someone to go rogue and not listen when communicated with. In my experience the latter has happened only once, and we have a lot of people with triage privileges.

+1 - "Who am I to have this power?" is a pretty common reaction to community promotions, so erring on the side of "I trust your judgement, so you should trust your judgement" is a good way to go.

But at the same time, we should make it clear that "Help me better calibrate my judgement" is an entirely appropriate use case for the core-mentorship list (and we keep those archives closed so they're not available to search engines).

Cheers, Nick.

-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia

On Dec 9, 2017, at 20:41, Nick Coghlan ncoghlan@gmail.com wrote:

+1 - "Who am I to have this power?" is a pretty common reaction to community promotions, so erring on the side of "I trust your judgement, so you should trust your judgement" is a good way to go.

But at the same time, we should make it clear that "Help me better calibrate my judgement" is an entirely appropriate use case for the core-mentorship list (and we keep those archives closed so they're not available to search engines).

Very well said, Nick. It’s useful to remind new contributors that very few things are irreversible, and that there are lots of outlets for asking questions.

-Barry