-
-
Notifications
You must be signed in to change notification settings - Fork 75
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Call out PyLadies-specific adaptions/additions
- Loading branch information
Showing
1 changed file
with
31 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,6 +5,36 @@ It is also copied below. Refer to the [PSF's policies] for [a best practices gui | |
for Events][events], the [PSF's Code of Conduct Working Group Enforcement Procedures][procedures], and | ||
the [PSF's Community Member Procedure for Reporting Code of Conduct Incidents][incidents]. | ||
|
||
```{attention} Scope Adaptations for PyLadies | ||
In addition to the [Scope](#scope) detailed below, this is also applicable to PyLadies related events | ||
and online spaces. This includes: | ||
* local PyLadies chapter events and meetups | ||
* PyLadies global events at Python conferences | ||
* PyLadies-focused conferences | ||
* PyLadies local and global mailing lists | ||
* PyLadies local and global Slack organizations | ||
* code repositories, issues, and pull requests within any PyLadies-controlled GitHub organization | ||
* comments & responses made on official PyLadies organization & PyLadies conference social media accounts, official hashtags, and hosted media. | ||
* any other online space administered by PyLadies | ||
In addition to what the [scope](#scope) below includes for whom the CoC applies, it also applies to: | ||
* PyLadies Global Council members | ||
* PyLadies chapter organizers and leaders | ||
* PyLadies maintainers, reviewers, and contributors | ||
* PyLadies online administrators | ||
* all community members | ||
``` | ||
|
||
```{attention} Additional Contacts | ||
In addition to the [PSF contact information](#contact-information) available for reporting violations | ||
or raising concerns, you may also reach out to [[email protected]](mailto:[email protected]) which is | ||
monitored by Tania Allard and Bethany Garcia. There is also the `@admin` group within the PyLadies | ||
Slack organization that you can privately message (click into the `@admin` group to see the | ||
individuals who are a part of the group), as well as the `#pyladies-support` channel. | ||
``` | ||
|
||
## Python Software Foundation Code of Conduct | ||
|
||
The Python community is made up of members from around the globe with a diverse set of skills, personalities, and experiences. It is through these differences that our community experiences great successes and continued growth. When you're working with members of the community, this Code of Conduct will help steer your interactions and keep Python a positive, successful, and growing community. | ||
|
@@ -136,7 +166,7 @@ Each online space listed above is encouraged to provide the following informatio | |
|
||
The Python Software Foundation Code of Conduct work group will receive and evaluate incident reports from the online communities listed above. The Python Software Foundation Code of Conduct work group will work with online community administrators/moderators to suggest actions to take in response to a report. In cases where the administrators/moderators disagree on the suggested resolution for a report, the Python Software Foundation Code of Conduct work group may choose to notify the Python Software Foundation board. | ||
|
||
##### Contact Information | ||
#### Contact Information | ||
|
||
If you believe that someone is violating the code of conduct, or have any other concerns, please contact a member of the Python Software Foundation Code of Conduct work group immediately. They can be reached by emailing <[email protected]> | ||
|
||
|