Differences between revisions 23 and 24
Revision 23 as of 2013-11-25 09:30:01
Size: 5086
Comment: Add announcement list.
Revision 24 as of 2015-09-11 01:09:01
Size: 5638
Editor: EwaJodlowska
Comment:
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
* The `psf-members mailing list <http://mail.python.org/mailman/listinfo/psf-members>`_, which is used for PSF internal discussions. * The `psf-community mailing list <http://mail.python.org/mailman/listinfo/psf-community>`_, which is a newly created list and open to all PSF Members. The purpose of the psf-community mailing list is to provide an environment where pythonistas can communicate with a large audience, share experiences, launch projects, and/or discuss their Python & OSS interests. This community mailing list will have public archives, accessible to everyone.

* The `psf-vote mailing list <http://mail.python.org/mailman/listinfo/psf-vote>`_, which is used for PSF voting discussions. This mailing list is only for voting members. If you are a voting member, you will be automatically subscribed to this mailing list, no action required from you.
Line 30: Line 32:
PSF members can also choose to help out in other ways. The PSF are stewards of the Python intellectual property and deal with many of the non-programming tasks that help guarantee Python has a bright future: keeping the servers running, handling trademark violations, funding Python sprints, administering PyCon, etc. PSF members that wish to be more active in these kinds of tasks may choose to join one of the PSF committees (e.g. the trademarks committee, the outreach and education committee or the infrastructure committee) or eventually put their names forward as potential board members or officers of the foundation (see the additional info below). PSF members can also choose to help out in other ways. The PSF are stewards of the Python intellectual property and deal with many of the non-programming tasks that help guarantee Python has a bright future: keeping the servers running, handling trademark violations, funding Python sprints, administering PyCon, etc. PSF members that wish to be more active in these kinds of tasks may choose to join one of the PSF Workgroups (e.g. the trademarks committee, the outreach and education committee or the infrastructure committee) or eventually put their names forward as potential board members or officers of the foundation (see the additional info below).
Line 34: Line 36:
Committee Pages/Sites Workgroup Pages/Sites
Line 37: Line 39:
The list of currently active committees is at http://www.python.org/psf/committees/ The list of currently active committees is at http://www.python.org/psf/committees/ and below:
Line 39: Line 41:
Some supplementary links:

* Outreach & Education committee: http://psf-outreach.org/ (Help needed getting this populated!)
* Sprints committee: http://pythonsprints.com/
* `Bylaws WG <https://wiki.python.org/psf/BylawsWG>`_
* Cuban Pythonistas WG
* Scientific Python WG
* International Sponsorship Bundle WG
* Grant WG
* Education WG
* Marketing WG
Line 65: Line 70:
  Our regular meetings are held on IRC on the #psf channel on the third
  Monday of
each month at 12:00pm (noon) Eastern time (currently 16:00
  UTC).
  Our regular meetings are held on IRC on the #psf-board channel every two weeks

Info for new PSF Members

(This page is deliberately made available to the public since it provides information which may be useful to prospective members in deciding whether or not to accept a nomination for membership)

PSF Members (Nominated & Sponsor)

New PSF members need to know about the following:

  • The psf-members-announce mailing list, which is a low-traffic list used only for PSF internal announcements.
  • The psf-community mailing list, which is a newly created list and open to all PSF Members. The purpose of the psf-community mailing list is to provide an environment where pythonistas can communicate with a large audience, share experiences, launch projects, and/or discuss their Python & OSS interests. This community mailing list will have public archives, accessible to everyone.
  • The psf-vote mailing list, which is used for PSF voting discussions. This mailing list is only for voting members. If you are a voting member, you will be automatically subscribed to this mailing list, no action required from you.
  • The psf-board-public mailing list, which is used for board discussions which are not legally or otherwise sensitive, allowing them to be shared with the wider PSF membership.
  • This PSF member's wiki. In order to get access, you need to create a profile, and then write to the wiki admins (e.g. goodger@python.org) to get your user name added to the MembersGroup page.

The mailing lists and the members' wiki are restricted to PSF members only as discussions of nominees, proposals and other items under consideration by the PSF may be sensitive or otherwise not yet ready for exposure to a wider audience. Particular pages on the wiki are flagged for public access when these concerns do not apply (registered PSF members can edit this page to see an example of how to make pages public).

To quote the mission statement, the aim of the PSF is "to promote, protect, and advance the Python programming language, and to support and facilitate the growth of a diverse and international community of Python programmers." Potential members are nominated because they're already helping with this mission, so the day to day contribution of many PSF members is simply to continue with what they were already doing.

A key additional responsibility shared by all PSF members is to participate in PSF voting activities, primarily the approval (or disapproval) of new nominated and sponsor members and the election of board members. From time-to-time, other motions may be put before the full membership for a vote, but the day-to-day activities of the PSF are generally handled by the PSF board and the committee members. Voting is primarily electronic these days - it is important that members at least submit their ballots (even if they explicitly abstain from all motions) to ensure quorum is reached. (All votes, including abstentions, are counted for purposes of reaching quorum, but only yes and no votes are subsequently counted for purposes of approving or disapproving of motions).

PSF members can also choose to help out in other ways. The PSF are stewards of the Python intellectual property and deal with many of the non-programming tasks that help guarantee Python has a bright future: keeping the servers running, handling trademark violations, funding Python sprints, administering PyCon, etc. PSF members that wish to be more active in these kinds of tasks may choose to join one of the PSF Workgroups (e.g. the trademarks committee, the outreach and education committee or the infrastructure committee) or eventually put their names forward as potential board members or officers of the foundation (see the additional info below).

The existing members that nominated new members for PSF membership (or the board in the case of sponsor members) should point them towards this page when informing them of their successful nomination.

Workgroup Pages/Sites

The list of currently active committees is at http://www.python.org/psf/committees/ and below:

  • Bylaws WG
  • Cuban Pythonistas WG
  • Scientific Python WG
  • International Sponsorship Bundle WG
  • Grant WG
  • Education WG
  • Marketing WG

Board Members (Directors) & Officers

New Board members (Directors) and Officers should:

A wiki admin should add the Director's/Officer's wiki account to the "BoardGroup" page: http://wiki.python.org/psf/BoardGroup

Info for new PSF members (last edited 2017-01-06 15:03:52 by EwaJodlowska)

Unable to view page? See the FrontPage for instructions.