Re: [python-committers] Proposing Mark Shannon to be a core developer
Thanks Mariatta! It would also be nice if we gave new committers a task along the lines of "mentor one woman or other person of diversity through their first non-trivial PR". (If the new committer is not comfortable actually merging the PR they can ask a more experienced core dev to do that -- after all new core devs are supposed to be mentored themselves by a more experienced core dev.) Even nicer would be if *every* core dev made a commitment to "sponsor" at least one person of diversity. I understand not everyone has the time. But perhaps *some* core devs will volunteer! Increasing the core's diversity is a very important goal to ensure the future health of Python. On Tue, May 15, 2018 at 4:51 PM, Mariatta Wijayawrote: > Part of the new core dev initiation should be watching this talk, titled > "What is a Python Core Developer?" https://youtu.be/hhj7eb6TrtI > > On Tue, May 15, 2018, 11:35 AM Guido van Rossum wrote: > >> Let's stop the email barrage, Mark is in. Can someone tell Mark what to >> do? >> >> -- --Guido van Rossum (python.org/~guido) ___ 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
Part of the new core dev initiation should be watching this talk, titled "What is a Python Core Developer?" https://youtu.be/hhj7eb6TrtI On Tue, May 15, 2018, 11:35 AM Guido van Rossumwrote: > Let's stop the email barrage, Mark is in. Can someone tell Mark what to do? > > ___ 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
Let's stop the email barrage, Mark is in. Can someone tell Mark what to do? On Tue, May 15, 2018 at 12:27 AM, Victor Stinnerwrote: > 2018-05-14 16:41 GMT-04:00 Larry Hastings : > > Dr. Mark Shannon contributed the "key sharing dictionary" to Python, > writing > > both the PEP and the implementation. This shipped in Python 3.3 and was > > listed as one of the top features of that release as according to the > > "What's New?" document. > > > > We've asked Mark in the past if he'd be interested in becoming a core > > developer--and he actually said no. At the time he said he didn't like > our > > antiquated workflow. Now that we've switched to the git-based core dev > > workflow, this objection is gone, and he's now interested in accepting > the > > commit bit and the responsibilities that it entails. > > > > I suspect you, my colleagues in CPython core development, will be > surprised > > at the current state of affairs. I'm expecting a load of "you mean Mark > > *isn't* a core developer yet?" replies. > > Wait. Mark is already a core dev, right? I don't understand your email :-) > > +1, obvisouly. > > 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/ > -- --Guido van Rossum (python.org/~guido) ___ 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
2018-05-14 16:41 GMT-04:00 Larry Hastings: > Dr. Mark Shannon contributed the "key sharing dictionary" to Python, writing > both the PEP and the implementation. This shipped in Python 3.3 and was > listed as one of the top features of that release as according to the > "What's New?" document. > > We've asked Mark in the past if he'd be interested in becoming a core > developer--and he actually said no. At the time he said he didn't like our > antiquated workflow. Now that we've switched to the git-based core dev > workflow, this objection is gone, and he's now interested in accepting the > commit bit and the responsibilities that it entails. > > I suspect you, my colleagues in CPython core development, will be surprised > at the current state of affairs. I'm expecting a load of "you mean Mark > *isn't* a core developer yet?" replies. Wait. Mark is already a core dev, right? I don't understand your email :-) +1, obvisouly. 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
On 2018-05-14 16:41, Larry Hastings wrote: > > > Dr. Mark Shannon contributed the "key sharing dictionary" to Python, > writing both the PEP and the implementation. This shipped in Python 3.3 > and was listed as one of the top features of that release as according > to the "What's New?" document. > > We've asked Mark in the past if he'd be interested in becoming a core > developer--and he actually said no. At the time he said he didn't like > our antiquated workflow. Now that we've switched to the git-based core > dev workflow, this objection is gone, and he's now interested in > accepting the commit bit and the responsibilities that it entails. > > I suspect you, my colleagues in CPython core development, will be > surprised at the current state of affairs. I'm expecting a load of "you > mean Mark *isn't* a core developer yet?" replies. > +1 ___ 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
+1 -- Best regards, Łukasz Langa > On May 14, 2018, at 4:41 PM, Larry Hastingswrote: > > > > Dr. Mark Shannon contributed the "key sharing dictionary" to Python, writing > both the PEP and the implementation. This shipped in Python 3.3 and was > listed as one of the top features of that release as according to the "What's > New?" document. > > We've asked Mark in the past if he'd be interested in becoming a core > developer--and he actually said no. At the time he said he didn't like our > antiquated workflow. Now that we've switched to the git-based core dev > workflow, this objection is gone, and he's now interested in accepting the > commit bit and the responsibilities that it entails. > > I suspect you, my colleagues in CPython core development, will be surprised > at the current state of affairs. I'm expecting a load of "you mean Mark > *isn't* a core developer yet?" replies. > > > Submitted for your consideration, > > > /arry > ___ > 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
+1 Yury -- Yury ___ 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
+1 On Mon, May 14, 2018, 6:47 PM INADA Naokiwrote: > +1 > > 2018年5月15日(火) 6:55 Ivan Levkivskyi : > >> +1 >> >> Yes, I actually thought he is a core dev for ages :-) >> > > Me too. > > >> -- >> Ivan >> >> >> >> On 14 May 2018 at 17:42, Eric Snow wrote: >> >>> +1 >>> >>> -eric >>> >>> On Mon, May 14, 2018 at 4:41 PM, Larry Hastings >>> wrote: >>> > >>> > >>> > Dr. Mark Shannon contributed the "key sharing dictionary" to Python, >>> writing >>> > both the PEP and the implementation. This shipped in Python 3.3 and >>> was >>> > listed as one of the top features of that release as according to the >>> > "What's New?" document. >>> > >>> > We've asked Mark in the past if he'd be interested in becoming a core >>> > developer--and he actually said no. At the time he said he didn't >>> like our >>> > antiquated workflow. Now that we've switched to the git-based core dev >>> > workflow, this objection is gone, and he's now interested in accepting >>> the >>> > commit bit and the responsibilities that it entails. >>> > >>> > I suspect you, my colleagues in CPython core development, will be >>> surprised >>> > at the current state of affairs. I'm expecting a load of "you mean >>> Mark >>> > *isn't* a core developer yet?" replies. >>> > >>> > >>> > Submitted for your consideration, >>> > >>> > >>> > /arry >>> > >>> > ___ >>> > 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/ >> > ___ > 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
14.05.18 23:41, Larry Hastings пише: Dr. Mark Shannon contributed the "key sharing dictionary" to Python, writing both the PEP and the implementation. This shipped in Python 3.3 and was listed as one of the top features of that release as according to the "What's New?" document. We've asked Mark in the past if he'd be interested in becoming a core developer--and he actually said no. At the time he said he didn't like our antiquated workflow. Now that we've switched to the git-based core dev workflow, this objection is gone, and he's now interested in accepting the commit bit and the responsibilities that it entails. I suspect you, my colleagues in CPython core development, will be surprised at the current state of affairs. I'm expecting a load of "you mean Mark *isn't* a core developer yet?" replies. +1 from me. I always wondered why he is not a core developer. ___ 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
+1 2018年5月15日(火) 6:55 Ivan Levkivskyi: > +1 > > Yes, I actually thought he is a core dev for ages :-) > Me too. > -- > Ivan > > > > On 14 May 2018 at 17:42, Eric Snow wrote: > >> +1 >> >> -eric >> >> On Mon, May 14, 2018 at 4:41 PM, Larry Hastings >> wrote: >> > >> > >> > Dr. Mark Shannon contributed the "key sharing dictionary" to Python, >> writing >> > both the PEP and the implementation. This shipped in Python 3.3 and was >> > listed as one of the top features of that release as according to the >> > "What's New?" document. >> > >> > We've asked Mark in the past if he'd be interested in becoming a core >> > developer--and he actually said no. At the time he said he didn't like >> our >> > antiquated workflow. Now that we've switched to the git-based core dev >> > workflow, this objection is gone, and he's now interested in accepting >> the >> > commit bit and the responsibilities that it entails. >> > >> > I suspect you, my colleagues in CPython core development, will be >> surprised >> > at the current state of affairs. I'm expecting a load of "you mean Mark >> > *isn't* a core developer yet?" replies. >> > >> > >> > Submitted for your consideration, >> > >> > >> > /arry >> > >> > ___ >> > 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/ > ___ 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
+1 from me :-) On 14 May 2018 at 21:41, Larry Hastingswrote: > > > Dr. Mark Shannon contributed the "key sharing dictionary" to Python, writing > both the PEP and the implementation. This shipped in Python 3.3 and was > listed as one of the top features of that release as according to the > "What's New?" document. > > We've asked Mark in the past if he'd be interested in becoming a core > developer--and he actually said no. At the time he said he didn't like our > antiquated workflow. Now that we've switched to the git-based core dev > workflow, this objection is gone, and he's now interested in accepting the > commit bit and the responsibilities that it entails. > > I suspect you, my colleagues in CPython core development, will be surprised > at the current state of affairs. I'm expecting a load of "you mean Mark > *isn't* a core developer yet?" replies. > > > Submitted for your consideration, > > > /arry > > ___ > 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
+1 On Mon, May 14, 2018, at 4:41 PM, Larry Hastings wrote: > > > Dr. Mark Shannon contributed the "key sharing dictionary" to Python, > writing both the PEP and the implementation. This shipped in Python 3.3 > and was listed as one of the top features of that release as according > to the "What's New?" document. > > We've asked Mark in the past if he'd be interested in becoming a core > developer--and he actually said no. At the time he said he didn't like > our antiquated workflow. Now that we've switched to the git-based core > dev workflow, this objection is gone, and he's now interested in > accepting the commit bit and the responsibilities that it entails. > > I suspect you, my colleagues in CPython core development, will be > surprised at the current state of affairs. I'm expecting a load of "you > mean Mark *isn't* a core developer yet?" replies. > > > Submitted for your consideration, > > > //arry/ > ___ > 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
+1 Yes, I actually thought he is a core dev for ages :-) -- Ivan On 14 May 2018 at 17:42, Eric Snowwrote: > +1 > > -eric > > On Mon, May 14, 2018 at 4:41 PM, Larry Hastings > wrote: > > > > > > Dr. Mark Shannon contributed the "key sharing dictionary" to Python, > writing > > both the PEP and the implementation. This shipped in Python 3.3 and was > > listed as one of the top features of that release as according to the > > "What's New?" document. > > > > We've asked Mark in the past if he'd be interested in becoming a core > > developer--and he actually said no. At the time he said he didn't like > our > > antiquated workflow. Now that we've switched to the git-based core dev > > workflow, this objection is gone, and he's now interested in accepting > the > > commit bit and the responsibilities that it entails. > > > > I suspect you, my colleagues in CPython core development, will be > surprised > > at the current state of affairs. I'm expecting a load of "you mean Mark > > *isn't* a core developer yet?" replies. > > > > > > Submitted for your consideration, > > > > > > /arry > > > > ___ > > 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
+1 -eric On Mon, May 14, 2018 at 4:41 PM, Larry Hastingswrote: > > > Dr. Mark Shannon contributed the "key sharing dictionary" to Python, writing > both the PEP and the implementation. This shipped in Python 3.3 and was > listed as one of the top features of that release as according to the > "What's New?" document. > > We've asked Mark in the past if he'd be interested in becoming a core > developer--and he actually said no. At the time he said he didn't like our > antiquated workflow. Now that we've switched to the git-based core dev > workflow, this objection is gone, and he's now interested in accepting the > commit bit and the responsibilities that it entails. > > I suspect you, my colleagues in CPython core development, will be surprised > at the current state of affairs. I'm expecting a load of "you mean Mark > *isn't* a core developer yet?" replies. > > > Submitted for your consideration, > > > /arry > > ___ > 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
On 05/14/2018 01:41 PM, Larry Hastings wrote: Dr. Mark Shannon contributed the "key sharing dictionary" to Python, writing both the PEP and the implementation. This shipped in Python 3.3 and was listed as one of the top features of that release as according to the "What's New?" document. We've asked Mark in the past if he'd be interested in becoming a core developer--and he actually said no. At the time he said he didn't like our antiquated workflow. Now that we've switched to the git-based core dev workflow, this objection is gone, and he's now interested in accepting the commit bit and the responsibilities that it entails. +1 -- ~Ethan~ ___ 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/
Re: [python-committers] Proposing Mark Shannon to be a core developer
+1 ___ 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] Proposing Mark Shannon to be a core developer
Dr. Mark Shannon contributed the "key sharing dictionary" to Python, writing both the PEP and the implementation. This shipped in Python 3.3 and was listed as one of the top features of that release as according to the "What's New?" document. We've asked Mark in the past if he'd be interested in becoming a core developer--and he actually said no. At the time he said he didn't like our antiquated workflow. Now that we've switched to the git-based core dev workflow, this objection is gone, and he's now interested in accepting the commit bit and the responsibilities that it entails. I suspect you, my colleagues in CPython core development, will be surprised at the current state of affairs. I'm expecting a load of "you mean Mark *isn't* a core developer yet?" replies. Submitted for your consideration, //arry/ ___ 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/