Movatterモバイル変換

[0]ホーム
URL:

ContentsMenuExpandLight modeDark modeAuto light/dark, in light modeAuto light/dark, in dark modeSkip to content
Python Developer's Guide
Logo
Python Developer's Guide
Back to top

Motivations and affiliations

CPython core team members participate in the core development process for avariety of reasons. Being accepted as a core team member indicates thatan individual is interested in acquiring those responsibilities, has theability to collaborate effectively with existing core team members, and has hadthe time available to demonstrate both that interest and that ability.

This page allows core team members that choose to do so to provide moreinformation to the rest of the Python community regarding their personalsituation (such as their general location and professional affiliations), aswell as any personal motivations that they consider particularly relevant.

Core team members that wish to provide this additional information add a newentry to thePublished entries section below. Guidelines relatingto content and layout are included as comments in the source code for this page.

Core team members who are available for training, consulting, contract, orfull-time work, or are seeking crowdfunding support for their communitycontributions, may also choose to provide that information here (includinglinking out to commercial sites with the relevant details).

For more information on the origins and purpose of this page, seeGoals of this page.

Published entries

The following core team members have chosen to provide additional detailsregarding their professional affiliations and (optionally) other reasons forparticipating in the CPython core development process:

Brett Cannon (Canada)

Alyssa Coghlan (Australia)

Alyssa began using Python as a testing and prototyping language while workingfor Boeing Defence Australia, and now works for Westpac, supporting theiruse of Python for a range of purposes.

As a core team member, she is primarily interested in helping to ensure Python’scontinued suitability for educational, testing and data analysis use cases,as well as in encouraging good architectural practices when assembling Pythonapplications and test harnesses from open source components.

Note: prior to August 2023, Alyssa used her birth name (Nick Coghlan). Some records(for example, mailing list archives, version control history) will still reference that name.

Steve Dower (United States/Australia)

Steve started with Python while automating a test harness for medicaldevices, and now works for Microsoft on anything that makes Python moreaccessible to developers on any platform.

As a core team member, his focus is on maintaining the already excellentWindows support and improving Python’s ability to be embedded in otherapplications.

Christian Heimes (Germany)

  • Red Hat (Software Developer, Security Engineering / Identity Management)

  • Python Software Foundation (Fellow)

Mariatta (Canada)

Support Mariatta bybecoming a sponsor,sending her ahappiness packet,orpaypal.

R. David Murray (United States)

David has been involved in the Internet since the days when the old IBMBITNET and the ARPANet got cross connected, and in Python programming sincehe first discovered it around the days of Python 1.4. After transitioningfrom being Director of Operations for dialup Internet providers (when thatbusiness started declining) to being a full time independent consultant,David started contributing directly to CPython development. He became acommitter in 2009. He subsequently took over primary maintenance of theemail package from Barry Warsaw, and contributed the Unicode oriented API.David is also active in mentoring new contributors and, when time isavailable, working on the infrastructure that supports CPython development,specifically the Roundup-based bug tracker and the buildbot system.

David currently does both proprietary and open source development work,primarily in Python, through the company in which he is a partner,Murray &Walker, Inc. He has done contract workfocused specifically on CPython development both through the PSF (thekickstart of the email Unicode API development) and directly funded byinterested corporations (additional development work on email funded byQNX, and work on CPython ICC support funded by Intel). He would like tospend more of his (and his company’s) time on open source work, and so isactively seeking additional such contract opportunities.

Antoine Pitrou (France)

Antoine started working with Python in 2005 in order to implement adecentralized virtual world protocol. He started contributing to CPythonin 2007 and became a core team member in 2008. His motivations have beendriven both by the abstract desire to make Python better for the wholeworld, and by the concrete roadblocks he was hitting in professionalsettings. Topics of choice have included interpreter optimizations,garbage collection, network programming, system programming andconcurrent programming.

As a professional, Antoine has been first specializing in networkprogramming, and more lately in open source data science infrastructure.He has made numerous contributions to Numba, Dask and is currently workingfull time on Apache Arrow as a technical leader at QuantStack.

Victor Stinner (France)

Victor is paid by Red Hat to maintain Python upstream and downstream (RHEL,CentOS, Fedora & Software collections). SeeVictor’s contributions toPython.

Kushal Das (India)

Barry Warsaw (United States)

Barry has been working in, with, and on Python since 1994. He attended thefirst Python workshop atNIST in Gaithersburg,MD in 1994, where he met Guido and several other early Python adopters.Barry subsequently worked with Guido for 8 years while atCNRI. Barry has served as Python’s postmaster,webmaster, release manager, Language Summit co-chair,Jython project leader,GNU Mailman project leader, and Python Steering Councilmember in 2019, 2020, 2021, 2024, and 2025.

Eric Snow (United States)

  • Microsoft (Software Developer)

  • Python Software Foundation (Fellow)

Dino Viehland (United States)

Dino started working with Python in 2005 by working on IronPython, animplementation of Python running on .NET. He was one of the primarydevelopers on the project for 6 years. After that he started the PythonTools for Visual Studio project focusing on providing advanced code completionand debugging features for Python. Today he works onCinder improving Pythonperformance for Instagram.

Carol Willing (United States)

Carol is focused on Python’s usage in education and scientific research.She is interested in distributed computing, organizational development,operational workflows, and sustainability of open source projects.

Goals of this page

Theissue metrics automatically collected by the CPython issue trackerstrongly suggest that the current core development process is bottlenecked oncore team time. This is most clearly indicated in the first metrics graph,which shows both the number of open issues and the number of pull requests awaitingreview growing steadily over time, despite CPython being one of the mostactive open source projects in the world. This bottleneck then impacts not onlyresolving open issues and accepting submitted pull requests, but also the process ofidentifying, nominating and mentoring new core team members.

The core commit statistics monitored by sites likeOpenHub provide a goodrecord as towho is currently handling the bulk of the review and maintenancework, but don’t provide any indication as to the factors currently influencingpeople’s ability to spend time on reviewing proposed changes, or mentoring newcontributors.

This page aims to provide at least some of that missing data by encouragingcore team members to highlight professional affiliations in the following twocases (even if not currently paid for time spent participating in the coredevelopment process):

  • members working for vendors that distribute a commercially supportedPython runtime

  • members working for Sponsor Members of the Python Software Foundation

These are cases where documenting our affiliations helps to improve theoverall transparency of the core development process, as well as making iteasier for staff at these organisations to locate colleagues that can helpthem to participate in and contribute effectively to supporting the coredevelopment process.

Core team members working for organisations with a vested interest in thesustainability of the CPython core development process are also encouraged toseek opportunities to spend work time on mentoring potential new coredevelopers, whether through the generalcore mentorship program, throughmentoring colleagues, or through more targeted efforts like Outreachy’s paidinternships and Google’sSummer of Code.

Core team members who are available for consulting or contract work on behalf ofthe Python Software Foundation or other organisations are also encouragedto provide that information here, as this will help the PSF to betterfacilitate funding of core development work by organisations that don’tdirectly employ any core team members themselves.

Finally, some core team members seeking to increase the time they have availableto contribute to CPython may wish to pursue crowdfunding efforts that allowtheir contributions to be funded directly by the community, rather than relyingon institutional sponsors allowing them to spend some or all of their worktime contributing to CPython development.

Limitations on scope

  • Specific technical areas of interest for core team members should be captured intheExperts Index.

  • This specific listing is limited to CPython core team members (since it’sfocused on the specific constraint that is core team member time), but itwould be possible to create a more expansive listing on the Python wiki thatalso covers issue triagers, and folks seeking to join the core team.

  • Changes to the software and documentation maintained by the core team,together with related design discussions, all take place in public venues, andhence are inherently subject to full public review. Accordingly, coredevelopers are NOT required to publish their motivations and affiliations ifthey do not choose to do so. This helps to ensure that core contributionprocesses remain open to anyone that is in a position to sign theContributorLicensing Agreement, the details of which are filed privately with thePython Software Foundation, rather than publicly.

On this page
[8]ページ先頭
©2009-2025 Movatter.jp