The PyLadies Project teams were kick started in an effort to provide other means of participation for PyLadies members while also increasing the ability of PyLadies to manage itself as an open source project. See the Request for Comment issue for information.
Any self-identifying PyLadies member can participate as a contributing member. Additionally each project will require a project lead or project leads. Any project member can self-nominate or nominate another person to be a project lead. If nominating another to be a project lead, the individual must be a self-identifying PyLadies member and their consent will be required (e.g. an email sent to the person and they consent to participate).
Membership as a PyLadies member, therefore, will rely on self-identification.
Additional requirements to consider:
-
Basic communication in English or ability to alternatively contribute to the project team through English (e.g. a local volunteer can help include updates in English representing volunteers from a geographic region). Please note that the language(s) a Project team can support depend on the members of the team, if additional languages are needed please note in your proposal (see below) or contact that project team directly.
-
Reasonably responsive on email, GitHub, and Slack
-
Open up a new issue outlining the scope of the project, project team members information, and other requested details with this template.
-
Solicit feedback and members in the PyLadies Slack using the channels #general and #project-proposals.
-
Get approval from the PyLadies Global Admin Team (the issue template automatically tags
cc/@pyladies/pyladies-global-admin).
We recommend making a few up front "administrative" decisions around membership, communication, & contributions. Documenting how the project team will be "run" helps volunteers understand where & how they can best contribute. These agreements can be added to the team project issue, the project repo README.md, or any other place that's accessible to all team members:
- How will members ask/apply to join your project team? Are there expectations and/or qualifications you'd like to articulate?
- What will be the process for onboarding new project members?
- How will the group communicate with one another? How will members stay informed & coordinated?
- What will be the workflow for contributions coming into the group? What will be the review process for issues & suggestions?
- How will the issues / units of work / project areas be managed? How will you track progress & challenges?
Any of the global-organizing admins or existing project leads can also help you with tools & processes that have worked for them, or with any repo ,project board, or wiki setup needed for your team. Just reach out on Slack, or open an issue in this repository.
Creating new chapter and password reset require PyLadies Admin account in GSuite. However, other activities like reviewing chapter requests and other email communication do not require an admin account. As such, Project lead(s) should be one of the PyLadies Admin account, however team members can be any self-identifying PyLadies member.
A team to handle the Global PyLadies Communication and Engagement work. Work includes managing comms as it relates to interchapter communication and managing digital assets (e.g. blog, Slack). As such, Project lead(s) should include at least one seasoned PyLadies Chapter organizer, however team members can be any self-identifying PyLadies member.
As an organization situated beneath the Python Software Foundation, PyLadies is subject to the PSF Code of Conduct. Additionally as a global organization we should offer a place for PyLadies to handle our own incident reports as well as have discussion related to any Code of Conduct considerations. Most importantly, though, this project team would offer support to our chapter organizers in training, knowledge acquisition, and more.
While there is a Python Software Foundation Grants program, PyLadies itself has a central set of finances available that could be better used to support our global chapters. Examples may include expanding financial aid at global Python conferences, having finance options available for chapters to obtain t-shirts, stickers, or other swag. Lastly, this group could help determine what to invest finance in and consider ways to help fundraise on behalf of PyLadies.
Maintaining PyLadies technology will be scoped to helping maintain pyladies.com, helping chapters with setting up their websites under the pyladies.com domain, and anything else that may be needed for the PyLadies chapters technology needs.
Looking at PyCon US as an example, PyLadies has a presence at PyCon US with programming including the PyLadies auction, PyLadies lunch, and the PyLadies booth. This project team can help build out similar programming at other global Python conferences as well as offer input on the size of PyLadies financial aid benefits for global Python conferences. Examples of work to be done include developing reusable assets, documentation on what PyLadies at PyCon programming may mean, and performing outreach to get a team that can help setup and staff events.
Many new PyLadies chapters ask common questions such as “what is your chapter doing this month” and may ask for example lesson(s) or tutorial(s) to run in their chapter. This project team will help curate chapter specific resources and manage those resources on https://github.com/pyladies/pyladies-chapter-resources. Additionally, helping chapters with onboarding would fall under this project team’s purview.
If you have questions, reach out in PyLadies Slack or else open an issue in this repository.