|Deletions are marked like this.||Additions are marked like this.|
|Line 2:||Line 2:|
== Grants ==
The PSF has started a grants program to fund Python-related
development. For more information, see [http://www.python.org/psf/grants/ PSF Grants].
|Line 44:||Line 49:|
|=== Have the Latest Grant Recipients Been Announced? ===
I saw mention of grants being awarded in Stephan Deibel's recent call for year-end donations. I
wasn't able to find a list of funded projects from the PSF page. Have they not been published yet
or have I just missed them?
-- SkipMontanaro [[DateTime(2004-12-26T09:51:23)]]
They should be announced soon. I ended up sending my message now to get it out before the end
of the tax year, even though the timing isn't perfect because the grants haven't been announced.
- StephanDeibel [[DateTime(2004-12-26T11:00:00)]]
This page will collect information about the Python Software Foundation, and its committees.
The PSF has started a grants program to fund Python-related development. For more information, see [http://www.python.org/psf/grants/ PSF Grants].
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.
PythonSoftwareFoundationLicenseV2 -- Old draft for Python Software Foundation License Version 2 (not adopted and now defunct)
Older wiki materials can be found here:
PSF Software Contribution Agreement
PythonSoftwareFoundationContribAgreementV2 -- Python Software Foundation Contribution Agreement
Committees and Board of Directors
PythonSoftwareFoundationCommittees -- This lists the committees that are currently active in the PSF.
PythonSoftwareFoundationBoard -- Miscellaneous information about the board of directors.
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.
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-along 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.