|
Size: 2893
Comment:
|
Size: 6745
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 28: | Line 28: |
| == Rules & Guidelines == | == Internal Rules & Guidelines == |
| Line 32: | Line 32: |
| * The WG will attempt to resolve any application within three weeks of receipt. | * New members will be approved if they get 50%+1 of the votes casted |
| Line 34: | Line 34: |
| * When adding new members to the working group, prospective members must send an email to psf-fellow@python.org introducing themselves and they must be current PSF Fellow Members. | |
| Line 36: | Line 37: |
| == Decision Making Policy == | |
| Line 37: | Line 39: |
| == Decision Making Procedures == Members of this WG voting on new Fellow Members should take into account one or more of the following criteria: * the candidate has been active as a managing or contributing member of the Python community for at least 3 years, or * the candidate has initiated or significantly influenced a project within the Python community which has significantly increased the Python user base, has significant relevance for Python applications, or has had a significant impact on the public awareness of Python as a programming language, or * the candidate has received an official Python community award (e.g. PSF Community Service Awards, Frank Willison Award). When adding new members to the working group, prospective members must send an email to psf-fellow@python.org introducing themselves and they must be current PSF Fellow Members. |
Below is the policy that the PSF Fellow Work Group is currently voting on (August 11, 2017) |
| Line 48: | Line 42: |
| == Voting == | === Criteria === |
| Line 50: | Line 44: |
| A vote for any member nomination will last for 5 days, or when all voting members have voted, whichever comes first. For a nomination vote to be approved, it must have a majority rule. | * For those who have served the Python community by creating and/or maintaining various creative contributions, the following statement should be true: * [Nominated Person] has served the Python community by making available code, tests, documentation, or design, either in a Python implementation or in a Python ecosystem project, that 1) shows technical excellence, 2) is an example of software engineering principles and best practices, and 3) has achieved widespread usage or acclaim." * For those who have served the Python community by coordinating, organizing, teaching, writing, and evangelizing, the following statement should be true: * [Nominated Person] has served the Python community through extraordinary efforts in organizing Python events, publicly promoting Python, and teaching and coordinating others. [Nominated Person]'s efforts have shown leadership and resulted in long-lasting and substantial gains in the number and quality of Python users, and have been widely recognized as being above and beyond normal volunteering. * If someone is not accepted to be a fellow in the quarter they were nominated for, they will remain an active nominee for 1 year for future consideration. * It is suggested/recommended that the nominee have wide Python community involvement. Examples would be (not a complete list - just examples): * Someone who has received a Community Service Award or Distinguished Service Award * A developer that writes (more than one) documentation/books/tutorials for wider audience * Someone that helps translate (more than one) documentation/books/tutorials for better inclusivity * An instructor that teaches Python related tutorials in various regions * Someone that helps organize local meet ups and also helps organize a regional conference * Nominees should be aware of the Python community’s Code of Conduct and should have a record of fostering the community. * Sitting board of directors can be nominated if they meet the above criteria. In all that this person does, [Nominated Person] is an example of what we aspire to be in the Python community. === Timeline for nominations === Nominees we be reviewed and voted on 4 times throughout the year on a quarterly basis. Timeline is as follows: * '''First quarter / Q1: from the beginning of January to the end of March (01/01 - 31/03)''' * Chair/co-chair will initiate the process in January via PSF mailing lists & social media by doing a call for PSF Fellow nominees. The cut off for quarter one will be February 20. Nominees will be reviewed and considered by the work group from February 20th to March 20th. The new fellows will be announced before March 31. * '''Second quarter / Q2: from the beginning of April to the end of June (01/04 - 30/06)''' * Chair/co-chair will initiate the process in April via PSF mailing lists & social media by doing a call for PSF Fellow nominees. The cut off for quarter two will be May 20. Nominees will be reviewed and considered by the work group from May 20th to June 20th. The new fellows will be announced before June 30. * '''Third quarter / Q3: from the beginning of July to the end of September (01/07 - 30/09)''' * Chair/co-chair will initiate the process in July via PSF mailing lists & social media by doing a call for PSF Fellow nominees. The cut off for quarter three will be August 20. Nominees will be reviewed and considered by the work group from August 20th to September 20th. The new fellows will be announced before end of September. * '''Fourth quarter / Q4: from the beginning of October to the end of December (01/10 - 31/12)''' * Chair/co-chair will initiate the process in October via PSF mailing lists & social media by doing a call for PSF Fellow nominees. The cut off for quarter four will be November 20. Nominees will be reviewed and considered by the work group from November 20th to December 20th. The new fellows will be announced before December 31. === Verification process === Verification can be done through any of the following (or combination of): * Github activity or similar * Meetup.com pages list organizers * Staff pages on conference websites or event reports received via the PSF * the person nominating them * any of the WG members, especially if we know them personally If it is someone we cannot find context on, we can ask the nominator to provide 3 references from within the community. |
| Line 72: | Line 106: |
| * Bruno Rocha * Stéphane Wirtel * Łukasz Langa * Chukwudi Nwachukwu * David Markey * Aisha Bello |
PSF Fellow Work Group Charter
Purpose & Common Goals
The purpose of this working group is to accept, review, discuss, and vote on new Fellow Member nominations.
Active Time
This workgroup will be active indefinitely until the PSF Board decides otherwise.
Core Values & Internal Government
The core values for this group are:
- Respect
- Support
- Positive Atmosphere
- Constructiveness
- Integrity
The workgroup adopts the PSF Code of Conduct (https://www.python.org/psf/codeofconduct/). Any actions (found by a majority) made against the members in the Code of Conduct will result in the acting person being removed from the workgroup.
Internal Rules & Guidelines
When a nomination is received, it will be posted on https://wiki.python.org/moin/PythonSoftwareFoundation/FellowNominations
- Approved Fellow Members will be minuted in the WGs monthly report as well as a monthly announcement to the membership
- New members will be approved if they get 50%+1 of the votes casted
- If/when a particular individual has a conflict of interest they will excuse themselves from any voting.
When adding new members to the working group, prospective members must send an email to psf-fellow@python.org introducing themselves and they must be current PSF Fellow Members.
Decision Making Policy
Below is the policy that the PSF Fellow Work Group is currently voting on (August 11, 2017)
Criteria
- For those who have served the Python community by creating and/or maintaining various creative contributions, the following statement should be true:
- [Nominated Person] has served the Python community by making available code, tests, documentation, or design, either in a Python implementation or in a Python ecosystem project, that 1) shows technical excellence, 2) is an example of software engineering principles and best practices, and 3) has achieved widespread usage or acclaim."
- For those who have served the Python community by coordinating, organizing, teaching, writing, and evangelizing, the following statement should be true:
- [Nominated Person] has served the Python community through extraordinary efforts in organizing Python events, publicly promoting Python, and teaching and coordinating others. [Nominated Person]'s efforts have shown leadership and resulted in long-lasting and substantial gains in the number and quality of Python users, and have been widely recognized as being above and beyond normal volunteering.
- If someone is not accepted to be a fellow in the quarter they were nominated for, they will remain an active nominee for 1 year for future consideration.
- It is suggested/recommended that the nominee have wide Python community involvement. Examples would be (not a complete list - just examples):
- Someone who has received a Community Service Award or Distinguished Service Award
- A developer that writes (more than one) documentation/books/tutorials for wider audience
- Someone that helps translate (more than one) documentation/books/tutorials for better inclusivity
- An instructor that teaches Python related tutorials in various regions
- Someone that helps organize local meet ups and also helps organize a regional conference
- Nominees should be aware of the Python community’s Code of Conduct and should have a record of fostering the community.
- Sitting board of directors can be nominated if they meet the above criteria.
In all that this person does, [Nominated Person] is an example of what we aspire to be in the Python community.
Timeline for nominations
Nominees we be reviewed and voted on 4 times throughout the year on a quarterly basis. Timeline is as follows:
First quarter / Q1: from the beginning of January to the end of March (01/01 - 31/03)
Chair/co-chair will initiate the process in January via PSF mailing lists & social media by doing a call for PSF Fellow nominees. The cut off for quarter one will be February 20. Nominees will be reviewed and considered by the work group from February 20th to March 20th. The new fellows will be announced before March 31.
Second quarter / Q2: from the beginning of April to the end of June (01/04 - 30/06)
Chair/co-chair will initiate the process in April via PSF mailing lists & social media by doing a call for PSF Fellow nominees. The cut off for quarter two will be May 20. Nominees will be reviewed and considered by the work group from May 20th to June 20th. The new fellows will be announced before June 30.
Third quarter / Q3: from the beginning of July to the end of September (01/07 - 30/09)
Chair/co-chair will initiate the process in July via PSF mailing lists & social media by doing a call for PSF Fellow nominees. The cut off for quarter three will be August 20. Nominees will be reviewed and considered by the work group from August 20th to September 20th. The new fellows will be announced before end of September.
Fourth quarter / Q4: from the beginning of October to the end of December (01/10 - 31/12)
Chair/co-chair will initiate the process in October via PSF mailing lists & social media by doing a call for PSF Fellow nominees. The cut off for quarter four will be November 20. Nominees will be reviewed and considered by the work group from November 20th to December 20th. The new fellows will be announced before December 31.
Verification process
Verification can be done through any of the following (or combination of):
- Github activity or similar
- Meetup.com pages list organizers
- Staff pages on conference websites or event reports received via the PSF
- the person nominating them
- any of the WG members, especially if we know them personally
If it is someone we cannot find context on, we can ask the nominator to provide 3 references from within the community.
Communication Plan
The working group will communicate via mailing list (psf-fellow@python.org) and via Slack (the-psf.slack.com#psf-fellow). If needed, conference calls or additional communication channels can be set up.
Budget
No budget will be needed for this. Possibly in the future, this WG can address benefits of Fellow Membership beyond just recognition. At that time the WG will ask the PSF board for a budget.
Current PSF Fellow WG Budget
$0
Participants
- Naomi Ceder
- Kushal Das
- Ewa Jodlowska
- Thomas Wouters
- Bruno Rocha
- Stéphane Wirtel
- Łukasz Langa
- Chukwudi Nwachukwu
- David Markey
- Aisha Bello