[python-committers] Changing commiter status

M.-A. Lemburg mal at egenix.com
Tue Jun 19 14:14:45 EDT 2018


On 19.06.2018 18:39, Brett Cannon wrote:
> On Mon, 18 Jun 2018 at 12:41 M.-A. Lemburg <mal at egenix.com> wrote:
> 
>> On 18.06.2018 21:07, Guido van Rossum wrote:
>>> Hm, unless I misunderstood, MAL's
>>>
>>>> Being a core developer of Python is a status
>>>
>>> suggests that core devs might want to keep this status since it confers
>>> "status" on their person (it looks good on a resume for sure). And I
>>> wouldn't want to make it any harder for a 3rd party to verify someone's
>>> claim to this status in their resume.
>>>
>>> Marc-Andre, is that what you meant?
>>
>> I guess I wasn't clear, sorry.
>>
>> Perhaps the better term is "title" rather than "status". My
>> understanding is that you become core developer and essentially
>> keep this title forever.
>>
>> Whether you actually have your keys in the repo to push a PR
>> or not is a different story and not really related to the "title"
>> you earned.
>>
>> Listing the core developers somewhere on an official page
>> would help with the verification you are referring to. At
>> the moment, we don't seem to have this. It does make a difference
>> on CVs and it's one of the few things we can give back to people
>> when contributing code and time to Python.
>>
>> Hope that's a little clearer.
>>
> 
> Yep, and no one is suggesting you don't get listed as a core dev somewhere.
> Basically the idea is you would swap the Python logo next to your name on
> bugs.python.org to being listed on a page on devguide.python.org in terms
> of visibly being identified as a core dev.

I personally would not want that to happen, since while I
don't have time to contribute code anymore, I still do
comment on tickets.

Ok, let me be even clearer :-)

While I understand that there is a need to show the world that
we need more active core devs, this drive to shelve existing
developers is not a good way to achieve this.

Here's a simple approach which is effective without all the
implied social costs of removing core dev flags:

* create a page with the core devs who have at least 10 commits
  in the last 6 months (the "active" ones):


https://github.com/python/cpython/graphs/contributors?from=2017-12-19&to=2018-06-19&type=c

  (at the moment, this gives 21 entries)

* run a few posts calling for help, pointing people to ways
  of becoming a core developers, the mentoring program,
  sprints to attend, etc.

* create a page listing the core developers to show the world
  who we are and add value to the title in order to make it
  interesting for other developers to get on that page as well

* perhaps also mention some other forms of recognition
  such as Mike's Python Dev of the Week:
  https://www.blog.pythonlibrary.org/category/pydevoftheweek/

* add more ways to add recognition to the core dev title
  to make it more attractive, e.g. an free tickets to PyCon US
  for life, your own page on python.org, etc.

We need to put some carrots out there, and keep refreshing
them.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Experts (#1, Jun 19 2018)
>>> Python Projects, Coaching and Consulting ...  http://www.egenix.com/
>>> Python Database Interfaces ...           http://products.egenix.com/
>>> Plone/Zope Database Interfaces ...           http://zope.egenix.com/
________________________________________________________________________

::: We implement business ideas - efficiently in both time and costs :::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/
                      http://www.malemburg.com/



More information about the python-committers mailing list