Python Software Foundation
This page will collects information about the Python Software Foundation.
For more details, please also have a look at the PSF section section on the main python.org web site.
The PSF Voting Members' Wiki is provided for collaboration amongst PSF voting members on topics that are not intended to be shared with the entire internet. The (public) front page of the members' wiki lists some examples of such material. With the new membership model, we will now gradually move more and more content from that wiki to these public pages.
Python Software Foundation
- Board of Directors, Officers, Committees and Members
- PSF Projects
- PSF Fiscal Sponsorship
- PSF License and Trademarks
- Historical Records
Board of Directors, Officers, Committees and Members
PSF Officers -- Our officers take care of the day-to-day business.
PSF Committees -- This lists the committees that are currently active in the PSF.
PSF Members -- Our ever-growing base of people who have a strong interest in Python.
PythonSoftwareFoundation/FellowNominations -- Nominations for PSF Fellowship are listed on this page.
2016: PSF Organizers' Manual
We are currently working on creating a PSF Organizers' Manual which we hope will include how-tos for starting a new PyCon and a user group in your area. The current group working on the manual includes a subset of the 2016 - 2017 Board but may open up to include other community members in the future. The goal is to unite previous efforts into one location and expand upon that, preferably documenting the manual on GitHub to solicit OSS contributions from the community.
Project Leaders: Lorena Mesa
2016: PSF Code of Conduct Workgroup
The PSF has begun to define a policy for handling Code of Conduct violations with email@example.com. PSF Director of Operations Ewa Jodlowska has started outlining the policy with feedback from 2016 - 2017 Board members that have opted to participate in the work group. Progress is ongoing with a goal of voting on an official policy at the July 28 2016 PSF Board meeting.
2015: Elections Workgroup
We are currently working on a charter, and a list of what we want to do. This link is just because I don't know how to make a new wiki page except by referrring to it on an existing page. When we get the charter done, we can update this. Laura Creighton ElectionsWorkgroupPlanning
2014: PSF Python Job Board
The Python job board was run by single volunteers for many years. Since the job board activities have significantly increased in recent years, the PSF wanted to relaunch the project using a team of volunteers. The implementation took a little longer than expected. The new job board was launched in March 2015 and the team is now focusing on the job review part.
Project Leaders: MarcAndreLemburg for the time being
Wiki page: PSF Python Job Board
2011: PyPI Cloud Mirroring Project
A group of PSF members is working on creating a stable PyPI mirroring installation that uses a content delivery network to make PyPI more robust and performant.
PSF Project Leader: MarcAndreLemburg
2011: PSF Python Brochure Project
The PSF is underwriting the development of a professional quality Python image brochure to be used in marketing Python to businesses, governments, schools, etc.
The printed brochure will be made available to conferences, user groups, companies and schools. Please see the website for information on how to order these brochures.
Project page: https://wiki.python.org/psf/PSF%20Python%20Brochure
PSF Project Leader: MarcAndreLemburg
2006 + 2007: Grants Program
The PSF started a grants program to fund Python-related conferences, activities and development. For more information, see PSF Grants.
Note that while the grants program was ended, the PSF is still accepting applications for grants and helps fund conferences, events and project all around the world.
PSF Project Leader: Martin von Löwis
2006: Python Advocacy Coordinator
In August 2006, the PSF board voted to fund a proposal from Jeff Rush for him to act as a full time Python Advocacy Coordinator for a period of six months. In this position, Jeff will work full time on developing and implementing an effective advocacy strategy for Python. His tasks will include writing content for the website and printable brochures for conferences, expanding Python's coverage in technical journals, and building a more effective network of advocacy volunteers from the community. Jeff is known for his work on PyCon 2006, and will be reporting to a group of several PSF directors and officers (initially Stephan Deibel, Chairman of the Board, and Neal Norwitz, Assistant Treasurer).
For details and progress reports see PythonAdvocacyCoordinator.
PSF Project Leader: Jeff Rush
2005: Python.org website redesign
In January 2005, the PSF board voted to fund a proposal (see WebsiteRedesignProposal) from Tim Parkin and Matt Goodall to develop a new framework for the python.org website. The purpose of this is to update the look for the python.org site and move to a more accessible and modern design (based on CSS), while keeping maintenance of the site simple and avoiding reliance on heavy monolithic tools.
This website has now been rolled out, although work on content and the toolset is ongoing. For details see http://www.python.org/dev/pydotorg/website/
Project Leader: Tim Parkin
PSF Fiscal Sponsorship
In 2011, the PSF began to provide Fiscal Sponsorship for Python groups. This allows groups like Boston Python to receive tax-deductible donations through the PSF. Currently, the PSF is sponsoring under Colvin's Model A for "Direct Projects". This model is for organizations that have no independent legal status. It is the same as if the work was being done by PSF volunteers. For further information, refer to FiscalSponsorship.
PSF License and Trademarks
Use of Trademarks or Python License
Our most commonly asked question is about use of the name "Python" or the Python logo, both of which are trademarks. If you want to use these, please see the PSF's Trademark Usage Policy at http://python.org/psf/trademarks. Variants of the logo are available at http://python.org/community/logos.
The second most commonly asked questions involve the Python software license (whether Python can be included in another product, terms of the license, etc). For that, see PythonSoftwareFoundationLicenseFaq.
Important: See PythonSoftwareFoundationLicenseFaq before using the following licenses.
PythonSoftwareFoundationLicenseV2Easy -- Approved Oct 22, 2004 as the official Python Software Foundation License Version 2
PythonSoftwareFoundationLicenseV2Revised -- Revised license that may be used as the basis for Version 3 in the future.
PSF Software Contribution Agreement
The following agreement is being used for contributors to Python, to ensure that all of the source code and documentation in Python are properly licensed.
http://zope.org/Members/lemburg/psc-wiki/FrontPage/view -- wiki containing older information on fund raising, from the days before the PSF become a 501(c)3 non-profit.
PythonSoftwareFoundationLicenseV2 -- Old draft for Python Software Foundation License Version 2 (not adopted and now defunct)
How do Modules Become Part of the Python Distribution?
I've always wondered:
How do modules become part of the Python distribution? What kind of process do you follow, what groups do you participate in, to become a part of that?
I've looked around, but haven't found any web pages on the subject.
-- LionKimbro 2004-06-28 21:22:21
Answer: The final decision is by BDFL pronouncement, but the usual process is that the module is first written as a stand-alone module, and released. After it's been in use for some time, the author makes the suggestion in comp.lang.python or python-dev (both are used, I'm not sure which is preferred) that it be adopted into the standard distribution. This gets discussed by the usual crowd and usually the answer is obvious long before it ever gets to Guido. Certain modules skip the stand-alone stage and are adopted directly into the standard library, but that is usually because the module was written in response to requests, and frequently by an experienced python core developer. If you are interested in getting your module adopted into the core, the #1 question you are sure to be asked is "are you willing to commit to supporting this module for at least the next 5 years?", because unless SOMEONE is willing to volunteer to provide that support the module can't be accepted.
PEP 2, "Procedure for Adding New Modules" contains details. -- David Goodger
I'm not going to delete this answer because it represents useful information which I hope will migrate elsewhere. I should point out, however, that these decisions are nothing to do with the PSF, which normally leaves development work to the developers unless assistance is specifically requested. -- Steve Holden