Differences between revisions 63 and 64
Revision 63 as of 2012-03-27 02:44:44
Size: 7696
Editor: nat-pool-bne-t1
Comment:
Revision 64 as of 2012-09-28 18:26:45
Size: 8629
Editor: PaulBoddie
Comment: wiki restore 2013-01-23
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Line 2: Line 3:
Line 5: Line 7:
Line 7: Line 10:
The [[http://wiki.python.org/psf/|PSF Members' Wiki]] is provided for collaboration amongst PSF 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.
Line 9: Line 11:
<<TableOfContents()>> The [[psf/|PSF Members' Wiki]] is provided for collaboration amongst PSF 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.


<<TableOfContents>>
Line 13: Line 18:
Line 14: Line 20:

Additional information about the board of directors is also available on PythonSoftwareFoundationBoard.
 Additional information about the board of directors is also available on [[PythonSoftwareFoundationBoard|PythonSoftwareFoundationBoard]].
Line 18: Line 23:
 * [[http://www.python.org/psf/committees|PSF Committees]] -- This lists the committees that are currently active in the PSF.
 * [[http://www.python.org/psf/members/#members|PSF Members]] -- Our ever-growing base of people who have a strong interest in Python.
Line 19: Line 26:
 * [[http://www.python.org/psf/committees|PSF Committees]] -- This lists the committees that are currently active in the PSF.

 * [[http://www.python.org/psf/members/#members|PSF Members]] -- Our ever-growing base of people who have a strong interest in Python.
Line 25: Line 29:
Line 26: Line 31:
Line 29: Line 35:
Line 30: Line 37:
Line 33: Line 41:
PSF Project Leader: Jesse Noller
PSF Project Leader: Brian Curtin
Line 37: Line 47:
''Active project''
''Active project - currently on hold''
Line 41: Line 53:
PSF Project Leader: MarcAndreLemburg
PSF Project Leader: [[MarcAndreLemburg|MarcAndreLemburg]]
Line 45: Line 59:
Line 46: Line 61:
Line 49: Line 65:
Line 50: Line 67:
Line 53: Line 71:
PSF Project Leader: MarcAndreLemburg
PSF Project Leader: [[MarcAndreLemburg|MarcAndreLemburg]]
Line 57: Line 77:
Line 59: Line 80:
The PSF started a grants program to fund Python-related conferences, activities and development.  For more information, see [[http://www.python.org/psf/grants/|PSF Grants]].
The PSF started a grants program to fund Python-related conferences, activities and development. For more information, see [[http://www.python.org/psf/grants/|PSF Grants]].
Line 63: Line 86:
Line 64: Line 88:
Line 67: Line 92:
Line 69: Line 95:
In August 2006, the PSF board voted to fund [[http://python.org/psf/grants/advocacy/orig-proposal.pdf|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).
Line 71: Line 96:
For details and progress reports see PythonAdvocacyCoordinator. In August 2006, the PSF board voted to fund [[http://python.org/psf/grants/advocacy/orig-proposal.pdf|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|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|PythonAdvocacyCoordinator]].
Line 75: Line 104:
Line 76: Line 106:
Line 79: Line 110:
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.
Line 83: Line 111:
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/
In January 2005, the PSF board voted to fund a proposal (see [[WebsiteRedesignProposal|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/
Line 89: Line 119:

== 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|FiscalSponsorship]].

Line 90: Line 127:
Line 93: Line 131:
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.
Line 97: Line 132:
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.
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|PythonSoftwareFoundationLicenseFaq]].
Line 103: Line 140:
'''Important''': See PythonSoftwareFoundationLicenseFaq before
using the following licenses.
Line 106: Line 141:
 * PythonSoftwareFoundationLicenseV2Easy -- Approved Oct 22, 2004 as the official Python Software Foundation License Version 2 '''Important''': See [[PythonSoftwareFoundationLicenseFaq|PythonSoftwareFoundationLicenseFaq]] before using the following licenses.
Line 108: Line 143:
 * PythonSoftwareFoundationLicenseV2Revised -- Revised license that may be used as the basis for Version 3 in the future.
 * [[PythonSoftwareFoundationLicenseV2Easy|PythonSoftwareFoundationLicenseV2Easy]] -- Approved Oct 22, 2004 as the official Python Software Foundation License Version 2
 * [[PythonSoftwareFoundationLicenseV2Revised|PythonSoftwareFoundationLicenseV2Revised]] -- Revised license that may be used as the basis for Version 3 in the future.
Line 112: Line 150:
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.

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.
Line 118: Line 156:
Line 120: Line 159:
Line 121: Line 161:
 * [[PythonSoftwareFoundationLicenseV2|PythonSoftwareFoundationLicenseV2]] -- Old draft for Python Software Foundation License Version 2 (not adopted and now defunct)
Line 122: Line 163:
 * PythonSoftwareFoundationLicenseV2 -- Old draft for Python Software Foundation License Version 2 (not adopted and now defunct)
Line 126: Line 166:
Line 127: Line 168:
Line 130: Line 172:
Line 131: Line 174:
Line 134: Line 178:
-- LionKimbro <<DateTime(2004-06-28T21:22:21Z)>>
-- [[LionKimbro|LionKimbro]] 2004-06-28 21:22:21
Line 138: Line 184:
-- MichaelChermside
Line 140: Line 185:
[[http://www.python.org/dev/peps/pep-0002/|PEP 2, "Procedure for Adding New Modules"]] contains details. -- David Goodger -- [[MichaelChermside|MichaelChermside]]
Line 142: Line 187:
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

[[http://www.python.org/dev/peps/pep-0002/|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

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 Members' Wiki is provided for collaboration amongst PSF 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.

Board of Directors, Officers, Committees and Members

PSF Projects

2011: PSF Sprints Program

Active project

The PSF funds and helps organize a Python sprints program. See pythonsprints.com for details.

Website: http://pythonsprints.com/

PSF Project Leader: Brian Curtin

2011: PyPI Cloud Mirroring Project

Active project - currently on hold

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

Active 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.

Website: http://brochure.getpython.info/

PSF Project Leader: MarcAndreLemburg

2006 + 2007: Grants Program

Project completed

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

Project completed

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

Project completed

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.

PSF License

Important: See PythonSoftwareFoundationLicenseFaq before using the following licenses.

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.

Historical Records

Discussion

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.

-- MichaelChermside

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

PythonSoftwareFoundation (last edited 2021-10-14 21:17:03 by Srinivas Ramakrishna)

Unable to edit the page? See the FrontPage for instructions.